Claude Sonnet 5 API Pricing: Migration Risks, Token Costs, and Opus Routing

TLDR

Claude Sonnet 5 is live as claude-sonnet-5: 1M context, 128k max output, and $2 / $10 per MTok input/output introductory pricing through August 31, 2026. Standard pricing is $3 / $15 per MTok after that.

For Sonnet 4.6 teams, this is not a simple model-ID swap. Re-baseline output tokens, effort level, prompt-cache hit rate, HTTP 400 rate, and Opus 4.8 fallback rate before routing production traffic.

Claude Sonnet 5 API Migration Snapshot

Item	Claude Sonnet 5
API model ID	claude-sonnet-5
Migration target	Claude Sonnet 4.6 production workloads
Best first tests	Coding agents, tool use, long-context research, support automation
Context window	1M tokens
Max output	128k tokens
Intro API price	$2 / $10 per MTok input/output through August 31, 2026
Standard API price	$3 / $15 per MTok input/output after August 31, 2026
Key migration note	Adaptive thinking is on by default
Effort default	high on Claude API and Claude Code
Cost caveat	The new tokenizer can produce about 30% more tokens for the same text, so measure real workload cost
Required telemetry	effort, usage.output_tokens, cache hit/miss fields, request 400 rate, p95 latency

Key Takeaways

• Sonnet 5 is a migration decision, not just a newer model ID.
• Measure cost per solved task, not token price alone.
• Set effort intentionally; Sonnet 5 defaults to high on Claude API and Claude Code.
• Re-baseline prompt caching, output tokens, and HTTP 400 rate before production rollout.
• Keep Opus 4.8 in the eval set for high-effort agentic work.

What Actually Shipped

Anthropic's Claude Sonnet 5 announcement positions it as the next Sonnet-class production model. The practical surface in the Claude model overview and official pricing page points to the same takeaway: Sonnet, not Opus, is where many teams make daily routing, latency, and cost decisions.

What Public Discussion Shows

The hard facts come from Anthropic's docs. In Anthropic's published comparison, Sonnet 5 scores 63.2% on SWE-bench Pro versus 58.1% for Sonnet 4.6, reaches 80.4% on Terminal-Bench 2.1 versus 67.0%, and improves Humanity's Last Exam with tools from 46.8% to 57.4%.

Public discussion is useful for a narrower purpose: it shows what builders noticed first and which claims deserve retesting. TestingCatalog's launch-chart thread surfaced the benchmark conversation, Chubby's price/performance read framed the comparison question, and Kilo Code's developer-tool availability note showed early ecosystem movement.–

Source: @claudeai

The follow-up questions are more useful than the launch hype. The Hacker News discussion focused on token usage and cost curves, the r/singularity launch thread debated the Opus comparison, and r/ClaudeAI early impressions collected user-level reports. Treat those threads as signals, not specs.

Claude Sonnet 5 API Pricing

Claude Sonnet 5 pricing has two phases.

Period	Input price	Output price
Introductory pricing through August 31, 2026	$2 / MTok	$10 / MTok
Standard pricing after August 31, 2026	$3 / MTok	$15 / MTok

The table follows Anthropic's Claude pricing page.

The important detail is that per-token pricing is not the whole cost story. Anthropic's Claude Sonnet 5 documentation notes that the new tokenizer can produce approximately 30% more tokens for the same text. Treat that as an approximate planning number, not a fixed multiplier. The exact increase depends on content and workload shape, so teams should re-run token counting against their own production prompts.

For migration, use this routing metric:

Effective cost per solved task = (primary model cost + retry cost + fallback cost) / successful tasks

If Sonnet 5 completes more tasks with fewer retries or fewer Opus fallback calls, it can still be cheaper in practice. If token usage increases without improving completion quality, the lower headline price may not translate into lower workload cost.

Three Engineering Dark Corners

The migration risk is not only model quality. Three less-visible details can change production cost or reliability.

Adaptive thinking can turn into output-token spend

Claude Sonnet 5 uses adaptive thinking by default. Anthropic's extended thinking documentation states that thinking tokens are billed as output tokens, so a short final answer can still hide a large amount of billed reasoning work.

Standard control is not a fixed thinking budget. Anthropic describes effort as the thinking-depth control in the Claude migration guide and effort documentation, while the model overview lists high as the Sonnet 5 default on Claude API and Claude Code. For simple routing or deterministic classification, test lower effort levels such as low or medium, or disable thinking entirely, then verify latency, quality, and output-token usage.

Migration checklist:

