Kimi K3.1 Pro vs Qwen3.8 Max

vs

Which one, when

Base output costs $10 vs $6 per million tokens (kimi-k3.1-pro vs qwen3.8-max). Evaluate qwen3.8-max for repeated text and image requests where cached prompt input matters. Against qwen3.8-max, evaluate kimi-k3.1-pro for long coding sessions with screenshot input and structured responses.

Benchmarks

Kimi K3.1 Pro: the vendor has not published benchmark scores.

Above averageNo peer higherQwen3.8 Max31 / 408 / 40
Kimi K3.1 Pro Qwen3.8 Max other models measured peer average ★ no peer scored higher
SWE-Bench Pro
N/A
67.7%
AndroidBench
N/A
75.1%
Cybergym
N/A
78.5%
HealthBench
N/A
no peer scored higher 60.2%
JobBench
N/A
53.4%
PLawBench
N/A
no peer scored higher 73.2%
GPQA Diamond
N/A
92.6%
Agents' Last Exam
N/A
27%

Vendor-published: Alibaba (Qwen) Alibaba (Qwen) Alibaba (Qwen) Alibaba (Qwen) Alibaba (Qwen) Alibaba (Qwen) Alibaba (Qwen) Anthropic Anthropic Anthropic Anthropic ByteDance DeepSeek DeepSeek Google Google Google Google MiniMax Moonshot Moonshot OpenAI OpenAI OpenAI OpenAI OpenAI OpenAI OpenAI Tencent Z.ai Z.ai Z.ai Z.ai

Pricing

Kimi K3.1 Pro Qwen3.8 Max Δ
Input / 1M tokens $2 $2 =
Output / 1M tokens $10 $6 1.7×
Cache read / 1M tokens $0.2 $0.25 0.8×
Cache write - 1.25x -

Rates from the live catalogue at build time; each model page carries the current rate card.

Where they sit · input price per 1M tokens across all 86 chat models on this billing unit (log scale)

$0.05 · Qwen3 VL Flash $30 · GPT-5.4 Pro

Capabilities

Kimi K3.1 Pro Qwen3.8 Max
Tool calling yes yes
Thinking control yes (vendor dial not published) yes (vendor dial not published)
Structured output yes yes
Prompt caching implicit (automatic) implicit + explicit
Cache lifetime not published explicit: 5m, reset on hit
Minimum cached prefix not published 1,024 tokens

Specs

Kimi K3.1 Pro Qwen3.8 Max
Input modalities text image text image
Output modalities text text
Released 2026-10-23 2026-08-03
Context window 1,048,576 983,616
Max output 1,048,576 131,072

Specs are transcribed from each vendor’s documentation; a row a vendor does not publish is left out rather than inferred. Full sources: Kimi K3.1 Pro · Qwen3.8 Max

One prompt, both models, measured through the gateway

PROMPT Explain to a CFO, in exactly three sentences, why our LLM bill doubled after we enabled reasoning. CHECK exactly 3 sentences

Kimi K3.1 Pro passed · 3 sentences

Enabling reasoning makes the model generate extra internal “thinking” tokens before responding, and these are typically billed at output-token rates even though users never see them. If request volume and pricing stayed flat but reasoning substantially increased tokens per request, the total bill could double. Compare pre- and post-change usage reports for reasoning tokens, then control costs with lower reasoning effort, token budgets, cheaper models, and selective use on tasks where the quality gain justifies the spend.

out 471 tok (+366 thinking) latency 14.3 s

Qwen3.8 Max passed · 3 sentences

Enabling reasoning makes the model produce additional hidden steps before responding, and those tokens are billable. It also tends to lengthen each interaction because the model works through more possibilities before settling on an answer. Therefore, the bill doubled mainly due to higher compute and token usage per request, not necessarily because the number of requests doubled.

out 378 tok (+305 thinking) latency 8.6 s

Instruction following (exactly three sentences, so countable), audience shaping (CFO register), and the hidden-thinking billing gap the token meters below expose.

PROMPT This function is supposed to return the longest run of consecutive equal items, but callers report it is off by one on single-element inputs and misses runs that end at the last index. Fix it and explain the bug in one paragraph. CHECK fix passes tests

Kimi K3.1 Pro passed · 8/8 cases

```python def longest_run(xs): if not xs: return 0 best = cur = 1 for i in range(1, len(xs)): if xs[i] == xs[i - 1]: cur += 1 else: best = max(best, cur) cur = 1 return max(best, cur) ``` The original `cur` counts matching adjacent pairs rather than items: it starts at 0, so a singleton returns 0, and a run of `k` equal items is recorded as only `k - 1`. Its bookkeeping also never correctly finalizes the current run’s length at end of input. The fix starts every run at 1, records its length when a mismatch ends it, and takes a final `max` after the loop so a run ending at the last index is included; empty input returns 0.

