Update (September 2026): Anthropic did not raise Claude Sonnet 5 from $2 / $10 to $3 / $15 on September 1. The company now lists $2 per million input tokens and $10 per million output tokens as the standard Sonnet 5 price. If you scheduled a 50% price increase into your forecasts or code, remove it. This page keeps the old URL because people still search for the announced August 31 expiry; the important answer is that the planned increase was canceled.
The more useful lesson is not that one forecast was wrong. It is that an AI price change can be announced, modeled, scheduled in code, and then canceled before its effective date. A pricing table behaves like a dependency with version history, provenance and reversals — not a constant you copy from a launch post once.
What changed after August 31
Sonnet 5 launched at $2 / $10 with an announced introductory window. Anthropic's current pricing documentation now says that rate became the standard price and that the previously scheduled September 1 increase will not occur.
| Monthly Sonnet volume (in / out) | Planned $3/$15 bill | Current $2/$10 bill | Avoided increase |
|---|---|---|---|
| Solo dev — 20M / 6M | $150 | $100 | $50 |
| Small team — 150M / 45M | $1,125 | $750 | $375 |
| Product with agent features — 1B / 300M | $7,500 | $5,000 | $2,500/mo |
If you scheduled the increase, undo it explicitly
- Price tables: remove or supersede the September 1 $3/$15 effective-dated row instead of silently editing history.
- Budgets: reset forecasts that multiplied the Sonnet line by 1.5.
- Customer quotes: do not pass through an increase that never happened.
- Routing rules: re-run the Haiku/Sonnet/Opus economics using the current rate card rather than the announced-but-canceled one.
The cancellation is exactly why hardcoded prices are dangerous
A robust cost system needs effective dates and a way to cancel future rates before they become active. The wrong implementation pattern is a conditional such as if (date >= '2026-09-01') sonnet = 3/15. The safer pattern is a versioned price source with provenance, a verification date, and a reconciliation step against the provider invoice.
This is also why UsageBox keeps the usage quantity separate from provider pricing. A token event that happened in August should remain the same token event after Anthropic changes, postpones or cancels a price change. Price the quantity in the system that owns your provider rate book; keep the underlying usage record stable.
What to monitor next
Provider pricing is still volatile even when a specific increase disappears. Watch the official pricing page for model launches, cache multipliers, batch discounts, regional premiums and retirements. Then reconcile your computed cost against the actual provider bill rather than assuming the rate table stayed correct because the code compiled.
For the current Claude model rate card and limits, see the Claude API pricing guide. For the implementation pattern behind price-table updates, see why hardcoded LLM pricing tables go stale. If you want the usage ledger independent from the provider bill, start with AI API billing reconciliation.