gpt-oss-120b vs Kimi K3.1 Pro
Pricing, context window and real answers (October 2026)
gpt-oss-120b (OpenAI) and Kimi K3.1 Pro (Moonshot), 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-120b |  Kimi K3.1 Pro | |
|---|---|---|
| Provider | OpenAI | Moonshot |
| Input (per 1M tokens) | $0.102 | $2.11 |
| Output (per 1M tokens) | $0.5035 | $10.55 |
| Typical cost (1,000 in + 500 out tokens × 1,000 calls) | $0.3537 | $7.39 |
| Context window | 131,072 tokens | 1,048,576 tokens |
| Release date | 8/5/2025 | 10/23/2026 |
| Input modalities | text | text, image, video |
| Throughput (p50) | 327 tokens/s (n=26) | — |
| Arena · overall | #218 · ELO 1,352 | Unranked |
| Arena · Japanese | #155 · ELO 1,325 | Unranked |
| Arena · coding | #225 · ELO 1,389 | Unranked |
Prices are FastMetal's rates, before tax.
Rankings: LMArena leaderboard dataset (lmarena-ai/leaderboard-dataset), CC BY 4.0, snapshot 2026-10-22; category names mapped and ratings rounded by FastMetal.
Which should you pick?
- On price, gpt-oss-120b: $0.5035 per 1M output tokens, 95% less than Kimi K3.1 Pro.
- For long documents, Kimi K3.1 Pro: a 1,048,576-token context window against 131,072 for gpt-oss-120b.
- 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-120b
**Step‑by‑step count of the letter “r” in the word “strawberry”**
1. Write out the word with each letter in order, labeling its position:
| Position | Letter |
|----------|--------|
| 1 | s |
| 2 | t |
| 3 | **r** |
| 4 | a |
| 5 | w |
| 6 | b |
| 7 | e |
| 8 | **r** |
| 9 | **r** |
|10 | y |
2. Scan the list and mark every occurrence of the letter **r**.
- Position 3 → r (first occurrence)
- Position 8 → r (second occurrence)
- Position 9 → r (third occurrence)
3. Count the marked entries: there are **3** marked positions.
**Result:** The word “strawberry” contains **3** occurrences of the letter **r**…
1.7s332 output tokens
Kimi K3.1 Pro
There are **3** ‘r’s in **“strawberry.”**
1. Write out each letter: **s – t – r – a – w – b – e – r – r – y**
2. Locate the ‘r’s: positions **3, 8, and 9**.
3. Count them: **1 + 1 + 1 = 3**.
11.3s
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-120b
### Why the `map` can’t be called
`Array.prototype.map` is a method that exists only on **arrays** (or array‑like objects).
When you see
```
TypeError: Cannot read properties of undefined (reading 'map')
at UserList (...)
```
it means that the variable you think is an array – `users` in this case – is actually **`undefined`** (or `null`).
React is trying to evaluate this line:
```jsx
{users.map(user => <li key={user.id}>{user.name}</li>)}
```
and it crashes because you can’t read `.map` from `undefined`.
---
## Common reasons `users` ends up undefined
| Reason | Typical scenario | How it shows up |
|--------|------------------|-----------------|
| **Prop not passed** | `<Use…
7.3s1610 output tokens
Kimi K3.1 Pro
## What's causing the error
The error means `users` is `undefined` when the component renders, and you can't call `.map()` on `undefined`. The component itself is fine — the problem is that whatever renders `<UserList />` either isn't passing the prop, or is passing a value that isn't an array yet.
The most common cause is **async data fetching**: the parent renders `UserList` before the data has loaded.
```jsx
function App() {
const [users, setUsers] = useState(); // ❌ undefined on first render
useEffect(() => {
fetch('/api/users')
.then(res => res.json())
.then(setUsers);
}, []);
return <UserList users={users} />; // users is undefined here initially
}
```
On…
36.3s
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-120b
Below is a **step‑by‑step review** of the original `get_data` implementation followed by a **refactored version** that addresses readability, performance, and modern Python best‑practice concerns.
---
## 1. What the original function does
```python
def get_data(url, retries=3):
import requests
import time
for i in range(retries):
try:
r = requests.get(url, timeout=10)
if r.status_code == 200:
data = r.json()
result = []
for item in data:
if item["active"] == True:
result.append({"name": item["name"], "id": item["id"]})
return result…
14.4s3132 output tokens
Kimi K3.1 Pro
The timeout and bounded retry loop are good starting points. The biggest issue is that failures—and even programming errors—are silently converted into retries and then `[]`.
### Suggested improvements
- **Avoid bare `except:`**. It catches `KeyboardInterrupt`, `KeyError`, JSON/schema errors, and other bugs. Retry only expected transient network failures; let malformed responses fail visibly.
- **Use a deliberate retry policy**. Retrying `401`, `403`, or `404` usually wastes time. Retry only transient statuses, use exponential backoff, and avoid sleeping after the final attempt.
- **Do not use `[]` for both failure and no results**. Prefer raising the final exception so callers can disting…
560.2s
Frequently asked questions
- Which is cheaper, gpt-oss-120b or Kimi K3.1 Pro?
- Per 1M output tokens, gpt-oss-120b is $0.5035 and Kimi K3.1 Pro is $10.55 on FastMetal (US dollars, before tax), so gpt-oss-120b is cheaper.
- How do the context windows of gpt-oss-120b and Kimi K3.1 Pro compare?
- gpt-oss-120b takes 131,072 tokens; Kimi K3.1 Pro takes 1,048,576.
- Can I use gpt-oss-120b and Kimi K3.1 Pro with the same API key?
- Yes. On FastMetal's OpenAI-compatible endpoint, switch by passing "gpt-oss-120b" or "kimi-k3.1-pro" 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-120b and Kimi K3.1 Pro from the browser chat and the API. No monthly fee.