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

Claude Haiku 5.5 vs Kimi K2.7 Code

vs

Which one, when

claude-haiku-5-5 is cheaper and larger on every limit: $0.1 input and $0.5 output against $0.95 and $4 for kimi-k2.7-code, 9.5x and 8x less, cache reads at $0.01 against $0.19, a 1000000-token context against 256000, and 128000 output tokens against 32768. It bills prompts above 100000 tokens at 5x, which still leaves it cheaper. kimi-k2.7-code accepts video input, and its thinking cannot be switched off. Pick claude-haiku-5-5 for cost and long inputs, and kimi-k2.7-code when you want Moonshot's coding model.

Benchmarks

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

Above averageKimi K2.7 Code1 / 5
Claude Haiku 5.5 Kimi K2.7 Code other models measured peer average ★ no peer scored higher
MLS-Bench-Lite
N/A
35.1%
MCP-Atlas
N/A
76%

Vendor-published: Alibaba (Qwen) Moonshot OpenAI Z.ai

Pricing

Claude Haiku 5.5 Kimi K2.7 Code Δ
Input / 1M tokens $0.1 $0.95 0.11×
Output / 1M tokens $0.5 $4 0.13×
Cache read / 1M tokens $0.01 $0.19 0.053×
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 K2.7 Code · $0.95
$0.05 · Qwen3 VL Flash $30 · GPT-5.4 Pro

Capabilities

Claude Haiku 5.5 Kimi K2.7 Code
Tool calling yes yes
Thinking control configurable always on
Structured output 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 K2.7 Code
Input modalities text image text image video
Output modalities text text
Released 2026-10-07 2026-06
Knowledge cutoff 2026-06 -
Context window 1M 256K
Max output 128K 33K
Thinking parameter output_config.effort
  • thinking.type
  • thinking.keep
Accepted values
output_config.effort
  • low
  • medium
  • high
  • xhigh
  • max
type
  • accepts only enabled
keep
  • accepts only all
Default medium thinking on with Preserved Thinking on

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 K2.7 Code

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

Enabling reasoning mode causes the model to generate an internal chain-of-thought before producing each answer, and that hidden reasoning text is billed like any other output. Those extra reasoning tokens typically add up to much more than the final response itself, so every API call now costs significantly more than before. Because our overall usage volume did not change, the doubled bill reflects that each query consumes roughly twice as many billable tokens.

out 259 tok (+174 thinking) latency 5.4 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 K2.7 Code 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 that the function counts *transitions* between equal neighbors instead of counting the items themselves, so a single-element list never enters the loop and returns `0` instead of `1`. Likewise, resetting `cur` to `0` on a mismatch forgets the current item that starts a new run, which causes runs that end at the last index to be undercounted. Initializing both `best` and `cur` to `1` and resetting `cur` to `1` fixes both issues.

out 410 tok (+222 thinking) latency 9.4 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 K2.7 Code passed · 5/5 fields, guidance "withheld pending the Q4 close"

```json { "company": "Meridian Robotics", "quarter": "September quarter", "revenue_usd_m": 412, "growth_pct": 11, "guidance": "withheld pending the Q4 close" } ```

out 721 tok (+663 thinking) latency 13.2 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 K2.7 Code passed · 120 words, 0 banned, 1 question

We're introducing Prompt Cache for our API Gateway, a new capability that stores prompt responses across multiple AI providers. By caching replies, you reduce redundant calls, lower latency, and cut costs without changing how you build. Teams using several model providers can now reuse identical prompt results instantly, keeping traffic consistent and budgets predictable. Responses are keyed by provider, model, and exact prompt, so you always get the right result. Configure TTL, hit thresholds, and eviction rules from a single dashboard. It fits into your existing routing and requires no code changes. Setup takes minutes and works with your current endpoints. Want to see how much latency and spend you can trim? Check the docs to enable Prompt Cache today.

out 2375 tok (+2235 thinking) latency 38.6 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-k2.7-code",  # 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 K2.7 Code?

Claude Haiku 5.5 is cheaper on the "Input / 1M tokens" row ($0.1 vs $0.95, 9.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 Claude Haiku 5.5 against Kimi K2.7 Code 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 K2.7 Code 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