out 2984 tok (+2785 thinking) latency 70.1 s

Qwen3.8 Max passed · 8/8 cases

```python def longest_run(xs): if not xs: return 0 best = cur = 1 for i in range(1, len(xs)): if xs[i] == xs[i - 1]: cur += 1 else: cur = 1 best = max(best, cur) return best ``` The bug is that the original code starts `best` and `cur` at `0`, so it counts adjacent equal *transitions* rather than the number of items in the run. A run of length `n` has only `n - 1` equal-neighbor transitions, so single-element inputs return `0`, and runs that reach the end are undercounted by one. Initializing the current run to `1` for the first element, resetting it to `1` on a break, and updating `best` from that count fixes the off-by-one.

out 1616 tok (+1411 thinking) latency 34.7 s

Whether the fix is actually correct (runnable), explanation density, and token efficiency on a bounded task.

PROMPT Extract a JSON object with fields {company, quarter, revenue_usd_m, growth_pct, guidance} from this text. Use null for anything not stated; add no other fields. CHECK valid JSON, schema exact

Kimi K3.1 Pro passed · 5/5 fields, guidance null

{"company":"Meridian Robotics","quarter":"September quarter","revenue_usd_m":412,"growth_pct":11,"guidance":null}

out 454 tok (+410 thinking) latency 12.0 s

Qwen3.8 Max passed · 5/5 fields, guidance null

{ "company": "Meridian Robotics", "quarter": "September quarter", "revenue_usd_m": 412, "growth_pct": 11, "guidance": null }

out 1199 tok (+1141 thinking) latency 24.4 s

Schema obedience (no invented fields), hallucination pressure (guidance is explicitly withheld), and structured-output path differences.

PROMPT Write a 120-word product announcement for an API gateway feature that caches prompts across providers. Forbidden words: "seamless", "unlock", "game-changer", "revolutionize", "empower". Exactly one sentence must be a question. CHECK 120 words, 0 banned words

Kimi K3.1 Pro passed · 120 words, 0 banned, 1 question

Meet Prompt Cache, our new API gateway feature for caching prompts and responses across model providers. It cuts token spend, lowers latency, and keeps applications responsive during traffic surges. Define cache keys, expiration rules, and tenant boundaries in one policy, then apply them to OpenAI, Anthropic, Gemini, or custom models without changing application code. Encryption, redaction, and immediate purges help protect sensitive data, while metrics reveal hit rates, savings, and performance by endpoint and provider. Need a faster way to handle repeated requests? Serve eligible results from cache and preserve your existing routing, fallback, and retry behavior. Available today in beta, Prompt Cache gives platform teams controls for cost, speed, and reliability, with no extra infrastructure to deploy or maintain.

out 2740 tok (+2576 thinking) latency 55.8 s

Qwen3.8 Max passed · 120 words, 0 banned, 1 question

Today, our API gateway adds prompt caching across major model providers. It stores prompts and responses in one fast cache layer. Teams can lower token spend, reduce latency, and repeat reliable answers. The feature supports OpenAI, Anthropic, Google, and Mistral through one configuration. You can set retention rules, scope access, and invalidate entries quickly. How does your team maintain consistent results during provider outages? Approved cached responses keep applications stable while fallback routes recover. The dashboard shows hit rates, savings, latency, and provider usage. Engineers receive audit trails for every cached prompt, enabling safer testing. Product managers can compare cost trends before and after cache adoption. Start with a small route, then safely expand caching to production traffic right now.

out 2744 tok (+2591 thinking) latency 46.3 s

Constraint obedience (word budget, banned-word list, the single question), style fingerprint, and length control.

Switch between them with one line

Both ids are in every tab below; the highlighted pair of lines is the only edit. Same endpoint, same key, same request shape.

from openai import OpenAI

client = OpenAI(
    base_url="https://synthorai.io/v1",
    api_key="sk-syn-...",
)

resp = client.chat.completions.create(
    model="kimi-k3.1-pro",
    # model="qwen3.8-max",  # uncomment this line, comment the one above
    messages=[{"role": "user", "content": "Summarize this diff"}],
    reasoning_effort="medium",
)
print(resp.choices[0].message.content)

Get your API key →

FAQ

Which is cheaper, Kimi K3.1 Pro or Qwen3.8 Max?

Both list $2 for “Input / 1M tokens”. Other rates and the number of units used can still change the total cost.

Can I A/B test Kimi K3.1 Pro against Qwen3.8 Max without two integrations?

Yes. Both are served through the same OpenAI-compatible endpoint with one API key. Switching is a one-line change to the model id, so you can route a fraction of traffic to each and compare bills directly.

Do Kimi K3.1 Pro and Qwen3.8 Max support prompt caching?

Yes. Both bill cache reads below their input rate, so warm-prefix workloads cost less than the list rates suggest. The exact cache-read rows are in the pricing table above.

Related comparisons

From our measured studies