June 16, 2026

Token prices collapsed faster than almost any technology cost in history. Yet engineering teams are hitting emergency spending caps and cancelling licences. Understanding why that happened is the first step to fixing it.

Uber burned through its entire annual AI budget in four months. Not by being wasteful, but by doing exactly what its leadership encouraged. The company had internal leaderboards celebrating heavy AI usage, executives publicly praised the productivity gains, and then the bill arrived. The result: a $1,500-per-month hard cap on each agentic coding tool, per employee, effective June 2026.¹

That story isn't a cautionary tale about one company's poor planning. It's a preview of what happens when metered, per-token pricing meets agentic workloads at scale, and it's landing in your budget right now.

Start with the numbers.

The Jevons paradox is running your AI budget

In 1865, economist William Stanley Jevons noticed something counterintuitive. As steam engines became more efficient, cheaper to run per unit of work, total coal consumption went up, not down. Efficiency unlocked demand that hadn't existed before.

The Jevons paradox is what's happening to your AI spend. Token prices dropped roughly 80% between 2025 and 2026.² Your engineers didn't pocket those savings; they used them as permission to run more, longer, and more ambitiously. A task that cost $10 now costs $2, so your team runs it five times instead of once, then hands it to an agent that runs it fifty times automatically.

The strongest counter-argument: "If unit costs fell 80%, even tripling usage keeps the bill flat." That's true for chat-style, single-turn interactions. It breaks completely once you introduce agentic loops, because an agent doesn't triple token consumption. It multiplies it by 50x.³ A single agentic coding session now pushes 1–3.5 million tokens per task;⁴ one agentic coding tool, used heavily, clears Uber's $1,500 monthly cap on its own.

The math isn't subtle.

What one agentic coding turn actually costs

Take Claude Opus 4.8, a model your senior engineers might reasonably reach for on a complex refactoring task. Input tokens run $5 per million; output tokens run $25 per million.

A single agentic turn with a reasonable context: 200,000 input tokens × $5/M = $1.00. The model responds with 50,000 output tokens × $25/M = $1.25. Total: $2.25 per turn.

Now multiply that across a real workday: 40 turns per day, 20 working days. That's $1,800 a month, from one engineer, using one tool, on one model. Uber's $1,500 cap doesn't cover it.

The pricing chart below shows why output tokens are the number that matters. Input is the sticker price. Output is the bill.

Developer spend follows a power law

Not every engineer hits $1,800 a month. A solo developer on a single subscription tool pays roughly $100. A heavy multi-tool user lands around $400. The power agentic user, the one actually getting the productivity gains, runs $1,500. And Microsoft reportedly cancelled employee AI licences after discovering some engineers were running $2,000 per month each.⁷

That distribution matters for how you think about governance. The engineers generating the most business value from AI are, structurally, the same engineers generating the largest bills. Blunt per-tool caps catch both.

Sixty-three percent of organisations now name AI an active FinOps concern, up from 31% in 2024, according to the FinOps Foundation.⁵ That doubling isn't panic; it's recognition that per-token billing has no natural ceiling, and finance teams weren't built to forecast it.

Converting variable cost into fixed cost

Every dollar you spend on external LLM APIs is a variable cost that scales with usage. There is no cap baked into the architecture. You impose caps manually, reactively, after the budget has already moved.

The structural alternative is converting that variable cost into a fixed, plannable one: infrastructure you own, models you run, a bill that reads more like a data-centre line item than a taxi meter. That's the architecture change, not a configuration tweak.

Owning the stack also collapses a second problem into the same decision. Teams that can't send sensitive code or proprietary data to external APIs in the first place, like regulated industries with strict data-residency requirements, get cost control and data control from one architectural choice: when the models run inside your own perimeter, the spend is a capacity you provisioned, and the data never leaves it.

The honest objection is that owned infrastructure costs more upfront. That's true, and you should model it carefully. The break-even depends on your team size, your model mix, and how far up that power-law curve your engineers actually sit. But the Uber scenario, burning an annual budget in four months and then reaching for a blunt cap, has a specific infrastructure shape behind it: metered external APIs with no architectural ceiling.

The third that hasn't solved this yet

Look at the FinOps Foundation's numbers again. Two years ago, fewer than one in three organisations considered AI spend a FinOps concern. Today it's nearly two in three. The other third hasn't caught up yet, or they've decided the productivity gains justify the open meter.

That second position is defensible for a while, at the right scale. One company reportedly spent approximately $500 million on AI after failing to enact employee usage caps.⁷ MIT research suggests roughly 95% of enterprise GenAI projects fail to deliver measurable financial returns within six months.⁶ Unlimited spend on ambiguous return is a hard position to hold when the board asks.

The move that's working for teams ahead of this curve: model the cost of your specific agentic workload (use the math above as a starting point), map it against the productivity return you can actually measure, and decide whether metered external spend or fixed owned infrastructure gives you better control over that ratio. Don't let the sticker price on input tokens be the number your finance team sees.

Sources

1. TechCrunch, "Uber caps employee AI spending after blowing through budget in four months" (June 2, 2026).
2. CloudZero, "LLM API Pricing Comparison". Per-million-token input/output prices and the ~80% year-over-year decline (2026).
3. LeanOps, "Agentic AI cost runaway: the token budget problem". Agents consume roughly 50× the tokens of a chat prompt (2026).
4. Morph LLM, "AI Coding Costs". Median monthly token usage (~51M/developer), tokens per agentic task, and per-developer monthly spend ranges (2026).
5. FinOps Foundation, finops.org. Share of organisations naming AI an active FinOps concern, 31% (2024) → 63% (2025).
6. MIT Project NANDA, The GenAI Divide: State of AI in Business (2025). Roughly 95% of enterprise generative-AI projects show no measurable financial return within six months.
7. Secondary industry reporting (2026). Microsoft engineers' reported ~$2,000/month agentic token bills and a reported ~$500M unmanaged AI spend at one company. Primary sources still to be confirmed before publication.