Anthropic released Claude Opus 4.7 in mid-April, bringing a new SWE-bench Pro record of 64.3% on coding capability and a rarely noticed underlying change: the new tokenizer maps the same input text to more tokens, with the increase ranging from 1.0× to 1.35× — about 35% higher for English content. This means that for APIs billed at the listed price, real bills are quietly inflating.
Tokenization is the first step in a large-model's text processing, slicing input text into a token sequence. Different tokenizers have different slicing granularity; the same passage might slice into 1,000 tokens or 1,350. Anthropic has changed the tokenizer for the Opus family, but hasn't lowered the per-token price — the result: every batch of text users process consumes more tokens, at the same unit price.
At Opus 4.6's pricing, suppose a 5,000-word English code-review task consumes 10,000 tokens — that costs $0.05. Switch to Opus 4.7 and the same task may consume 13,500 tokens, costing $0.0675 — a 35% jump. This number is invisible on a single call, but in production systems running millions of tokens per day, monthly bill differences easily reach thousands of dollars.
More notably, this increase is not uniform. Structured code, repetitive logs, and templated documents tend to see larger token increments; creative writing and dialogue text see smaller ones. If your application is code-heavy, real cost inflation will significantly exceed the official average of 35%.
Tokenizer changes have always been the elephant in the room. Claude Opus 4.7 is no isolated case — every historical tokenizer change has brought implicit cost reassessment, but most have stayed within 5%. This time, a 35% jump is large enough to invalidate carefully built cost models.
Facing a tokenizer change, the most pragmatic approach is to re-measure token consumption with real input samples and build a cost baseline based on actual content. For high-frequency call scenarios, sample a typical batch, measure actual token differences using both Opus 4.6 and Opus 4.7 API endpoints, and derive the real inflation coefficient. Tokenization is foundational infrastructure for large models; its changes should not come as a surprise to users. The only reliable approach is to let your own data speak.