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

Claude Haiku 5.5 vs DeepSeek V4 Pro (0813)

vs

Which one, when

claude-haiku-5-5 costs $0.1 input and $0.5 output against $1.32 and $3.96 for deepseek-v4-pro-0813, about 13x less on input and 8x less on output, with cache reads at $0.01 against $0.132. Both offer a 1000000-token context. claude-haiku-5-5 accepts image input and bills prompts above 100000 tokens at 5x, which still leaves it cheaper; deepseek-v4-pro-0813 is text only and allows 393216 output tokens against 128000. Pick claude-haiku-5-5 for volume and for images, and deepseek-v4-pro-0813 for very long text outputs.

Benchmarks

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

Above averageNo peer higherDeepSeek V4 Pro (0813)13 / 211 / 21
Claude Haiku 5.5 DeepSeek V4 Pro (0813) other models measured peer average ★ no peer scored higher
DeepSWE 1.1
N/A
62.7%
Cybergym
N/A
83.3%
GDPval-AA v2 Elo · 1508-1769 per Z.ai · 2026-09-04
N/A
1590
GPQA Diamond
N/A
92.4%
Agents' Last Exam
N/A
25.7%

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

Pricing

Claude Haiku 5.5 DeepSeek V4 Pro (0813) Δ
Input / 1M tokens $0.1 $1.32 0.076×
Output / 1M tokens $0.5 $3.96 0.13×
Cache read / 1M tokens $0.01 $0.132 0.076×
Cache write 1.25x (5m) / 2x (1h) no separate charge -

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)

Capabilities

Claude Haiku 5.5 DeepSeek V4 Pro (0813)
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 no fixed TTL (evicted when unused)
Minimum cached prefix 1024 tokens not published

Specs

Claude Haiku 5.5 DeepSeek V4 Pro (0813)
Input modalities text image text
Output modalities text text
Released 2026-10-07 2026-08-13
Knowledge cutoff 2026-06 -
Context window 1M 1M
Max output 128K 393K
Thinking parameter output_config.effort reasoning_effort
Accepted values
output_config.effort
  • low
  • medium
  • high
  • xhigh
  • max
reasoning_effort
  • the model card documents low
  • high
  • max
Default medium -

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 · DeepSeek V4 Pro (0813)

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

DeepSeek V4 Pro (0813) passed · 3 sentences

Enabling reasoning causes the model to generate a hidden chain-of-thought with many additional tokens before producing the final answer, which sharply increases compute consumption per request. Those extra reasoning tokens are billed at the same or higher rates, so total usage doubled even though the volume of final outputs stayed similar. We can control this by adjusting reasoning effort, setting token limits, or routing only complex requests through reasoning mode.

out 308 tok (+226 thinking) latency 5.1 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

DeepSeek V4 Pro (0813) 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 `cur` was initialized to `0` and only counted adjacent matching pairs, so a run of length `n` produced `n - 1` (or `0` for a single element) instead of `n`. The code also reset to `0` on a change, when the new run should start at length `1`. Initializing `cur` and `best` to `1` fixes both the single-element case and runs ending at the last index.

out 1315 tok (+1130 thinking) latency 16.9 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

DeepSeek V4 Pro (0813) passed · 5/5 fields, guidance null

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

out 2155 tok (+2121 thinking) latency 26.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

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

DeepSeek V4 Pro (0813) passed · 121 words, 0 banned, 1 question

Introducing cross-provider prompt caching in our API gateway. Send a prompt once, and the gateway stores its computed prefix across Anthropic, OpenAI, and other LLM providers. Subsequent requests with the same prompt hit the cache, cutting latency and token costs while keeping outputs consistent across routing decisions and provider failovers. Teams can route identical prompts between providers without reprocessing shared context or lengthy system instructions. How much could you save on repeated prompt prefixes? The cache respects provider-specific key formats, handles TTLs automatically, and works with streaming and batch requests. Enable it with one configuration flag—no changes to your application code. Available today on all plans. Monitor cache hit rates, token savings, and provider-specific performance metrics in the live dashboard.

out 2845 tok (+2694 thinking) latency 25.5 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="deepseek-v4-pro-0813",  # 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 DeepSeek V4 Pro (0813)?

Claude Haiku 5.5 is cheaper on the "Input / 1M tokens" row ($0.1 vs $1.32, 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 Claude Haiku 5.5 against DeepSeek V4 Pro (0813) 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 DeepSeek V4 Pro (0813) 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