Let’s talk about the price hike that never showed up on the pricing page.
There is a moment every business owner knows. You order the same thing you always order. The price on the board hasn’t moved. But the serving is smaller, the wrapper is thinner, and somewhere between the kitchen and the table, the portion shrank without anyone announcing it. Economists gave it a name. Shrinkflation. The price stays honest. The unit of measure does the lying.
The AI industry just discovered the same trick. And because it’s a machine doing it, almost nobody noticed until the bill arrived.
Here’s what happened. Anthropic released Claude Opus 4.7. Same price as Opus 4.6 — five dollars per million input tokens, twenty-five per million output. Same numbers, same page, same headline. No announcement of a price increase. No email. Just a changelog note buried in the migration guide: the new model uses an updated tokenizer.
Most people reading that line will glaze over. Tokenizer. Sounds like plumbing. It isn’t plumbing. It’s the meter.
A tokenizer is the thing that decides how many tokens your words are worth before the model ever sees them. Think of it as the guy at the weighbridge who decides what your load weighs. The new tokenizer in Opus 4.7 is more aggressive. The same sentence you typed yesterday now produces more tokens. More tokens, bigger bill. Same price per token. Different total.
Independent cost-tracking firms ran the numbers. Ramp’s analysis flagged an effective increase of around twenty-seven percent. Finout and CloudZero measured up to thirty-five percent more tokens on identical text. Developers measured their own sessions on Reddit and Hacker News — twenty, thirty, sometimes sixty percent more expensive depending on the work. Anthropic didn’t dispute any of it. The tokenizer change is in their own release notes. They just didn’t call it what it is.
A price increase.
Now, I’m not going to stand here and pretend Anthropic is uniquely evil. Compute is brutal. The subsidized era was always going to end. Companies that burn billions on inference have to find the money somewhere. Fine. But there’s a difference between raising your price and changing the unit of measurement. One is a business decision. You see it. You rage about it. You can shop around. The other is a quiet redefinition of the deal you thought you made.
And that is the pattern worth naming, because this is not a one-off. This is the playbook.
Watch what’s happening across the whole industry. The headline wars are all about the sticker — who’s cheaper per token, who’s cutting prices, who’s giving away free tiers. That’s the visible layer, and most of it is theatre. The real money moves are happening in the layers you can’t see: the tokenizer, the reasoning-effort settings, the context compression, the shift from flat subscriptions to metered credits, the usage-based billing where the price is per something you cannot count yourself. The interface changed. The incentive did not.
Here’s the part people are missing. It’s not just that the bill went up. It’s that the bill can no longer be verified.
With a normal product, you can check. The loaf is smaller — you can weigh it. The phone plan costs more — you can read the contract. But tokens are not something you can count with your hands. The meter belongs to the seller. The definition of a token belongs to the seller. The tokenizer that produces them belongs to the seller. When the unit of account is proprietary and opaque, the invoice is not a statement. It is a claim you have to take on faith.
And that is where consent dies. Not in the dramatic moment. In the boring one. You agreed to a price. The price didn’t change. But the thing you were actually buying — a unit of work, a piece of outcome, a completed task — quietly became more expensive, and nothing in the transaction required your permission, or even your knowledge.
This is the oldest extraction move in commerce, wearing a tokenizer. Shrinkflation used to be a bakery problem. Now it’s an intelligence problem, running at the layer where every business on earth is being asked to build.
So what do you do with this? Three things, and they’re practical.
One. Stop reading the pricing page. Start reading the meter. Track tokens per request, per task, per outcome — not just the rate card. If your token counts creep up after a model migration without your prompts changing, that’s not a bug. That’s the bill telling you the truth.
Two. Pin the unit of measurement in your contracts, not just the price. When you negotiate, ask the vendor to guarantee token counts for defined workloads, or at least to actually tell you when the tokenizer changes. The vendors who refuse are telling you something.
Three. Measure outcomes, not inputs. The only number that matters is cost per completed job — the report written, the ticket resolved, the code merged. If the machine gets smarter and the price per token stays flat but the tokens per job go up, you haven’t bought an upgrade. You’ve bought a tax.
And the deeper principle, the one that survives all of this: the human has a right to a stable unit of account. You cannot consent to a deal you cannot measure. You cannot audit a bill you cannot re-count. When the meter is the seller’s black box, you are not a customer. You are a tenant on their meter, and the rent can change at any time without a signature.
The machine is getting smarter. Good. But it’s also getting more expensive in ways nobody will put on the pricing page. The people who come out of this decade whole will be the ones who watched the meter, not the sticker.
Because the sticker was never the deal.
The meter was.