Kimi K3 vs Qwen3.7 Max
Pricing, context window and real answers (August 2026)
Kimi K3 (Moonshot) and Qwen3.7 Max (Qwen), 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
 Kimi K3 |  Qwen3.7 Max | |
|---|---|---|
| Provider | Moonshot | Qwen |
| Input (per 1M tokens) | ¥536.1 | ¥263.58 |
| Output (per 1M tokens) | ¥2,680.5 | ¥790.75 |
| Typical cost (1,000 in + 500 out tokens × 1,000 calls) | ¥1,876 | ¥659 |
| Context window | 1,048,576 tokens | 1,000,000 tokens |
| Release date | 7/16/2026 | 5/21/2026 |
| Input modalities | text, image | text |
| Arena · overall | #11 · ELO 1,486 | #21 · ELO 1,475 |
| Arena · Japanese | Unranked | Unranked |
| Arena · coding | #8 · ELO 1,530 | #15 · ELO 1,526 |
Prices are FastMetal's yen rates before tax. Arena ranks are as of the latest leaderboard scrape.
Which should you pick?
- On price, Qwen3.7 Max: ¥790.75 per 1M output tokens, 70% less than Kimi K3.
- On the Overall arena board, Kimi K3 ranks higher (#11; Qwen3.7 Max is #21).
- On the Coding arena board, Kimi K3 ranks higher (#8; Qwen3.7 Max is #15).
- For long documents, Kimi K3: a 1,048,576-token context window against 1,000,000 for Qwen3.7 Max.
- 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.
Kimi K3
# Counting the 'r's in "strawberry"
**Step 1: Write out each letter with its position**
| Position | Letter |
|----------|--------|
| 1 | s |
| 2 | t |
| 3 | **r** ✓ |
| 4 | a |
| 5 | w |
| 6 | b |
| 7 | e |
| 8 | **r** ✓ |
| 9 | **r** ✓ |
| 10 | y |
**Step 2: Identify each 'r'**
- Position 3: the 'r' in "st**r**"
- Position 8: the first 'r' in "be**r**ry"
- Position 9: the second 'r' in "ber**r**y"
**Step 3: Verify by splitting the word**
"Strawberry" = "straw" + "berry"
- "straw" contains **1** r
- "berry" contains **2** r's
**Answer: There are 3 r's in "strawberry."** 🍓
12.2s594 output tokens
Qwen3.7 Max
To count the number of 'r's in the word "strawberry", let's break the word down letter by letter from left to right:
1. **s** - not an 'r'
2. **t** - not an 'r'
3. **r** - This is the **1st** 'r'
4. **a** - not an 'r'
5. **w** - not an 'r'
6. **b** - not an 'r'
7. **e** - not an 'r'
8. **r** - This is the **2nd** 'r'
9. **r** - This is the **3rd** 'r'
10. **y** - not an 'r'
By examining each character individually, we can see that the letter 'r' appears in the 3rd, 8th, and 9th positions.
Therefore, there are **3** 'r's in "strawberry".
15.1s842 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…
Kimi K3
## What's causing it
The error means `users` is `undefined` when the component renders — `.map()` only exists on arrays, so calling it on `undefined` throws. Your component code is fine; the problem is **upstream**: whatever renders `<UserList />` isn't passing a valid array.
The most common culprit is **async data fetching with uninitialized state** in the parent:
```jsx
function App() {
const [users, setUsers] = useState(); // ← undefined!
useEffect(() => {
fetch('/api/users')
.then(res => res.json())
.then(setUsers);
}, []);
return <UserList users={users} />; // undefined on first render
}
```
The component renders *before* the fetch resolves, so `users` is `…
47.5s1756 output tokens
Qwen3.7 Max
This error occurs because the `users` prop being passed to your `UserList` component is **`undefined`** at the time React tries to render it. JavaScript cannot call the `.map()` method on `undefined`, which throws the error.
This usually happens for one of three reasons:
1. **Asynchronous Data Fetching:** The parent component is fetching `users` from an API. On the *initial render*, the data hasn't arrived yet, so the variable is `undefined`.
2. **Missing Prop:** The parent component forgot to pass the `users` prop (e.g., `<UserList />` instead of `<UserList users={myUsers} />`).
3. **Incorrect State Initialization:** The parent component initialized its state as `undefined` or `null` inste…
34.9s1851 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):…
Kimi K3
This works, but there are several issues worth addressing. Here's a breakdown, followed by an improved version.
## Issues
### Correctness & best practices
1. **Bare `except:`** — catches *everything*, including `KeyboardInterrupt` and programming bugs like `KeyError` on a malformed item (which then get pointlessly retried). Catch `requests.RequestException` specifically.
2. **Silent failures** — errors are swallowed with no logging, and returning `[]` makes "API is down" indistinguishable from "no active items." At minimum, log; ideally, raise after the final attempt.
3. **Retrying non-retryable errors** — a 400/401/404 will never succeed on retry, but the code sleeps and retries anyway. O…
57.6s8060 output tokens
Qwen3.7 Max
Here is a comprehensive review of your function, broken down by readability, performance, and best practices, followed by a refactored version.
### 1. Readability & Style (PEP 8)
* **Imports inside the function:** Imports should generally be placed at the top of the file, not inside the function. This makes dependencies clear and avoids slight overhead on every function call.
* **`item["active"] == True`:** In Python, explicitly comparing to `True` is discouraged (PEP 8). You should just use `if item.get("active"):`. Using `.get()` also prevents `KeyError` if the key is missing.
* **Manual List Building:** The `for` loop with `.append()` can be replaced with a much cleaner and faster **list…
58.3s3301 output tokens
Frequently asked questions
- Which is cheaper, Kimi K3 or Qwen3.7 Max?
- Per 1M output tokens, Kimi K3 is ¥2,680.5 and Qwen3.7 Max is ¥790.75 on FastMetal (yen, before tax), so Qwen3.7 Max is cheaper.
- How do the context windows of Kimi K3 and Qwen3.7 Max compare?
- Kimi K3 takes 1,048,576 tokens; Qwen3.7 Max takes 1,000,000.
- Which ranks higher, Kimi K3 or Qwen3.7 Max?
- Kimi K3 ranks higher on the public arena (Kimi K3 #11, Qwen3.7 Max #21). Ranks move as the leaderboard updates.
- Can I use Kimi K3 and Qwen3.7 Max with the same API key?
- Yes. On FastMetal's OpenAI-compatible endpoint, switch by passing "kimi-k3" or "qwen3.7-max" 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 Kimi K3 and Qwen3.7 Max from the browser chat and the API. No monthly fee.