gpt-oss-20b vs MiMo-V2.5
Pricing, context window and real answers (September 2026)
gpt-oss-20b (OpenAI) and MiMo-V2.5 (Xiaomi), compared as you can actually call them on FastMetal. Both are served from the same OpenAI-compatible endpoint and API key; switching is a change to the model string.
Specs and pricing
 gpt-oss-20b | MiMo-V2.5 | |
|---|---|---|
| Provider | OpenAI | Xiaomi |
| Input (per 1M tokens) | ¥5.36 | ¥25.02 |
| Output (per 1M tokens) | ¥25.02 | ¥50.04 |
| Typical cost (1,000 in + 500 out tokens × 1,000 calls) | ¥18 | ¥50 |
| Context window | 131,072 tokens | 1,050,000 tokens |
| Release date | 8/5/2025 | 4/22/2026 |
| Input modalities | text | text, audio, image, video |
| Throughput (p50) | — | — |
| Arena · overall | #252 · ELO 1,317 | #96 · ELO 1,434 |
| Arena · Japanese | #179 · ELO 1,256 | #141 · ELO 1,321 |
| Arena · coding | #232 · ELO 1,369 | #81 · ELO 1,491 |
Prices are FastMetal's yen rates before tax. Arena ranks are as of the latest leaderboard scrape.
Which should you pick?
- On price, gpt-oss-20b: ¥25.02 per 1M output tokens, 50% less than MiMo-V2.5.
- On the Overall arena board, MiMo-V2.5 ranks higher (#96; gpt-oss-20b is #252).
- On the Japanese arena board, MiMo-V2.5 ranks higher (#141; gpt-oss-20b is #179).
- On the Coding arena board, MiMo-V2.5 ranks higher (#81; gpt-oss-20b is #232).
- For long documents, MiMo-V2.5: a 1,050,000-token context window against 131,072 for gpt-oss-20b.
- If in doubt, try both on the same key. Switching is a change to the model string, and each is billed at its own rate.
Real answers to the same prompts
Exactly what the FastMetal gateway returned, side by side. Not benchmark scores: actual output.
Count the number of 'r's in 'strawberry'
Count the number of 'r's in 'strawberry'. Explain your reasoning step by step.
gpt-oss-20b
**Count of ‘r’ in “strawberry”: 3**
---
### Step‑by‑step reasoning
1. **Write out the word in individual letters**
```
s t r a w b e r r y
```
2. **Identify each ‘r’**
- The first ‘r’: appears after the “t” → **r**
- The second ‘r’: appears in the part “berry” → **r**
- The third ‘r’: the next letter after that → **r**
3. **Verify there are no more letters left**
The remaining letters are “b”, “e”, “y”, none of which are “r”.
4. **Count the identified ‘r’s**
1 (first) + 1 (second) + 1 (third) = **3**
---
### Quick recap
- Word: **strawberry**
- Letters containing “r”: positions 3, 8, and 9.
- Total count: **3**.
11.6s371 output tokens
MiMo-V2.5
# Counting the 'r's in 'strawberry'
Let me spell the word out letter by letter:
| Position | Letter | Is it 'r'? |
|----------|--------|------------|
| 1 | **s** | ❌ |
| 2 | **t** | ❌ |
| 3 | **r** | ✅ (1) |
| 4 | **a** | ❌ |
| 5 | **w** | ❌ |
| 6 | **b** | ❌ |
| 7 | **e** | ❌ |
| 8 | **r** | ✅ (2) |
| 9 | **r** | ✅ (3) |
| 10 | **y** | ❌ |
## Answer: **3** 'r's
The three r's are found at positions **3**, **8**, and **9** in the word.
14.9s313 output tokens
Debug This Error
I'm getting the following error in my Node.js application: TypeError: Cannot read properties of undefined (reading 'map') at UserList (/app/components/UserList.js:12:25) at renderWithHooks (/app/node_modules/rea…
gpt-oss-20b
### Why does the error happen?
`users.map(...)` can only run when **`users` is an array**.
The stack trace shows that the crash happens on line 12 of `UserList.js`, which is the
exact spot where the code tries to call `.map`.
The value that is being passed to `UserList` (or the initial value that the parent
creates) is **`undefined`** (or it could be `null`/`{}`). When JavaScript tries to
read `users.map`, it throws:
```
TypeError: Cannot read properties of undefined (reading 'map')
```
Typical reasons for this are:
1. The parent component **didn’t pass the `users` prop** at all.
2. The parent passed it but the value was **`undefined` / `null`** because data
hasn’t been loaded ye…
11.4s1303 output tokens
MiMo-V2.5
This error occurs because your `users` prop is `undefined` when the component tries to call `.map()` on it. This usually happens when:
1. The parent component doesn't pass a `users` prop
2. The `users` data is still loading (asynchronous operation)
3. There's a typo in the prop name when passing from parent
## How to Fix It
### 1. Add Default Props or Prop Validation
Add a default value for the `users` prop:
```jsx
function UserList({ users = [] }) {
return (
<ul>
{users.map(user => <li key={user.id}>{user.name}</li>)}
</ul>
);
}
// Or with PropTypes
import PropTypes from 'prop-types';
function UserList({ users }) {
return (
<ul>
{users.map(user => <li key…
11.2s808 output tokens
Code Review
Please review the following Python function and suggest improvements for readability, performance, and best practices: def get_data(url, retries=3): import requests import time for i in range(retries):…
gpt-oss-20b
Below is a quick “code‑review” style list that touches the three axes you asked for – **readability**, **performance**, and **best practices**.
After the bullet‑list I’ll paste a refactored version that incorporates the most common fixes.
---
## 1. Readability
| Issue | Why it hurts | Quick fix |
|-------|--------------|-----------|
| **Imports inside the function** | Every call recompiles the import tables and makes the module’s top‑level slower. | Move `import requests` and `import time` to the module’s global header. |
| **Bare `except:`** | Catches *everything* (KeyboardInterrupt, SystemExit, MemoryError, etc.) and swallows useful tracebacks. | Catch only the expected network-relate…
24.6s2267 output tokens
MiMo-V2.5
# Code Review: `get_data` Function
## Issues Identified
| Category | Issue | Severity |
|----------|-------|----------|
| Style | Imports inside function body | Medium |
| Reliability | Bare `except` catches `KeyboardInterrupt`/`SystemExit` | High |
| Reliability | Silent failures — no logging | Medium |
| Readability | `== True` comparison (redundant) | Low |
| Readability | No docstring or type hints | Medium |
| Performance | Could use list comprehension | Low |
| Robustness | No exponential backoff on retries | Medium |
| Robustness | `r.json()` can fail silently under bare except | High |
| Style | Uninformative variable names (`r`, `i`) | Low |
| Config | Magic numbers hardcoded (`ti…
33.6s1854 output tokens
Frequently asked questions
- Which is cheaper, gpt-oss-20b or MiMo-V2.5?
- Per 1M output tokens, gpt-oss-20b is ¥25.02 and MiMo-V2.5 is ¥50.04 on FastMetal (yen, before tax), so gpt-oss-20b is cheaper.
- How do the context windows of gpt-oss-20b and MiMo-V2.5 compare?
- gpt-oss-20b takes 131,072 tokens; MiMo-V2.5 takes 1,050,000.
- Which ranks higher, gpt-oss-20b or MiMo-V2.5?
- MiMo-V2.5 ranks higher on the public arena (gpt-oss-20b #179, MiMo-V2.5 #141). Ranks move as the leaderboard updates.
- Can I use gpt-oss-20b and MiMo-V2.5 with the same API key?
- Yes. On FastMetal's OpenAI-compatible endpoint, switch by passing "gpt-oss-20b" or "mimo-v2.5" as the model. Each is billed at its own rate from the same prepaid balance.
Try both on one API key
Create an account and add credit to call gpt-oss-20b and MiMo-V2.5 from the browser chat and the API. No monthly fee.