TL;DR (July 2026): In seven weeks, the three biggest AI dev platforms all moved their flagship products onto the same billing object: the credit. GitHub cut Copilot over to AI Credits on June 1 (1 credit = $0.01, token-based drawdown, completions stay free). OpenAI ended the Workspace Agents free preview on July 6 and now meters every agent run in credits on top of seats. Anthropic switches Fable 5 to metered usage credits on July 20. Credits are winning because they let vendors sell a number that feels fixed while metering everything underneath it - and because per-seat pricing visibly breaks when one seat's agents do five seats' work. If you buy AI software, the seat is now the entry ticket and the credit meter is the bill; if you sell it, your pricing catalog just became production code.
None of the three vendors coordinated this, which is what makes it a structural story rather than a product story. Three different companies, three different products, one conclusion: neither pure per-seat nor raw per-token survives contact with agentic usage. Per-seat collapses because agents decouple work from headcount. Raw per-token terrifies buyers because nobody can picture a million tokens. The credit is the compromise both sides accept - and 2026 is the year it became the default.
The three cutovers, side by side
| Date | Vendor | What changed | The mechanism |
|---|---|---|---|
| June 1 | GitHub | All Copilot plans move from premium requests to usage-based billing | AI Credits, 1 credit = $0.01; drawdown computed from input/output/cached tokens at listed per-model rates; Pro includes $15, Pro+ $70, Max $200; completions and Next Edit stay free |
| July 6 | OpenAI | Workspace Agents free preview ends | Workspace credits drawn per agent run, on top of per-seat fees; GPT-5.5 rates published per million tokens, no consumption table for real workflows |
| July 20 | Anthropic | Fable 5 leaves included-in-subscription status | Usage credits at the $10/$50 per-MTok API rate once the included window ends |
The details differ; the shape is identical. A flat fee stops being the price and becomes the floor. The marginal unit of work gets a meter. And the meter's unit is never the token - it is a credit whose token-conversion rate the vendor controls per model, which means the vendor can reprice without changing the headline number. That last property is why credits won.
Why per-seat broke first
The clearest formulation of the vendor-side problem came from a July r/SaaS thread that made the rounds: AI-native SaaS teams are finding that their agents "now do work that used to take multiple human seats, but the pricing model still charges per seat. So a customer pays less as the AI gets more efficient - which is backwards for the vendor's revenue." Every efficiency gain the vendor ships reduces the vendor's own invoice. The teams handling it well are moving to usage- or outcome-based pricing tied to work performed, not humans logged in - the shift we analyzed in depth in our per-seat-pricing piece.
Buyers, meanwhile, keep asking the mirror-image question - a representative thread this month: "Why are SaaS companies moving toward credit-based pricing?" The honest answer: because credits let the vendor meter true consumption while giving you a prepaid number that feels like a plan. It is not a conspiracy; it is the only stable point between two pricing models that both stopped working.
Credits are now code (and they break like code)
A detail from inside GitHub's own tooling this month shows how operationally real this shift is: a CI guard had to be added because the model catalog and the credits-pricing catalog kept drifting apart - a model added to the pricing file but not the supported-models list produced misleading "retired or unsupported" errors at container start. Read that again from a distance: pricing is now a versioned artifact in the deploy pipeline, with its own drift bugs, its own CI, its own incident class. Anthropic's July 17 mishap - a bug that walled Fable 5 behind usage credits two days before the announced switch (our full account here) - is the same lesson from the consumer side: when pricing is code, pricing has outages.
The counter-pressure: this pricing level may not hold
The most-discussed skeptical take of the window came from Palo Alto Networks' CEO, arguing AI pricing "needs to fall 90%" as token costs climb for buyers. Meanwhile the discount flank is real: Chinese labs (Kimi's K-series most visibly) and aggressive new entrants keep pricing frontier-adjacent capability at a tenth of Western rates, and cheap-model routing via aggregators is now a default cost tactic. Credits do not protect vendors from that pressure - but they do let a vendor cut effective prices per model silently, by adjusting conversion rates, without repricing the plan. Expect exactly that through the fall.
What to do with this, on each side of the invoice
- If you buy: treat every "included credits" number as a promotional artifact and budget from the metered rate. Build your own per-workflow consumption table - the vendors have shown, three times in seven weeks, that they will not publish one. Meter runs, attribute them to invokers, and alert at 60/85% of a cap you chose calmly.
- If you sell: the window where per-seat was defensible for agentic products is closing; the r/SaaS inversion is arithmetic, not opinion. But learn from the same vendors' mistakes: publish the consumption table your customers will otherwise reverse-engineer angrily, and treat your pricing catalog as production code with tests - because it is.
For the per-vendor mechanics, see the deep dives: Copilot's AI Credits, Workspace Agents' seat-plus-meter, and the Fable 5 switch.