Kimi K3 vs Kimi K3.1 Pro

vs

Which one, when

Moonshot built kimi-k3.1-pro from kimi-k3. For a new text or screenshot workflow, start with kimi-k3.1-pro for lower input and output rates. For an existing integration, replay representative tool calls before changing the model alias.

Benchmarks

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

Above averageNo peer higherKimi K352 / 6712 / 67
Kimi K3 Kimi K3.1 Pro other models measured peer average ★ no peer scored higher
DeepSWE 1.1
67.5%
N/A
OSWorld-Verified
84.8%
N/A
Cybergym
80%
N/A
Finance Agent v2
54.4%
N/A
Harvey Lab-AA
no peer scored higher 94.6%
N/A
GPQA Diamond
93.5%
N/A
BrowseComp
91.2%
N/A
Video-MME (w. sub)
no peer scored higher 90%
N/A

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 Tencent Z.ai Z.ai Z.ai Z.ai

Pricing

Kimi K3 Kimi K3.1 Pro Δ
Input / 1M tokens $3 $2 1.5×
Output / 1M tokens $15 $10 1.5×
Cache read / 1M tokens $0.3 $0.2 1.5×

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 · $3 Kimi K3.1 Pro · $2
$0.05 · Qwen3 VL Flash $30 · GPT-5.4 Pro

Capabilities

Kimi K3 Kimi K3.1 Pro
Tool calling yes yes
Thinking control always on yes (vendor dial not published)
Structured output yes yes
Prompt caching implicit (automatic) implicit (automatic)
Cache lifetime not published not published
Minimum cached prefix not published not published

Specs

Kimi K3 Kimi K3.1 Pro
Input modalities text image video text image
Output modalities text text
Released 2026-07-16 2026-10-23
Context window 1,048,576 1,048,576
Max output 1,048,576 1,048,576
Thinking parameter reasoning_effort (top-level; the thinking object is not accepted) -
Accepted values
reasoning_effort
  • low
  • high
  • max
-
Default max -

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 · Kimi K3.1 Pro

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

Reasoning models don't just answer questions—they "think" first, generating long internal chains of step-by-step logic before producing a response. Those hidden thinking steps are billed as output tokens (the most expensive kind, typically 3–5x the price of input tokens), and a single query can generate thousands of them even when the visible answer is only a paragraph long. So you're paying for dramatically more compute per request: the bill doubled because the model does far more work behind the scenes, not because usage increased.

out 755 tok (+637 thinking) latency 20.8 s

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

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 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 best = max(best, cur) else: cur = 1 return best ``` The bug is a fencepost error: `cur` counts *matching adjacent pairs* rather than *items in the run*, because it starts at 0 and only increments when `xs[i] == xs[i - 1]`. A run of length L contains L−1 equal pairs, so every run was undercounted by exactly one. For a single-element list (a run of length 1) the loop never runs and the function returns 0 instead of 1; likewise any run ending at the last index — e.g. the two `2`s in `[1, 2, 2]` — reported 1 instead of 2, making it look like no run existed at all. […]

out 1837 tok (+1547 thinking) latency 47.2 s

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

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 passed · 5/5 fields, guidance null

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

out 924 tok (+863 thinking) latency 25.9 s

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

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 passed · 120 words, 0 banned, 1 question

Meet Prompt Cache, a new API gateway capability that stores prompt responses and serves them across OpenAI, Anthropic, Google, and Azure endpoints. It matches requests by model, prompt hash, tools, temperature, and tenant policy, so repeated work returns fast while sensitive contexts stay isolated. Teams set TTLs, stale rules, encryption scopes, and bypass flags per route. Analytics show hit rate, latency saved, token spend avoided, and drift risk by provider. What changes for developers? Keep one integration, add cache headers, and watch fallback logic respect consent, residency, and audit needs. During rollout, canary keys compare fresh answers with cached copies before promotion. Prompt Cache cuts vendor calls, steadies p95 latency, and gives platform owners controls for cost, quality, and compliance.

out 1527 tok (+1354 thinking) latency 37.9 s

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

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",
    # model="kimi-k3.1-pro",  # 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 or Kimi K3.1 Pro?

Kimi K3.1 Pro is cheaper on the "Input / 1M tokens" row ($2 vs $3, 1.5× 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 against Kimi K3.1 Pro 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 and Kimi K3.1 Pro 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