- Claude Sonnet 5.5 keeps Sonnet 5 prices ($2 input, $10 output per million tokens) but halves cache reads to $0.10.
- Five changes can return errors on old code:
thinking: disabled, forced tool use, the old computer-use tool, some advisor pairings and thinking-block reuse. - Adaptive thinking is now on by default, so read content blocks by type and raise
max_tokens. - Do a staged rollout: swap the model ID, fix the 400 errors, then re-run your own evals and cost checks.
Claude Sonnet 5.5 is Anthropic’s mid-tier model, released on September 28, 2026 as the second model of the 5.5 family. It costs the same as Sonnet 5 on input and output, yet a few request settings that worked yesterday now return a 400 error.
That is the real story for developers. The headline numbers are easy to read off a pricing page. The breaking changes are not, and they usually show up in production logs on a Friday evening.
This guide covers the price, speed and context facts for Claude Sonnet 5.5, then walks through every migration change from the official docs with before-and-after code and a checklist you can paste into a ticket. All facts below come from Anthropic’s platform documentation as checked on October 31, 2026.
Claude Sonnet 5.5 at a glance
| Item | Value |
|---|---|
| API model ID | claude-sonnet-5-5 |
| Released | September 28, 2026 |
| Context window | 1M tokens |
| Max output | 128K tokens (300K on the Batch API with a beta header) |
| Input / output price | $2 / $10 per million tokens |
| Cache read | $0.10 per million tokens |
| Cache write | $2.50 (5 minute) and $4 (1 hour) per million tokens |
| Batch API | 50% discount on input and output |
| Thinking | Adaptive, on by default, default effort high |
| Latency tier | Fast |
| Knowledge cutoff | June 2026 |
It is available on the Claude API, Amazon Bedrock (as anthropic.claude-sonnet-5-5), Google Cloud, Microsoft Foundry and Claude Platform on AWS. Anthropic lists retirement as not sooner than September 28, 2027.
Claude Sonnet 5.5 pricing and speed compared
The prices did not move, except for one line. Prompt cache reads cost $0.10 per million tokens, which is half of what Sonnet 5 charged. If your app re-sends a long system prompt or a large document on every call, that line is where you will see savings.
| Model | Price per MTok (in / out) | Latency | Default effort |
|---|---|---|---|
| Claude Fable 5.1 | $10 / $50 | Slower | high |
| Claude Opus 5.5 | $4 / $20 | Moderate | medium |
| Claude Sonnet 5.5 | $2 / $10 | Fast | high |
| Claude Haiku 5.5 | from $0.10 / $0.50 | Fastest | medium |
Speed is a tier, not a number: the docs label Sonnet 5.5 “Fast”, Haiku “Fastest” and Opus “Moderate”. Real latency depends on your effort setting, prompt length and output size, so measure it on your own traffic. For a side-by-side with the larger model, read our Claude Opus 5.5 vs Sonnet 5.5 comparison, and for the cheapest tier see Claude Haiku 5.5 explained.
Watch the bill: thinking tokens are billed as output tokens. Because thinking now runs by default, the same prompt can cost more than it did on Sonnet 4.6 even though the price per token is unchanged.
The five breaking changes
These are the changes Anthropic lists for code that already runs on Sonnet 5. Each one is a 400 error or a silent behaviour change, so fix them before you flip traffic.
1. thinking: disabled is rejected
On Claude Sonnet 5.5, thinking: {"type": "disabled"} returns a 400 invalid_request_error. The lowest setting is between_tools, which turns off up-front thinking. It works at low, medium and high effort and returns an error at xhigh or max.
# Before (Claude Sonnet 5)
client.messages.create(
model="claude-sonnet-5",
max_tokens=16000,
thinking={"type": "disabled"},
messages=[{"role": "user", "content": "..."}],
)
# After (Claude Sonnet 5.5)
client.messages.create(
model="claude-sonnet-5-5",
max_tokens=16000,
thinking={"type": "between_tools"},
output_config={"effort": "high"},
messages=[{"role": "user", "content": "..."}],
)
With between_tools, you cannot change effort mid-conversation, and you cannot send display, budget_tokens or block_binding with it. Manual thinking budgets (enabled with budget_tokens) also return 400.
2. Forced tool use returns an error
Setting tool_choice to {"type": "any"} or {"type": "tool", "name": "..."} fails. Only auto and none work. If you relied on forcing a tool to get structured data, keep tool_choice on auto, add strict: true to the tool, or move the schema to structured outputs. To make the model call a tool, say in the prompt when it applies.
3. Thinking blocks are tied to a model and a conversation
Each thinking block records which model made it. Sonnet 5.5 reads blocks from Sonnet 5, Opus 4.8, Haiku 4.5 and earlier models, but not from Opus 5, Opus 5.5 or the Fable and Mythos models. Unreadable blocks are dropped before the model sees them, and dropped blocks are not billed.
The API also checks that nothing before a thinking block changed since it was produced. Keep conversations append-only: change instructions with mid-conversation system messages rather than by editing earlier turns. On accounts created on or after August 31, 2026, replaying a block after such an edit returns a 400 unless you set a fallback behaviour.
4. The old computer-use tool is not accepted
On the Claude API and Google Cloud (Google managed), a request that declares computer_20251124 returns a 400. Use the computer_toolset_20260801 toolset instead. Amazon Bedrock still accepts the older tool for this model.
5. The advisor tool rejects four advisors
If you pair Sonnet 5.5 with the advisor tool, Claude Opus 4.8, Claude Opus 4.7, Claude Sonnet 5 and Claude Haiku 5.5 are rejected as advisors.
The silent change: text between tool calls
Short progress notes the model writes between tool calls now arrive inside thinking blocks. An app that streams that text to users will go quiet between calls until you set a display value that returns it, or switch to between_tools. This does not fail a request, which makes it easy to miss in testing.
How to upgrade from Sonnet 5 step by step
- Change the model ID to
claude-sonnet-5-5in a staging config, not in code. - Search for
"disabled",tool_choice,temperature,top_pandtop_k. Setting a sampling parameter returns 400 on this model. - Read response content by block type. A reply can start with a thinking block, so code that reads
content[0].textbreaks. - Pass thinking blocks back unchanged in tool loops, including empty ones.
- Raise
max_tokens, because it covers thinking plus text. - Send 5 percent of traffic and compare errors, latency and cost per task.
- Re-run your effort sweep, since the best effort level may have shifted.
Coming from Sonnet 4.6 or earlier is a bigger jump. Thinking was off by default there, so also replace thinking budgets with an effort level, drop sampling parameters and set display: "summarized" if you show reasoning text. Models before 4.5 also need assistant prefills replaced. The official migration guide lists every group by starting model. If you want help, the docs even mention a Claude Code command, /claude-api migrate this project to claude-sonnet-5-5, that does the first pass for you.
What to test before you ship
| Area | Test | Pass condition |
|---|---|---|
| Errors | Replay 100 real prompts | No 400 responses |
| Parsing | Responses that start with thinking blocks | Text still extracted |
| Tools | Flows that used forced tool choice | Same tool called with auto |
| Streaming UI | Long multi-tool task | Progress text still visible |
| Cost | Cost per completed task | Within your budget |
The same habits that keep agents reliable apply here; our AI agents best practices post covers evals and monitoring, and the MCP stateless architecture guide matters if your tools run over MCP.
Who should move first
- Heavy prompt-cache users: half-price cache reads pay off quickly.
- Agent and coding workloads: Anthropic positions Sonnet 5.5 for agentic work, but verify on your own tasks.
- Apps with strict output formats: test the forced-tool change first.
- Small teams with simple chat features: a quick model-ID swap plus the thinking fix is usually enough.
Benchmark tables from third-party sites differ from each other, so treat them as a starting point and run a small eval on your own prompts. Official details live in the Sonnet 5.5 migration guide, the pricing page and the effort documentation.
Final thoughts
Claude Sonnet 5.5 is a cheap upgrade in price terms and a careful one in code terms. Swap the model ID in staging, fix the 400 errors from thinking and tool settings, then judge it by cost per finished task rather than price per token. Keep the migration checklist above in your pull request and the rollout stays boring, which is what you want.
Frequently asked questions
What is the Claude Sonnet 5.5 API model ID?
The Claude API model ID is claude-sonnet-5-5. On Amazon Bedrock it is anthropic.claude-sonnet-5-5.
How much does Claude Sonnet 5.5 cost?
Input costs $2 and output costs $10 per million tokens. Cache reads cost $0.10 per million tokens, and the Batch API gives a 50% discount on input and output.
Why does thinking disabled fail on Claude Sonnet 5.5?
The model no longer accepts it. Send thinking: {"type": "between_tools"} at low, medium or high effort, or use adaptive thinking.
Can I still force a tool call?
No. tool_choice of type any or tool returns a 400. Use auto with strict tool schemas or structured outputs, and say in the prompt when the tool applies.
How big is the context window?
The context window is 1M tokens with up to 128K output tokens. The Batch API supports up to 300K output tokens with a beta header.
Keep learning
Need help with testing, WordPress or SEO?
We help teams ship better software and grow their sites. Tell us what you are working on and we will suggest a clear next step.