• Log the actual effort setting with every eval run.
• Track usage.output_tokens, not only visible response length.
• Compare p50/p95 latency for Sonnet 4.6, Sonnet 5, and Opus 4.8.
• For simple routing or deterministic classification tasks, test lower effort levels or disable thinking entirely, then compare latency, output-token usage, and task accuracy.
• Watch for tasks where Sonnet 5 answers correctly but spends enough thinking tokens that Opus 4.8 becomes competitive.

Prompt caching must be re-baselined

For long-context research, support agents, and multi-step orchestration, Anthropic's prompt caching guide is often the biggest cost lever. Sonnet 5's new tokenizer can change the token count of the same prompt, so cached-input cost assumptions should be recalculated after migration. Cache behavior should also be re-verified independently by monitoring cache creation and cache read usage fields.

Do not assume that a prompt caching strategy tuned around Sonnet 4.6 will produce the same workload-level cost profile on Sonnet 5.

Migration checklist:

• Re-run token counting on all long prompts before switching traffic.
• Re-check cache breakpoints and cache-control placement.
• Monitor cache_creation_input_tokens and cache_read_input_tokens during the migration window.
• Alert on sudden cache-read drops or cache-creation spikes after changing the model ID.

Rejected sampling parameters are production-breaking 400s

Sonnet 5 is stricter about some sampling parameters than many older integrations expect. Anthropic's API release notes state that non-default temperature, top_p, and top_k return an HTTP 400 error. If your SDK wrapper hardcode sampling settings for every model, a rollout can fail at request time.

Migration checklist:

• Search the codebase for hardcoded temperature, top_p, and top_k.
• Add model-specific parameter validation before requests are sent.
• Canary the migration with error-rate alerts before full production rollout.
• Keep a Sonnet 4.6 fallback route until parameter validation is clean.

Claude Sonnet 5 vs Claude Sonnet 4.6

Claude Sonnet 5 is the natural upgrade candidate for teams already using Sonnet 4.6, but it should not be treated as a zero-review migration.

Area	What changes
Model ID	Change from claude-sonnet-4-6 to claude-sonnet-5
Thinking	Adaptive thinking is on by default
Manual extended thinking	Manual budget-token mode is removed
Sampling parameters	Non-default temperature, top\_p, and top\_k return HTTP 400 errors
Tokenizer	The same text can map to more tokens
Best improvement area	Coding, tool use, and agentic workflows

This matters most for applications with tight token budgets, deterministic sampling settings, or long prompts. Before replacing Sonnet 4.6 in production, rerun token counting, remove unsupported sampling parameters, and compare task success rates.

Sonnet 5 or Opus 4.8: The Routing Decision Tree

The strongest evaluation is not only Sonnet 5 vs Sonnet 4.6. For many teams, the real routing question is:

Should this workflow run on cheaper Sonnet 5 or stronger Opus 4.8?

Model	Standard input price	Standard output price	Best fit
Claude Sonnet 5	$3 / MTok	$15 / MTok	Fast, capable, lower-cost agentic workflows
Claude Opus 4.8	$5 / MTok	$25 / MTok	Complex agentic coding and enterprise work
Claude Sonnet 4.6	$3 / MTok	$15 / MTok	Existing Sonnet workloads not yet migrated

Use this simple decision tree:

• Route to Sonnet 5 when the workflow is medium complexity, latency-sensitive, or cost-sensitive.
• Route to Sonnet 5 when the task is repetitive enough that retries and review time can be measured reliably.
• Keep Opus 4.8 in the route when the task requires high-effort planning, multi-file coding, or expensive enterprise decisions.
• Keep Opus 4.8 in the route when a failed answer costs more than the token difference.
• Keep Sonnet 4.6 temporarily when production prompts depend on unsupported sampling parameters or manual extended thinking budgets.

The most common mistake is choosing by price alone. The better approach is to compare:

• solved-task rate
• average input tokens
• average output tokens
• retries per successful task
• latency per successful task
• human review time saved
• Opus fallback rate

Benchmarks: What To Trust And What To Retest

Anthropic positions Claude Sonnet 5 around coding, tool use, and agentic professional workflows. The third-party launch conversation, especially TestingCatalog's benchmark-chart thread and Chubby's price/performance comparison, turned that into a practical benchmark question: does Sonnet 5 close enough of the Opus gap to change production routing?

The numbers explain why that question matters. Sonnet 5 trails Opus 4.8 by 6.0 points on SWE-bench Pro and 2.3 points on Terminal-Bench 2.1, but beats Sonnet 4.6 by 5.1 and 13.4 points on those same tests. Chubby's chart also shows Sonnet 5 moving from roughly $2+ per task at low effort toward the $5-$7 range at higher effort, so effort settings should be part of the benchmark.

Source: @kimmonismus

