
On April 16, Anthropic released Claude Opus 4.7 and held its headline rate unchanged. On the same day it removed bundled tokens from enterprise plans. Businesses running Claude workloads are paying more than they were on April 15.
On April 16, 2026, Anthropic released Claude Opus 4.7 and held its headline rate at $5 per million input tokens and $25 per million output tokens, the same figures listed on its pricing page before the release. On the same day, the company completed its elimination of the token allowance previously bundled into enterprise seat plans, moving all enterprise customers to a model where every token is billed at API rates on top of a $20 per employee per month base fee. The net result: businesses running Claude workloads are paying more than they were on April 15, without receiving a price increase notice.
The tokenizer change
The mechanism is the tokenizer: the component that converts raw text into the numerical units the model processes and bills for. Anthropic's own documentation, states that the new tokenizer in Opus 4.7 "may use roughly 1x to 1.35x as many tokens when processing text compared to previous models." The source of the increase is finer-grained subword segmentation: the same input is broken into more, smaller pieces.
The impact is not uniform. Analysis published by tokencost.app found the word-to-token ratio changed from approximately 750,000 words per million tokens on Opus 4.6 to approximately 555,000 words per million tokens on Opus 4.7, a roughly 35% reduction in how much text a fixed token budget covers. The effect is heaviest on structured data formats: JSON, XML, and YAML inputs hit the upper bound of the 1.35x range. Python and JavaScript land between 1.2x and 1.3x. Plain English prose sees minimal change.
Anthropic's own docs flagged one additional implication for developers: the API endpoint used to pre-compute token counts, /v1/messages/count_tokens, now returns different values for Opus 4.7 than it did for Opus 4.6. Any application that cached token estimates based on the previous model's behaviour is now underestimating costs.
The enterprise bundle removal
The second change, also effective April 16, completed a transition Anthropic had begun in November 2025. Under previous enterprise plans (Chat-only, Standard, and Premium seat tiers) the monthly per-seat fee included a token allowance, covering usage up to a threshold at no additional charge. Those plans are no longer available for new contracts. Existing customers have been moving to the $20 per employee per month structure at each renewal cycle since November.
The Register reported the change on April 16 under the headline "Anthropic ejects bundled tokens from enterprise seat deal." Fredrik Filipsson, co-founder of Redress Compliance, told Gizmodo the change could triple costs for some enterprise customers. Adrien Laurent, CEO of IntuitionLabs, offered a different reading: "Most users were in extra usage territory anyway, well beyond what the base seat fee covered."
Anthropic confirmed to The Register that the transition began in November 2025, but offered no public explanation for eliminating the bundled allowance.
Independent measurements
Simon Willison, a developer and researcher, published direct before-and-after token count comparisons on April 20 at simonwillison.net, using Anthropic's own /count_tokens API endpoint.
His results exceeded the ceiling Anthropic had stated. A system prompt that consumed 5,039 tokens on Opus 4.6 consumed 7,335 tokens on Opus 4.7, a 1.46x multiplier. A high-resolution image (3,456 by 2,234 pixels, 3.7 megabytes) went from 1,578 tokens to 4,744 tokens, a 3.01x increase, which Willison attributed primarily to Opus 4.7's expanded resolution support rather than the tokenizer change alone. A 30-page PDF came in at 1.08x: 56,482 tokens on 4.6 versus 60,934 on 4.7.
The 1.46x figure sits above the 1.35x ceiling in Anthropic's documentation. Separate independent testing published by claudecodecamp.com, which measured real Claude Code files using the same /count_tokens endpoint, reported multipliers up to 1.47x on technical documentation inputs and a weighted ratio of 1.325x across seven real-world file types.
The reaction
Developer backlash began within hours of the April 16 release and spread across Reddit, Hacker News, and X.
A post on r/ClaudeAI titled "Opus 4.7 is not an upgrade but a serious regression" accumulated approximately 2,300 upvotes within 24 hours, according to reporting by botmonster.com and dnyuz. Claude Pro subscribers reported exhausting their usage limits after as few as three questions, an outcome attributed to the tokenizer inflation compounding with the model's adaptive thinking feature, which consumes tokens automatically.
On Hacker News, thread 47816960 drew hundreds of comments. User "hgoel" wrote: "I hit my 5 hour limit within 2 hours yesterday... ~5% consumption per exchange vs. 1-2% previously."
On X, developer and writer Josh Pigford posted: "opus 4.7 is first time I've thought anthropic may be moving too fast." On The Register's forums, an anonymous enterprise user wrote: "we got the global email 'you're using it too much' and 'here are the costs.'"
The phrase that circulated widely across platforms: "stealth price increase." The rate card is unchanged. The bill is not.
Boris Cherny, creator of Claude Code at Anthropic, responded publicly after the initial backlash. He confirmed that bugs present in the initial Opus 4.7 release had been addressed and stated that rate limits were being raised. An Anthropic product manager acknowledged the team was "sprinting on tuning" adaptive thinking behaviour.
What Anthropic published and what it didn't
The tokenizer change is disclosed in Anthropic's official documentation under a section titled "Updated token counting," within a broader "Breaking changes" heading on the "What's New in Claude Opus 4.7" page at platform.claude.com. The docs include a migration checklist advising developers to update their max_tokens parameters to allow additional headroom.
Anthropic published no dedicated blog post explaining the billing implications of the tokenizer change. The launch blog post covered capability improvements. No proactive email to API customers specifically addressing the cost impact has been publicly confirmed. The company did not respond to requests for comment on whether such communications were sent.
The enterprise bundle removal received similar treatment. Its disclosure was a support documentation update, not a customer announcement. Its public profile came from The Register's April 16 coverage.
Businesses running workloads on the Claude API should check their token counts directly using Anthropic's /v1/messages/count_tokens endpoint before assuming 4.6-era estimates remain accurate. Those on enterprise contracts that renewed after November 2025 will already be on usage-based billing; those still on legacy seat plans should verify their renewal terms.
