DEV Community: socaity

The token bill came due

socaity — Mon, 06 Jul 2026 09:07:27 +0000

Five checks of a spreadsheet, one habit of a culture: how usage-based billing turned 2025's AI enthusiasm into 2026's cost crisis, and why the exit is not a throttle.

Somewhere out there is a company that spent roughly $500 million on Claude in a single month, reportedly because nobody set a usage limit on employee licences. Uber burned through its entire annual AI budget in four months and now caps engineers at $1,500 a month per tool. On the second of July, Tesla capped employee AI spending at $200 a week. The same week, 404 Media published leaked Slack messages and dashboards showing Amazon, Adobe, Atlassian and Citi quietly throttling employee AI use, with one firm's spend tripling past $15 million a month.

None of these companies stopped believing in AI. They stopped believing in the meter. 2026 is the year usage-based token billing caught up with unlimited enthusiasm, and the reckoning is running on two tracks at once: what the tokens cost, and who controls the tap. This piece follows both to the same destination: open-weight models, hosted in Europe.

What tokenmaxxing was

Through 2025 the doctrine in large companies was simple: use as much AI as possible. CBC documented the culture directly: Meta and Amazon employees competed on internal leaderboards for most tokens used. The word for it was tokenmaxxing, and it rested on an assumption so obvious nobody checked it: more tokens means more value.

A token, for anyone who has not paid for one, is the unit AI vendors bill by: a word-fragment of input or output, metered like electricity. Global News wrote the plain-language explainer when the surprise bills started making general news, and even r/singularity was passing around a Computerphile video just to explain why the meter runs the way it does.

By late May, Fortune had published tokenmaxxing's obituary: token consumption never measured business value, it measured consumption. The companies that optimised for it got exactly what they optimised for.

Why the bill exploded

The mechanics are not mysterious. A chat prompt is one metered exchange. An agent is a loop: it plans, calls tools, reads results, retries, and every step burns tokens. Goldman Sachs put the multiplier at 24x for agentic workflows; Tom's Hardware reported cases running up to 1,000 times the tokens of standard use.

The practitioner numbers match. One user on r/ollama flagged Cursor's move to per-tool-call billing as an effective 25x price rise, because "each tool call is billed separately". A developer on r/OpenAI reported spending 7.35 billion input tokens in November, and wrote a survival guide for others.

Then came the sentence nobody deploying "cost-saving" AI wanted to read. Reporting on Microsoft's own internal data, Fortune concluded that using the tech is often more expensive than paying human employees, a finding Forbes echoed in July. The most-cited case study is secondhand but telling: according to a widely shared account of Marc Benioff's podcast remarks, Salesforce will reportedly spend some $300 million on Anthropic tokens this year while hiring no new engineers. As the top comment on that thread put it: "That's a structural shift, not a cost-cutting round."

Anatomy of a surprise bill

It is worth slowing down on the mechanics, because the surprise in "surprise bill" is structural, not careless. Four compounding effects do the damage.

Context is re-billed every turn. A conversation does not remember; it re-reads. Each exchange resends the accumulated context, so a long agent session pays for its own history again and again. Vendors sell prompt caching as the fix, and the discounts are real but uneven: in the 7.35-billion-token thread on r/OpenAI, practitioners compare a 90 percent cached-token discount on newer model lines against 50 percent on older ones, which is exactly why cache strategy has become a budget line. Coinbase pushed its internal cache hit rate from 5 percent to 60 percent as one of the three levers that halved its spend.

Every tool call is a metered event. An agent that plans, calls a search tool, reads the result, calls a code tool, fails, and retries has spent six billable exchanges to answer one question. That is how Cursor's per-tool-call billing became an effective 25x price rise in the community's maths, and why Microsoft told Axios that agentic tools produce "bonkers" bills.

Prices move underneath you. Old automations quietly keep paying old rates: r/OpenAI users found legacy endpoints running at what is now effectively 100 times the cost of current equivalents, and when the newest models arrived priced higher per token, not lower, the assumption that time would fix the bill died too.

Nobody owns the meter reading. The final effect is organisational: token spend sits outside the tools finance already watches. The result is an entire cottage industry of AI cost-observability tooling, built to answer a question that infrastructure teams solved for cloud a decade ago: who spent what, on which workload, and was it worth it.

None of these four is misuse. They are the pricing model working as designed. Which is why the responses that follow, caps, audits, routing, all share a ceiling: they tune consumption, not terms.

The pullback: tokenminimizing

