Kimi K3.1 Pro vs Qwen3.8 Flash

vs

Which one, when

Base output costs $10 vs $0.47 per million tokens (kimi-k3.1-pro vs qwen3.8-flash). Choose qwen3.8-flash when a video clip must go straight into the prompt. Against qwen3.8-flash, 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 Flash12 / 163 / 16
Kimi K3.1 Pro Qwen3.8 Flash other models measured peer average ★ no peer scored higher
SWE-Bench Pro
N/A
62.5%
OSWorld 2.0 partial
N/A
52.3%
JobBench
N/A
55.7%
GPQA Diamond
N/A
91.7%
ERQA
N/A
no peer scored higher 72.3%
Agents' Last Exam Pass
N/A
24.3%
LVBench
N/A
76.6%

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

Pricing

Kimi K3.1 Pro Qwen3.8 Flash Δ
Input / 1M tokens $2 $0.15 13×
Output / 1M tokens $10 $0.47 21×
Cache read / 1M tokens $0.2 $0.016 13×
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)

Kimi K3.1 Pro · $2 Qwen3.8 Flash · $0.15
$0.05 · Qwen3 VL Flash $30 · GPT-5.4 Pro

Capabilities

Kimi K3.1 Pro Qwen3.8 Flash
Tool calling yes yes
Thinking control yes (vendor dial not published) configurable
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 Flash
Input modalities text image text image video
Output modalities text text
Released 2026-10-23 2026-08-27
Context window 1,048,576 1,000,000
Max output 1,048,576 131,072
Thinking parameter -
  • enable_thinking
  • thinking_budget
  • preserve_thinking
Accepted values -
enable_thinking
  • true
  • false
thinking_budget
  • in tokens
preserve_thinking
  • true
  • false
Default -

on

qwen3.8-flash is hybrid thinking with thinking enabled by default, thinking_budget defaults to the 262,144-token chain maximum, and preserve_thinking is off

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 Flash

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 Flash passed · 3 sentences

Enabling reasoning makes the model spend additional output tokens to plan and validate answers before responding, and those tokens are billed. It also increases compute and latency per request, so each task consumes more capacity than a non-reasoning call. As a result, billable tokens and compute roughly doubled, directly driving the higher invoice.

out 330 tok (+262 thinking) latency 8.9 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 Flash passed · 8/8 cases

```python def longest_run(xs): if not xs: return 0 best = 1 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 version counts adjacent equal pairs rather than items in a run, starting both `cur` and `best` at `0`, and it resets `cur` to `0` after a mismatch, thereby discarding the first element of the new run. That makes single-element inputs return `0`, and because every run is effectively measured in “steps” between equal elements, the last element is not counted—particularly noticeable when the longest run ends at the final index.

out 2123 tok (+1933 thinking) latency 43.8 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 Flash passed · 5/5 fields, guidance null

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

out 519 tok (+463 thinking) latency 10.5 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 Flash passed · 120 words, 0 banned, 1 question

We are announcing prompt caching across providers in our API gateway. Store approved prompt outputs once and reuse them across supported model providers, cutting latency, cost, and duplicate token spend. The feature matches identical requests, checks validity, and returns cached results while preserving routing controls. Developers keep existing endpoints; the gateway manages storage, invalidation, and provider differences. This reduces noisy repeat calls, improves steady responses, and frees teams to focus on better agent workflows. OpenAI, Anthropic, Google, Mistral, and custom routes are supported. Cache hits appear in analytics with latency, token, and cost reductions visible. Check retention and privacy rules before enabling it. Ready to add cache controls to your gateway? Enable it in settings and watch spend drop now.

out 5958 tok (+5805 thinking) latency 88.8 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-flash",  # 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 Flash?

Qwen3.8 Flash is cheaper on the "Input / 1M tokens" row ($0.15 vs $2, 13× apart). Other rows may point the other way; the table above carries the full rate card, and real cost depends on your mix.

Can I A/B test Kimi K3.1 Pro against Qwen3.8 Flash 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 Flash 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