One two-hour coding session reportedly cost Uber $1,200, according to Yahoo Finance. That's not a monthly bill. That's one engineer, one sitting, one afternoon of letting Claude Code run.
Multiply that across roughly 5,000 engineers who reportedly hit 95% monthly active usage, and you get the headline: Uber exhausted its entire 2026 AI coding budget by April. Not over budget. Exhausted. Four months into a twelve-month plan.
CTO Praveen Neppalli Naga confirmed the overrun to The Information and said the company was "back to the drawing board" on its assumptions. The COO, per Fortune, reportedly started questioning aloud whether the spend was worth it.
Everyone read this as an Uber story, or an AI-hype story. It's neither. It's a pricing-physics story, and the physics apply just as ruthlessly to a two-person startup burning credits on a Tuesday afternoon.
Because here's the part that should stop you cold: Uber blew its budget while per-token prices were collapsing.
Between early 2025 and now, per-token prices reportedly fell somewhere between 60% and 97%. Analysis of 2.4 billion enterprise API calls reportedly shows the blended cost dropped from $18.40 to $6.07 per million tokens year over year.
Over that same window, total AI coding bills reportedly rose 320%.
That's the paradox in two numbers. Unit prices fell by two-thirds. Aggregate spend more than quadrupled. Both true at once.
Unit prices fell by two-thirds. Aggregate spend more than quadrupled. Both true at once — that's the paradox, and the physics apply at every scale.
Last issue we called this the "standing re-evaluation tax" and argued PMs now have to own pricing. This is the enterprise casualty with a name on it — and the physics behind the invoice.
The mechanism is simple and merciless: consumption is growing faster than prices are falling. Way faster.
Faros AI's research reportedly pegs agentic coding tools at 18.6 times more token consumption per developer than the old autocomplete-style copilots. Every time a model gets cheaper, the agent doesn't cost less. It runs more.
More loops. More edge cases checked. More alternatives generated. A single "build this feature" request can burn 200,000 tokens before you see a line of output — reading files, generating code, running tests, reading the errors, regenerating, looping again.
You see the result. The meter was running the whole time.
This is why your CFO's spreadsheet is wrong. It assumes elasticity runs the normal direction: price drops, you save. In agentic coding, price drops and consumption expands to fill the space and then some. Cheaper models drive higher bills.
The critical error is that most people budget for one variable — number of API calls — when real exposure is calls times tokens-per-call times price-per-token. The middle term is the one that eats you alive.
Now watch the same physics work at 1/1000th the scale.
A solo founder on r/microsaas reportedly hit $340 in a single week running Claude API agents unsupervised, before they even understood what was happening and bolted on prompt guards. Others on r/SaaS reportedly report bills jumping from $200 one month to $900 the next "with no clear explanation."
The recurring refrain: "I fixed it after the first bill, but that first bill hurt."
Zapier's June 15 repricing exposed the same dynamic inside no-code workflows. AI steps moved to tier multipliers — a Premium step making two tool calls reportedly burns 15 tasks, and a Professional plan ships with 750. Zapier's own 75-task-per-run safety limit exists because someone worked out that an unconstrained AI step could torch a month's task allowance in a single afternoon.
That's the tell. This isn't a big-company problem or a small-company problem. It's scale-invariant physics. Uber's $1,200 session and the solo founder's $340 week are the same event photographed at different zoom levels.
So the question stops being "which model do I pick" and becomes "who owns the meter."
Here's the pivot most teams miss: the fix isn't cheaper tokens. The fix is routing and metering as standing infrastructure.
Consider a mid-sized legal-tech startup drowning in a multi-provider mess — GPT-4o for summaries, Claude for clause work, DeepSeek dropping in at a tenth of GPT-4o's input price. Their cost tracking had devolved into a spreadsheet nightmare because every provider billed differently.
They put an aggregator in front of everything and wrote one dynamic routing rule: any prompt under 500 tokens goes to Mistral Small at $0.10 per million tokens instead of GPT-4o at $2.50 per million, unless flagged high-risk.
That single rule reportedly cut their monthly inference bill by 63%. Not by picking a better model — by refusing to send a frontier-priced model work that a cheap one handles fine.
This is the shift. Routing is no longer an optimization you get to later. It's the load-bearing layer between your product and an invoice that grows whether or not you're watching.
And behind routing sits the uglier truth: billing infrastructure itself is becoming a standing spend category.
As one product leader put it bluntly — you can build the AI feature in three months, but the billing infrastructure to charge accurately for it will take a year and still have edge cases.
Metering multi-step agent flows, retries, cached versus fresh tokens, input priced differently from output, internal versus external calls — this is genuinely hard engineering. Teams are quietly spending more time on billing edge cases than on the features themselves.
That tax doesn't appear in any vendor pitch deck. It shows up in every roadmap review.
So here is the concrete 2026 mandate, and it's a product mandate, not a finance one.
First: name an owner. Someone on the product side owns "cost of usage" as a permanent line item — not a quarterly cleanup, not a fire drill after the first scary invoice. A standing role, because the meter is a standing process.
Second: budget it at 3x your estimate. Treat AI API cost the way disciplined teams treat cloud infra — assume your forecast is wrong by a factor of three and build from there.
Third: bake in 2x consumption growth year over year, even if your product's usage stays flat. Agent loops get longer as context windows expand and models get more capable. Budget for prices to keep falling — maybe 50% a year, not 97% — but never bet your runway on it. The easy declines already happened.
Fourth: build or buy the routing and metering layer before you need it, not after. The legal-tech team's 63% cut came from infrastructure that existed before the bill blew up, not from a heroic cleanup afterward.
Uber had the money to absorb a four-month blowout and publicly wince. A two-person startup gets no such luxury. The first surprise bill is the whole runway.
The lesson isn't "AI coding is too expensive." Uber's engineers reportedly hit 70% AI-generated committed code; the value was real. The lesson is that falling per-token prices are a trap dressed as relief, and the only defense is treating cost of usage as owned infrastructure with a name attached.
Pick your models however you like. But if nobody owns the meter, the meter owns you — and it runs whether you watch it or not.