The corporate reversal now has its own name. The Information reports Meta is curbing employee AI usage under the banner of tokenminimizing, as costs reach billions. The Next Web catalogued the wave: AT&T limiting Copilot access, Walmart capping its in-house agent, Amazon scrapping its usage leaderboard, Microsoft engineers found spending $500 to $2,000 a month on Claude Code tokens alone. Accenture told staff to stop using AI for unnecessary tasks as one executive described "just rapid escalation in AI token spend", and TechCrunch found companies scrambling to stop employees maxing out budgets on trivial tasks.

The sophisticated version of the pullback is model routing: send hard problems to expensive frontier models, everything else to cheap ones. CNBC called routing a structural problem for OpenAI and Anthropic, and by late June was reporting the wholesale shift from tokenmaxxing to efficiency. An entire tooling industry has sprung up around cost control.

Routing and caps are rational. They are also a tell. Throttling optimises your spend on a meter someone else controls: the vendor still sets the price, the limits, and the terms, and can change all three overnight.

The developer revolt

If the CFO story is about bills, the developer story is about trust, and it broke first. When Anthropic's usage limits tightened in the spring, r/ClaudeCode filled with reports that limits were "silently reduced". One user argued the widely reported "rate limit bug" was really quiet peak-hours throttling of paid quotas. The texture of the threads says it all: a five-hour limit hit in a single session, a five-hour limit after 14 minutes and two prompts, a heavy Max user reporting limits changed dramatically overnight, and a subreddit megathread just to contain the complaints.

Then the cancellations: a 13-month Max subscriber walking away from the $200 plan, another calling the new limits useless, users rotating multiple $20 plans to dodge weekly caps, and a thread arguing the paid plan had become objectively worse than the free tier.

It was not one vendor. When GitHub moved Copilot to usage-based credits, the flagship thread was titled Bye Bye Copilot: new pricing looks to be a joke, with one developer projecting a jump from about $28 to about $746 a month. Another wrote an elegy for the tool: "A few simple prompts. A few days of development. EUR 40 later." A third thread marvelled at how much money flat-rate Copilot must have been losing. Cursor users had already been through it: a pricing change that ended all-day coding overnight, Max Mode burning credits faster than anyone expected, $130 gone halfway through the month, and side-by-side comparisons of the old and new price models. On r/OpenAI, users itemised how the newest models got more expensive, not less, and warned each other about legacy API endpoints now effectively 100x the price of current ones.

This was building for years. As far back as 2023 and 2024, developers were asking whether local models could replace ChatGPT, compiling lists of cheaper providers, doing the local-versus-API maths, and asking how to admit an AI investment had gone wrong. The 2026 crisis did not appear from nowhere; the meter just finally ran fast enough for everyone to see it.

The escape hatch: open-weight models

While the bills landed, something else happened: the cheap models got good. Forbes tracked how DeepSeek and Alibaba's Qwen reshaped the open-source race, with Qwen taking over half of global open-model downloads. Red Hat's state-of-open-source review reads like a changing of the guard, and IISS treated DeepSeek's open-weight frontier release as a strategic event.

Honest numbers matter here. On the SWE-bench Verified coding leaderboard, the top proprietary models score in the high eighties and nineties, while the leading open-weight models, Kimi K2.6, DeepSeek V4 and GLM-5, sit around 77 to 80 percent. That is a real gap at the frontier, and an irrelevant one for a large share of production workloads, which is exactly what the community's own benchmarking keeps finding: Kimi K2 climbing the SWE-bench leaderboard, DeepSeek v3.2 posting gold-level competition results at a fraction of frontier pricing, practitioners comparing DeepSeek, GLM and MiniMax head-to-head for agentic coding, and GLM release threads full of people actually deploying it.

The switches are no longer hypothetical:

Coinbase cut its AI spend nearly in half by defaulting engineers to GLM 5.2 and Kimi 2.7, citing GLM at about $1.40 per million input tokens against $5 for the frontier equivalent.
Lindy moved essentially all of its traffic off Claude to DeepSeek, reporting around 90 percent cost reduction on migrated routes.
Airbnb's CEO says its customer-service agent relies heavily on Qwen: "very good, also fast and cheap." (One agent, not the whole company, and thirteen models are in the mix.)
Cursor's Composer was built on Moonshot's open-weight Kimi K2.5, further-trained on code, something the company later conceded it should have disclosed.
Microsoft is testing an Azure-hosted DeepSeek inside Copilot Cowork, telling Axios that agentic tools generate "bonkers" bills. Testing, not shipped, but the direction is unmistakable.
On the ground, employees report the same move: one company simply replaced Claude with DeepSeek, and Claude Code users openly ask how to migrate to GLM or MiniMax.

