Claude Sonnet 5 Intro Pricing Ends August 31: Act Before the Rate Hike

Anthropic's Claude Sonnet 5 introductory pricing ends August 31, with rates rising 50% on September 1 to $3 per million input tokens and $15 per million output tokens, but the new tokenizer generates roughly 30% more tokens than Sonnet 4.6, effectively doubling costs for unoptimized workloads. Anthropic recommends enabling prompt caching and using the Batch API to mitigate the increase.

Claude Sonnet 5 launched June 30 with introductory pricing: $2 per million input tokens, $10 per million output. On September 1, that becomes $3 and $15 — a 50% rate increase. You have 29 days. But the rate card is only half the story: Sonnet 5 ships with a new tokenizer that generates roughly 30% more tokens for the same text, compared to Sonnet 4.6. If your workloads haven’t been benchmarked yet, you don’t know what your September bill looks like. Now’s the time to find out — and to do something about it. The Double Hit The pricing deadline gets the attention. The tokenizer doesn’t — and it should. Sonnet 5 uses a newer-generation tokenizer, the same one introduced with Opus 4.7. English prose generates 33–42% more tokens than it would in Sonnet 4.6. Python code comes in at 27–28% more. The practical average across mixed workloads is roughly 30% inflation. Do the combined math: a workload that ran at $X on Sonnet 4.6 will run at approximately $X × 1.30 tokenizer × 1.50 rate increase = $X × 1.95 on Sonnet 5 at standard rates, with no optimizations. That’s a near-doubling of the effective cost — not the 50% the rate change alone implies. Anthropic has documented this. It’s in the release notes. But launch coverage focused on the performance benchmarks, and the tokenizer detail got buried. | Scenario | Input per 1M | Output per 1M | |---|---|---| | Sonnet 5 intro now | $2.00 | $10.00 | | Sonnet 5 standard Sep 1 | $3.00 | $15.00 | | Sonnet 5 cache read | $0.30 | — | | Sonnet 5 Batch Sep 1 | $1.50 | $7.50 | | Sonnet 5 Batch + cache read | $0.15 | — | Step 1: Measure Before You Optimize Don’t guess at the impact. Measure it on your actual content. The Anthropic Console has a tokenizer counter; use it on a representative sample of your production prompts — both system prompts and user messages — and compare against your Sonnet 4.6 baselines. Alternatively, instrument your API calls and compare input tokens on equivalent requests across both models. Once you have a measured multiplier for your content type, you can project September costs accurately. Teams running prose-heavy workloads legal, docs, support should expect closer to 40% inflation. Code-heavy pipelines will see 25–28%. Mixed codebases land around 30%. Step 2: Enable Prompt Caching Prompt caching is the highest-leverage optimization available before September 1. Cache hits cost 10% of the base input rate — at standard pricing, that’s $0.30 per million tokens versus $3.00. A 90% reduction on your stable prefix content. Enabling it requires adding a cache control field to stable content blocks. See Anthropic’s prompt caching documentation https://platform.claude.com/docs/en/build-with-claude/prompt-caching for the full reference. response = client.messages.create model="claude-sonnet-5-20260630", max tokens=1024, system= { "type": "text", "text": "Your system prompt here...", "cache control": {"type": "ephemeral"} } , messages= {"role": "user", "content": "User message here"} Verify cache hits in production print response.usage.cache creation input tokens print response.usage.cache read input tokens The default TTL is 5 minutes. For longer sessions or document analysis, request the 1-hour TTL: {"type": "ephemeral", "ttl": "1h"} . Minimum cacheable block is 1,024 tokens. Break-even is low: if the same prefix appears more than twice within the TTL window, caching wins. Track cache read input tokens in production to confirm you’re getting hits. Step 3: Route Async Work Through the Batch API The Batch API https://platform.claude.com/docs/en/build-with-claude/batch-processing applies a 50% discount to both input and output tokens for asynchronous processing. At September standard rates, that means $1.50 input and $7.50 output per million tokens — instead of $3.00 and $15.00. If your workload includes anything that doesn’t need a real-time response — evaluation pipelines, nightly document processing, bulk content generation, data extraction — this is where to route it. Batches support up to 10,000 requests, results returned within 24 hours. Use the custom id field on each request to match results back to inputs, since results return in completion order, not submission order. Stacked with prompt caching, you can get cache-hit input cost down to $0.15 per million tokens on async workloads. That changes the economics significantly for high-volume pipelines. What You’re Getting for the Price This isn’t a pure tax. Sonnet 5 is a meaningfully better model, especially for agentic work. On SWE-bench https://www.swebench.com/ Pro, it scores 63.2% versus 58.1% for Sonnet 4.6. Terminal-Bench 2.1 shows a 13.4-point gain — the largest practical jump in the suite, reflecting better multi-step tool use. FrontierCode v1 more than doubled: 38.8% from 15.1%. For teams running coding agents or browser automation, those gains are real. For high-volume, cost-sensitive, single-turn workloads where quality differences are marginal, the calculus is less clear — which is exactly why measuring first matters. The Bottom Line Twenty-nine days. The deadline is firm — no public signal from Anthropic of any extension. Teams that benchmark and optimize now lock in the current intro rates while they test. Teams that wait pay full price from day one in September. The three-step playbook: measure your tokenizer delta this week, enable prompt caching on your system prompts, and route async jobs to the Batch API. Full pricing details are in Anthropic’s pricing documentation https://platform.claude.com/docs/en/about-claude/pricing . This is a tax on inaction. Run the numbers before August ends.