New Sign up free, 10 calls on us. Up to $1, no card needed.

Claude Haiku 5.5 vs Kimi K3

vs

Which one, when

claude-haiku-5-5 costs $0.1 input and $0.5 output against $3 and $15 for kimi-k3, 30x less on both, with cache reads at $0.01 against $0.3. Context is about the same (1000000 and 1048576). kimi-k3 accepts video input and allows up to 1048576 output tokens against 128000; its thinking cannot be switched off, where claude-haiku-5-5 lets you disable it. claude-haiku-5-5 bills prompts above 100000 tokens at 5x, which still leaves it far cheaper. Pick claude-haiku-5-5 for high-volume work, and kimi-k3 for video input or very long outputs.

Benchmarks

Claude Haiku 5.5: the vendor has not published benchmark scores.

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

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

Pricing

Claude Haiku 5.5 Kimi K3 Δ
Input / 1M tokens $0.1 $3 0.033×
Output / 1M tokens $0.5 $15 0.033×
Cache read / 1M tokens $0.01 $0.3 0.033×
Cache write 1.25x (5m) / 2x (1h) - -

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 78 chat models on this billing unit (log scale)

Claude Haiku 5.5 · $0.1 Kimi K3 · $3
$0.05 · Qwen3 VL Flash $30 · GPT-5.4 Pro

Capabilities

Claude Haiku 5.5 Kimi K3
Tool calling yes yes
Thinking control configurable always on
Structured output yes yes
Prompt caching explicit (you mark the prefix) implicit (automatic)
Cache lifetime 5m default, 1h option not published
Minimum cached prefix 1024 tokens not published

Specs

Claude Haiku 5.5 Kimi K3
Input modalities text image text image video
Output modalities text text
Released 2026-10-07 2026-07-16
Knowledge cutoff 2026-06 -
Context window 1M 1M
Max output 128K 1M
Thinking parameter output_config.effort reasoning_effort (top-level; the thinking object is not accepted)
Accepted values
output_config.effort
  • low
  • medium
  • high
  • xhigh
  • max
reasoning_effort
  • low
  • high
  • max
Default medium max

Specs are transcribed from each vendor’s documentation; a row a vendor does not publish is left out rather than inferred. Full sources: Claude Haiku 5.5 · Kimi K3

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

Claude Haiku 5.5 passed · 3 sentences

Enabling reasoning makes the model generate a long internal chain of thought before its answer, and those thinking tokens are billed as output tokens, which cost several times more than input tokens. The model often produces many times more output per request than it did without reasoning, so the per-call cost rises even when the visible answer looks about the same length. Because that extra spend scales with every request, the bill roughly doubled, and we can control it by setting reasoning budgets, using reasoning only for tasks that need it, or routing simpler requests to a non-reasoning model.

out 332 tok (+159 thinking) latency 2.9 s

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

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

Claude Haiku 5.5 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 `cur` counts adjacent equal *pairs*, not run *elements*. A run of k equal items produces k−1 matching pairs, so the function returns one less than the true length, and a single-element input produces no pairs at all, so it returns 0 instead of 1. Resetting `cur` to 0 on a mismatch compounds this by starting every run one step behind. The fix starts both `cur` and `best` at 1 (a non-empty list always has a run of at least one element), resets `cur` to 1 on a mismatch, and updates `best` after every element rather than only inside the equal-branch. The empty-list guard keeps the function from returning 1 for `[]`. […]

out 1012 tok (+591 thinking) latency 6.0 s

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

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

Claude Haiku 5.5 passed · 5/5 fields, guidance "Formal guidance withheld pending the Q4 "

```json { "company": "Meridian Robotics", "quarter": "September quarter", "revenue_usd_m": null, "growth_pct": 11, "guidance": "Formal guidance withheld pending the Q4 close" } ``` Notes: The text gives revenue as 412 but doesn't state the currency, so I left `revenue_usd_m` as null. Growth is "eleven and change," so 11 is an approximation.

out 725 tok (+572 thinking) latency 4.6 s

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

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

Claude Haiku 5.5 passed · 120 words, 0 banned, 1 question

**Introducing Prompt Cache Sync, the newest feature in GatewayOne.** Teams routing requests across OpenAI, Anthropic, and Google have often paid to process the same long system prompts again and again. Now the gateway stores those prompts once and reuses them wherever they appear, regardless of provider. Repeated context is matched by content hash, so cached prefixes return faster and cost less, with no changes to your application code. How much could this save your team? Enable Prompt Cache Sync from the dashboard, and your next billing report will show the difference. Cache entries follow your existing retention settings and can be purged per project at any time. Availability begins this week for all Scale and Enterprise plans worldwide. Start today.

out 2164 tok (+1929 thinking) latency 9.9 s

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

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="claude-haiku-5-5",
    # model="kimi-k3",  # 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, Claude Haiku 5.5 or Kimi K3?

Claude Haiku 5.5 is cheaper on the "Input / 1M tokens" row ($0.1 vs $3, 30× 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 Claude Haiku 5.5 against Kimi K3 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 Claude Haiku 5.5 and Kimi K3 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