Claude Opus 5.5 cuts prices. Does it cut the cost of work?

Anthropic released Claude Opus 5.5 on September 22 with a striking claim: at default settings, typical workloads cost 40% less than on Opus 5 in its own tests. That is not a promise that every customer's bill will fall by 40%. Anthropic's announcement.

The distinction matters if you are paying an AI system to fix code, prepare a report, or complete a business task. A lower rate helps. So does needing fewer attempts—and spending less time checking the result. Only the first appears directly on a price list.

What actually got cheaper

Anthropic's published comparison separates three changes. Standard input and output prices fall by 20% from Opus 5. Cache reads, which reuse previously processed input, fall by 60%. The larger 40% workload-saving figure also reflects Anthropic's account of more efficient task execution. It is a result the company reports, not one we have reproduced. Price comparison and methodology.

That makes the upgrade worth evaluating without making the headline saving a budget assumption. A workflow that reuses substantial context has a different cost mix from one that mostly generates fresh output. Retries can change that mix again.

Sol and Grok are already part of the comparison

GPT-6 Sol is no longer an upcoming API release: OpenAI's changelog records its release on September 22. Grok 4.7 was announced a day earlier, on September 21, with API availability. OpenAI release record, Grok announcement.

For teams building software around these models, the published base API rates per million tokens—the chunks of text providers meter—give a starting point:

• Claude Opus 5.5: $4 for input and $20 for output. Claude documentation.
• GPT-6 Sol: $2 for input and $10 for output at standard rates for prompts up to 272,000 input tokens; longer prompts cost more. OpenAI model documentation.
• Grok 4.7: $2 for input and $6 for output at its lower-context rates; requests above 200,000 tokens of context have higher rates. Grok model documentation.

Input is what you send; output is what the model generates. These are usage-based developer prices, not monthly chatbot subscriptions. The figures omit caching, tool charges and premium processing options. They are a rate-card comparison, not a cost estimate for the same job.

The cheaper attempt is not necessarily the cheaper result

Our reading: the useful unit is an accepted result, with the work needed to reach it included.

For a coding task, that means a change that passes the relevant tests and survives review—not simply a patch produced quickly. For a report, it means claims that can be checked against sources—not a convincing first draft.

A practical comparison would hold the assignment and acceptance criteria steady, then record the full bill, completion time, retries and human corrections. A low-cost attempt that needs substantial repair may lose its advantage. A more expensive attempt may justify itself if it reliably removes that repair work. Neither outcome is established by the published token prices.

Check the upgrade before changing the default

There is also a concrete migration issue. Anthropic's Opus 5.5 documentation lists breaking changes for existing integrations, including always-on thinking and errors for forced tool use. Swapping a model name is not sufficient evidence that an existing application still behaves correctly. Compatibility notes.

For a small team, the next step need not be a wholesale switch. Choose a repeatable task with a clear finish line, keep the current setup available, and compare the alternatives on that task. If the existing model already clears the bar, the newcomer should earn the disruption.

Opus 5.5 gives teams a reason to revisit that calculation. Sol and Grok belong in the same evaluation. The question worth answering is simple: which one leaves you with finished work—and how much did it take to get there?

Reporting note: This is source-based analysis, not a hands-on benchmark. Official sources were checked on September 23, 2026. We have not independently measured these models' comparative quality, speed or task costs.