claude-haiku-4-5 vs gemini-3.1-pro
Fourteen priced metrics for the same 2,000-in / 300-out call, with and without provider caching, and what TokenZero's cascade would do with the pair.
At list prices as of 2026-10-26, claude-haiku-4-5 costs $1.52 per million blended tokens on a 2,000-in / 300-out call against $3.30 for gemini-3.1-pro, 53.9% less. With the static prefix cached both drop further: $3.50 versus $4.90 per thousand calls. TokenZero routes only prompts its classifier scores simple and holds a 99.8% parity floor.
· Source: provider list prices verified in pricing table 2026-10-26; costs computed by the same code that signs TokenZero receipts
At a glance
- Cheaper per blended token
- claude-haiku-4-5 by 53.9% (computed)
- claude-haiku-4-5 blended $/1M
- $1.52 (computed)
- gemini-3.1-pro blended $/1M
- $3.30 (computed)
- Input $/1M
- $1.00 vs $2.00
- Output $/1M
- $5.00 vs $12.00
- Cached input $/1M
- $0.100 vs $0.200
- Cache discount
- 90% vs 90% (computed)
- Monthly at 100k calls
- $350 vs $760 (computed)
- Saved per 1M calls
- $4,100 (computed)
- Providers
- anthropic vs gemini
- Lifecycle
- active, no retirement announced vs active, no retirement announced
- Parity floor for routing
- 99.8% (shadow-eval breaker)
claude-haiku-4-5 vs gemini-3.1-pro: list prices and the same workload on both (USD, table 2026-10-26)
| Metric | claude-haiku-4-5 | gemini-3.1-pro | Delta |
|---|---|---|---|
| Provider · tier | anthropic · fast | gemini · frontier | different providers |
| Input $/1M | $1.00 | $2.00 | 50% gap |
| Output $/1M | $5.00 | $12.00 | 58.3% gap |
| Cached input $/1M | $0.100 | $0.200 | 90% / 90% off input |
| Cache write $/1M | $1.250 | no surcharge | |
| Minimum cacheable prefix | 4096 tokens | 1024 tokens | |
| Effective blended $/1M (2,000 in / 300 out) | $1.52 | $3.30 | claude-haiku-4-5 53.9% less |
| Per call | $0.00350 | $0.00760 | $0.00410 |
| Per month at 100k calls | $350 | $760 | $410 |
| …with the 1,500-token prefix cached | $350 | $490 | $140 |
| Long-context threshold | single tier | 200,000 tokens ($4.00 in / $18.00 out above) | |
| Processing tiers | speed: fast 2x | standard only | |
| Lifecycle | active, no retirement announced | active, no retirement announced | |
| Cheaper sibling (cascade target) | — | gemini-3.8-flash | |
| TokenZero cascade recommendation | none (cascade stays within one provider; cross-provider moves only on failover) | $4,100 saved per 1M calls if every call moved; $1,640 at a 40% simple-prompt share | 99.8% parity floor, breaker on |
Use either model through TokenZero
ANTHROPIC_BASE_URL=https://tokenzero.sh
GOOGLE_GEMINI_BASE_URL=https://tokenzero.sh
# keep your own keys; cache formatting on, routing advisory, signed receipt per callFree up to $500/month of routed spend; paid plans take 15% of verified savings with a 3x-ROI-or-$0 rule.
What is not on this page
Third-party quality scores (coding ELO, extraction accuracy, reasoning benchmarks) and per-model latency are not shown because TokenZero does not measure them; the numbers above are prices and the arithmetic on them. The latency benchmark shows what the gateway does measure.
Questions people ask
Which is cheaper, claude-haiku-4-5 or gemini-3.1-pro?
claude-haiku-4-5. At list prices as of 2026-10-26 it costs $1.52 per million blended tokens versus $3.30 for gemini-3.1-pro, a 53.9% gap on a 2,000-input / 300-output call. Per month at 100,000 calls that is $350 versus $760.
How much does prompt caching change the claude-haiku-4-5 vs gemini-3.1-pro gap?
Cached input costs $0.100 on claude-haiku-4-5 and $0.200 on gemini-3.1-pro per million. With a 1,500-token static prefix cached, 100,000 calls cost $350 and $490 respectively; TokenZero's formatter places the breakpoints and sets prompt_cache_key automatically.
Can TokenZero route gemini-3.1-pro traffic to claude-haiku-4-5 safely?
Not automatically: cascade routing stays inside one provider so the request shape, tools and keys are unchanged. Cross-provider moves happen only on failover when you name the fallback model and key. Use the calculator to price a manual migration of the workload.
Is claude-haiku-4-5 or gemini-3.1-pro being retired?
claude-haiku-4-5: active, no retirement announced. gemini-3.1-pro: active, no retirement announced. TokenZero audits flag retired ids and the gateway warns in X-TokenZero-Warning with the provider's replacement.
Related
Price your own workload on claude-haiku-4-5 and gemini-3.1-pro