Treat launch benchmarks as directional. Retest:

• Whether Sonnet 5 reduces retries in your own codebase.
• Whether adaptive thinking changes latency or output length.
• Whether the new tokenizer increases your effective bill.
• Whether prompt-cache hit rate stays stable after the tokenizer changes.
• Whether rejected parameters create HTTP 400 spikes in canary traffic.
• Whether Opus 4.8 still wins on high-effort tasks.

This is where the Hacker News cost discussion and r/ClaudeAI early user reports are useful. They are not the source of truth for model specs, but they reveal the questions real developers ask first: "Will this actually be cheaper?" "Does it use more tokens?" "When should I still pay for Opus?"

How To Evaluate Claude Sonnet 5 Yourself

Use the introductory pricing window to run a small but realistic test.

Build a 20-task evaluation set

Include real tasks, not toy prompts:

• bug fix in your repo
• tool-calling workflow
• long-context document synthesis
• support-ticket triage
• code review
• SQL or data analysis
• multi-step agent task

Run the same tasks on Sonnet 4.6, Sonnet 5, and Opus 4.8

Do not compare one-off outputs. Compare the same task set under the same prompt and review criteria.

If your evaluation stack uses coding agents, frameworks, or prompt-eval tools, the CometAPI Cookbook has GitHub-native integration guides for common developer workflows such as Claude Code, Codex, LiteLLM, LangChain, Langfuse, and Promptfoo.

Measure solved-task cost

Track:

• input tokens
• output tokens
• thinking-token-heavy requests, using output-token deltas and any available usage breakdown
• cache creation tokens
• cache read tokens
• retries
• latency
• HTTP 400 errors
• manual edits needed
• final pass/fail score

Watch migration constraints

When moving from Sonnet 4.6 to Sonnet 5:

• use claude-sonnet-5
• remove unsupported sampling parameters
• avoid manual extended thinking budgets
• retest max_tokens
• recount tokens with the Sonnet 5 tokenizer
• re-check prompt caching breakpoints
• alert on cache-read drops, cache-creation spikes, and HTTP 400 spikes

Decided by workload class

Use Sonnet 5 by default for medium-complexity production workflows. Keep Opus 4.8 for high-effort workflows until your own solved task data says otherwise.

What To Watch Next

Watch five things over the next few weeks:

1. Independent coding and agent benchmarks.
2. Real developer reports on token usage under the new tokenizer.
3. Reports on adaptive-thinking output-token spend.
4. Prompt-cache hit-rate behavior on long-context workloads.
5. Pricing or availability changes after the introductory window ends on August 31, 2026.

If your team already uses Sonnet 4.6, do not wait until the pricing window closes. July and August are the right time to test Sonnet 5 against your real workloads and decide whether to migrate.

FAQ

How much does Claude Sonnet 5 cost?

Claude Sonnet 5 costs $2/$10 per MTok input/output through August 31, 2026. Standard pricing is $3/$15 per MTok after that.

Is Claude Sonnet 5 a drop-in replacement for Sonnet 4.6?

Mostly, but not without testing. Update the model ID, remove unsupported sampling parameters, set effort, recount tokens, and re-baseline prompt caching.

Are Claude Sonnet 5 thinking tokens billed?

Yes. Thinking tokens are billed as output tokens, so monitor usage.output_tokens and latency.

Can I turn off adaptive thinking for simple tasks?

Yes. On Claude Sonnet 5, pass thinking: {"type": "disabled"} to turn thinking off. If the workload still benefits from reasoning, keep adaptive thinking enabled and use the effort parameter to control thinking depth. Sonnet 5 defaults to high effort, so latency-sensitive workloads should test lower effort settings such as low or medium.

Can prompt caching costs change after migrating to Sonnet 5?

Yes. Re-check cache breakpoints and monitor cache_creation_input_tokens and cache_read_input_tokens.

Will Sonnet 5 ignore unsupported sampling parameters?

No. Non-default temperature, top_p, and top_k return HTTP 400 errors. Remove hardcoded sampling parameters or add model-specific validation before production rollout.

Should I use Claude Sonnet 5 or Claude Opus 4.8?

Use Sonnet 5 for cost-sensitive workflows. Keep Opus 4.8 for high-effort agentic coding and complex enterprise tasks.

Test The Migration With CometAPI

You can test Claude Sonnet 5 through CometAPI and compare it with Claude Sonnet 4.6, Claude Opus 4.8, and other frontier models in one API workflow. For setup patterns across coding agents, automation tools, and evaluation frameworks, use the CometAPI Cookbook as a practical companion to your benchmark. Start with a small task set, measure cost per solved task, and choose the model that wins on your own workload.