Model comparison

Kimi K3 vs Qwen4 Max

Pricing, context window and real answers (November 2026)

Kimi K3 (Moonshot) and Qwen4 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

moonshotai logoKimi K3qwen logoQwen4 Max
ProviderMoonshotQwen
Input (per 1M tokens)$2.22$1.50
Output (per 1M tokens)$11.08$4.48
Typical cost (1,000 in + 500 out tokens × 1,000 calls)$7.76$3.73
Context window1,048,576 tokens1,000,000 tokens
Release date7/16/202611/16/2026
Input modalitiestext, imagetext, image, video
Throughput (p50)96 tokens/s (n=18)—
Arena · overall#20 · ELO 1,487Unranked
Arena · Japanese#8 · ELO 1,508Unranked
Arena · coding#14 · ELO 1,538Unranked

Prices are FastMetal's rates, before tax.

Rankings: LMArena leaderboard dataset (lmarena-ai/leaderboard-dataset), CC BY 4.0, snapshot 2026-11-11; category names mapped and ratings rounded by FastMetal.

Which should you pick?

  • On price, Qwen4 Max: $4.48 per 1M output tokens, 60% less than Kimi K3.
  • For long documents, Kimi K3: a 1,048,576-token context window against 1,000,000 for Qwen4 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

Qwen4 Max

## Answer: There are **3** r's in "strawberry." ### Step-by-step reasoning **Step 1: Write out the word letter by letter.** s – t – r – a – w – b – e – r – r – y **Step 2: Number each position and check for 'r'.** | Position | Letter | Is it 'r'? | |---|---|---| | 1 | s | no | | 2 | t | no | | 3 | **r** | ✅ yes (1) | | 4 | a | no | | 5 | w | no | | 6 | b | no | | 7 | e | no | | 8 | **r** | ✅ yes (2) | | 9 | **r** | ✅ yes (3) | | 10 | y | no | **Step 3: Tally the matches.** One 'r' appears in the first part, "st**r**aw," and two more appear together in the second part, "be**rr**y." 1 + 2 = **3** **Why people often miscount:** The word splits naturally into "straw" + "berry," and the…
11.8s416 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

Qwen4 Max

## What's causing it `users` is `undefined` when `UserList` renders, so `users.map(...)` throws. Destructuring `{ users }` from props doesn't create a default — if the parent doesn't pass `users` (or passes `undefined`), you get exactly this error. The stack trace confirms it's happening during render (`renderWithHooks`), not in an event handler, which means the very first render already has no data. ## The three usual culprits **1. Data is still loading (most common)** ```jsx function Parent() { const [users, setUsers] = useState(); // undefined on first render useEffect(() => { fetch('/api/users') .then(r => r.json()) .then(setUsers); }, []); return <UserList…
16.6s802 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

Qwen4 Max

## Overall assessment The function works on the happy path, but it has one genuine bug (a bare `except` that swallows *everything*, including data-shape errors), and its failure semantics are ambiguous: `[]` means both "no active items" and "the service is down." Below are the issues ordered roughly by impact, then a refactor. --- ## Correctness & robustness **1. Bare `except:` is the biggest problem.** It catches `KeyboardInterrupt` and `SystemExit` (so Ctrl-C during a retry storm won't work), and it hides programming errors. Catch `requests.ConnectionError`, `requests.Timeout`, and `requests.HTTPError` explicitly. **2. Data processing inside the retry loop causes pointless retries.**…
121.9s5826 output tokens

Compare on more prompts →

Frequently asked questions

Which is cheaper, Kimi K3 or Qwen4 Max?
Per 1M output tokens, Kimi K3 is $11.08 and Qwen4 Max is $4.48 on FastMetal (US dollars, before tax), so Qwen4 Max is cheaper.
How do the context windows of Kimi K3 and Qwen4 Max compare?
Kimi K3 takes 1,048,576 tokens; Qwen4 Max takes 1,000,000.
Can I use Kimi K3 and Qwen4 Max with the same API key?
Yes. On FastMetal's OpenAI-compatible endpoint, switch by passing "kimi-k3" or "qwen4-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 Qwen4 Max from the browser chat and the API. No monthly fee.

More comparisons with Kimi K3

More comparisons with Qwen4 Max