Underneath it all is a price engine. DeepSeek's sparse-attention work halved long-context API costs, and Epoch AI's data shows inference price-per-capability falling between 9x and 900x per year depending on the task. Or as one r/singularity commenter put it, frontier pricing is expensive "for the same reason weed is", while DeepSeek "charges 2 orders of magnitude less on their API and is still profitable".

More than a discount: cost, control, predictability

If open weights were only cheaper, this would be a procurement story. The deeper shift is about control. When the weights are open, no vendor can silently cut your limits, reprice your legacy endpoints, or take a model away from you. CDOTrends called 2026 the year the enterprise stops renting its brain, and after the spring's silent-throttling threads, "renting" is exactly the right word. When Anthropic pulled Claude Code from the Pro plan, the top r/LocalLLaMA response was a 1,500-upvote migration guide framed around "choice and ownership".

The honest caveat: self-hosting is not automatically cheaper. The community's own maths on trillion-parameter models is sobering; one r/LocalLLaMA thread weighs a $70-per-387M-token API bill against the hardware to run a 1.02T model yourself and concludes local's real payoff is control and privacy, not raw cost. DIY GPU operations are a job. The pragmatic middle path is hosted open weights: fixed, published prices on models nobody can take away, run by someone whose job is uptime.

What a controllable stack looks like

Strip the argument to its practical core and "control" becomes a short procurement checklist. Whatever you run, from whoever you run it with, demand four things in writing:

