Claude Opus + Extended Thinking — Cost Runaway
Opus 4.6 outputs at $75/M tokens. Extended thinking counts as output. A 32K thinking budget = $2.40 per request just for thinking. Bills explode when Opus + high thinking budget is used at scale. Fix: right-size the budget, use Sonnet for most work, cache aggressively, alert on cost anomalies.
Rule of thumb: Sonnet 4.5 with 10K thinking = $0.15/request. Opus 4.6 with 32K thinking = $2.40/request (16× more). Reserve Opus for genuinely hard problems (proofs, high-stakes analysis). Cap Opus thinking budget at 16K unless justified. Alert when any request exceeds $1. Cache aggressively to reduce input side.
The Cost Math
| Config | Thinking cost | Notes |
|---|---|---|
| Opus 4.6, 32K budget | Up to $2.40 | 32,000 × $75/M |
| Opus 4.6, 16K budget | Up to $1.20 | 16,000 × $75/M |
| Opus 4.6, 8K budget | Up to $0.60 | 8,000 × $75/M |
| Sonnet 4.5, 32K budget | Up to $0.48 | 32,000 × $15/M |
| Sonnet 4.5, 10K budget | Up to $0.15 | 10,000 × $15/M |
| Haiku 4.5, 5K budget | Up to $0.025 | 5,000 × $5/M |
These are worst cases (full budget used). Actual usage is often 40-70% of budget. But at scale, worst-case × 10K requests/day = real money.
The Symptoms You're Seeing
Monthly bill: $500 → $18,000 after enabling Opus thinking → 36× jump; unmanaged budget expansion Per-request usage.output_tokens shows 8,000-30,000 regularly → Thinking dominating output tokens Cost per user query: $0.02 (Sonnet) → $2.40 (Opus 32K thinking) → Direct 100× multiplier Alerts firing on account balance → Reactive; too late Team debating: "does the answer quality justify 100× cost?" → The right conversation, but usually starts too late Rate limit hits despite low RPM → TPM (tokens per minute) limits hit before RPM
What Actually Causes Runaway
Fixes That Work (Tested Nov 2026)
1Task-Sized Budget + Model Selection
2Cost Estimation Before Request
3Aggressive Caching + Cost Observability
Estimate cost of ONE request, then multiply by projected daily volume. Sonnet at 10K daily requests with 5K thinking = ~$1,000/day. Opus same setup = ~$5,000/day. Whether it's worth 5× depends on downstream value. Make this decision with data, not vibes.
Preventing This Error Going Forward
- Default to Sonnet, escalate to Opus explicitly. Not the other way around.
- Cap thinking budget by task category. 32K only for justified cases.
- Estimate max cost before every request. Fail loud if over ceiling.
- Log actual cost per request. Alert on outliers immediately.
- Cache aggressively. Cuts input side by 90% at high scale.
- Set org-level spend limits in console. Hard cap as last resort.
- Run cost postmortem weekly. Which endpoints drive spend?
Researcher · AI Error Hub
Frequently Asked Questions
Genuinely hard reasoning: novel proofs, cutting-edge research assistance, high-stakes financial analysis, medical decision support (with human review). If a downstream decision hinges on getting the reasoning right and the cost of wrong is > $10, Opus pays off. For content generation, chatbots, summaries: Sonnet is almost always the correct choice.
Yes — thinking and redacted_thinking blocks appear in response.content. Their token count is included in usage.output_tokens. You can inspect what Claude thought about (useful for auditing whether thinking budget is well-spent).
No — caching only affects INPUT tokens. Thinking is generated fresh each request (that's the point). Caching still helps because Opus input is $15/M; 100K cached tokens = $1.35 saved vs uncached per request.
No streaming interrupt for thinking. Set the budget at request time; Claude respects it as a cap. If Claude would exceed budget, it wraps up early. So over-shooting the budget cap is impossible — but Claude might use the full amount even for simple queries if budget is very high.
Often yes. Baseline Sonnet without thinking is $3/M input, $15/M output — plenty capable for chat, extraction, summarization, most analysis. Enable thinking selectively for reasoning-heavy queries. A/B test with/without; measure quality delta vs cost.
Related Errors
Control Claude Spend at Scale
Weekly deep dives on cost tuning, model selection, and thinking budget math. 12,000+ developers subscribe.
Subscribe Free →