A published price list, per million tokens, that does not change retroactively. If pricing lives in a sales deck, it is a variable, not a price. (Scaleway's model-as-a-service list is what this looks like in EUR: public, per-token, per-model.)
Pinned model versions. The silent-throttling threads were so corrosive precisely because nobody could prove what changed; a pinned open-weight checkpoint cannot be quietly swapped underneath you.
Exportable weights, or a provider who runs models whose weights are public. This is the exit clause that makes every other clause enforceable. A vendor who knows you can leave behaves differently from one who knows you cannot.
A jurisdiction you operate in. Terms are only as strong as the law that enforces them, which is the bridge to the second force in this story.

We wrote a companion piece on the sovereignty half of this checklist, The EU AI Stack Checklist, after a US directive switched two frontier models off for everyone outside America with three days of warning. The same test applies here: who can switch you off, and under which law?

The European dimension

For European companies, 2026 added a second force, and it arrived abruptly. When US export controls cut non-US access to Anthropic's frontier models in June, CEPA reported European alarm over a foreign "kill switch" on critical AI. Lawfare argues the controls are pushing international users toward Chinese open-weight models, PIIE reaches the same conclusion: weights you can download are weights nobody can switch off. AI Frontiers called the episode a sobering warning that Europe failed to treat AI as a sovereign capability, and Global Banking and Finance Review documents Siemens, Renault and Orange responding by spreading model risk across US, Chinese and European providers.

The dependence runs deeper than models. Tech Policy Press argues AI demand keeps Europe hooked on the three US hyperscalers. The EU's answer includes OpenEuroLLM, a EUR 37.4M open-model effort across some twenty organisations, Mistral's open-weight sovereign bet, and first-party builds like Siemens' self-contained LLM platform. And to keep this honest: Raconteur reports real resistance, with Volvo and Stellantis warning sovereignty raises costs, and Europe still dependent on non-EU providers for over 80 percent of key digital products. Sovereignty is a direction of travel, not a done deal.

One move, three problems: the case for EU-hosted open weights

Put the two forces together and the destination writes itself. Cost: open weights collapse the price of the token and, hosted at fixed published rates, end the surprise bill. Control: nobody can silently throttle, reprice, or revoke a model whose weights are public. Sovereignty: hosted on EU infrastructure, the data never leaves European jurisdiction, and no foreign directive can switch it off.

This is not theoretical infrastructure. EU providers already run open-weight models at published EUR prices; Scaleway serves open models from European data centres from EUR 0.20 per million tokens, pay-per-token, on its own published price list. That is what a meter you can read looks like.

To be plain about our own position: this is the thesis Socaity is built on, so treat this section as our argument rather than a neutral finding. We run open-weight models on EU soil with predictable pricing because everything above convinced us the alternative is renting a meter you cannot read from a jurisdiction you cannot vote in. The pitch is deliberately unexciting: reliable, boring, predictable. Nothing surprising on the invoice. Nothing surprising in the data-residency report. Boring is the feature.

The bill you can predict

The 2026 token crisis was not a failure of AI. It was a forcing function. It stripped away the illusion that renting intelligence by the token, from a vendor who sets the meter, on infrastructure governed elsewhere, was either sustainable or safe. The companies that internalise the lesson are not the ones with the cleverest throttles; they are the ones that own their stack.

The durable advantage is a bill and a data location you can predict a year out.

If you want to see what that feels like, it is one line: pip install socaity, and the open-model catalogue runs on EU soil, with your data staying in the EU. The details are at socaity.ai.

Frequently asked questions

What was tokenmaxxing? The 2025 corporate doctrine of using as much AI as possible, complete with internal leaderboards for most tokens consumed. It treated consumption as a proxy for value; Fortune declared it dead in May 2026 because it never was.

Why do AI agents cost so much more than chatbots? Agents loop: they plan, call tools, read results and retry, and every step is billed. Goldman Sachs puts the multiplier at 24x, with reported cases up to 1,000x.

Are open-weight models as good as the frontier? Close, and closing. On SWE-bench Verified the leading open models score roughly 77 to 80 percent against the frontier's 89 to 95. For a large share of production workloads the gap does not justify a 3x to 100x price difference, which is why Coinbase, Lindy and Airbnb switched where it made sense.

Is self-hosting cheaper than the API? Not automatically. The community's own maths on trillion-parameter models says local's real payoff is control and privacy. The pragmatic middle path is managed open-weight hosting at fixed published prices, in a jurisdiction you operate in.

Sources

News

Community

The EU AI Stack Checklist

socaity — Mon, 06 Jul 2026 09:07:23 +0000

In June 2026 a frontier AI model went dark for everyone outside America.
Anthropic launched Fable 5 and Mythos 5 on 9 June. At 5:21pm ET on 12 June,
a US export-control directive
ordered access suspended for all foreign nationals, and since a shared cloud
cannot be fenced by nationality, both models went dark for everyone outside
the US.
Access came back on 1 July
with a new safety classifier that routes blocked requests to a different
model,
and the stronger tier, Mythos 5, returned only to roughly 100 vetted US
organisations
that defend critical infrastructure. Nobody's engineering failed. The terms
did.

Europe noticed. Austria's State Secretary for Digitalisation wrote to the
European Commission
proposing the EU explore bringing Anthropic inside European jurisdiction.
And the money had already moved: Gartner forecasts worldwide sovereign
cloud infrastructure spending of $80 billion in 2026, with European spending
growing 83%.

That is the thing about an AI stack: the model is the easy part. The part
that decides whether your product survives a bad Friday is jurisdiction,
portability and exit terms. Here is the checklist we use. Run your current
stack through it honestly.

1. EU hosting

Ask where inference runs, not where the vendor is incorporated. A European
sales entity in front of US-controlled compute fails this check. What to
demand: the region of the machines that execute your requests, in the
contract.

How we answer it: Socaity runs open models on EU soil. The deployment is the
product, not a compliance footnote.

2. Data residency

Your prompts and outputs are business data. If they transit or rest outside
EU jurisdiction, your DPO inherits a problem you created. What to demand:
residency for data in transit and at rest, named in writing.

3. Model portability

The June story had a quiet lesson: teams glued to one proprietary model had
no plan B. Portability means switching models without a rewrite. This is the
whole test:

import socaity
socaity.install("qwen/qwen-image-edit-plus")
from socaity.sdk.replicate.qwen import qwen_image_edit_plus

out = qwen_image_edit_plus(api_key=key).run(
    image=["you.png"], prompt="keep the face"
)
out.get_result().save("real.png")

Swap the model name, keep the call. If your stack cannot do that, every
model decision you make is a marriage.

4. Exit terms

Read the clause that describes your last day as a customer. Can you export
what is yours? How much notice do you get before a model is retired or
restricted? The June directive gave the world three days.
What to demand: notice periods and export rights, not goodwill.

5. The off-switch test

One question: who can switch you off, and under which law? If any answer
involves a jurisdiction you do not operate in, you are renting your roadmap
from someone else's government. Open weights on EU infrastructure is the
boring answer. Boring is the point. Trust something that never surprises
you.

The full Socaity model list is one SDK call away:
https://socaity.ai?utm_source=substack&utm_content=eu-ai-stack-checklist

If this checklist found a gap in your stack, that is the post doing its job.
Forward it to whoever owns the vendor contract.

Sources