Uber Burned Its Entire 2026 AI Coding Budget in 4 Months — The Per-Token Cost Paradox Every Builder Is About to Face

Uber gave 90% of its engineers access to Claude Code in December 2025. By April 2026, the entire year's AI coding budget was gone. Not over-budget. Not close to the line. Exhausted. Four months into a twelve-month plan.

The COO publicly questioned whether the investment was worth it. Uber has since capped spending at $1,500 per engineer per month. At their scale, that's still $847,000 a month in AI coding costs alone. And they're the ones who got religion. Plenty of enterprises haven't.

If this were just an Uber story, it'd be a footnote in an earnings call. It's not. It's a preview of a cost dynamic that hits every builder who scales AI features, whether you're running a 2,000-person engineering org or a two-person no-code startup burning through API credits on a Tuesday afternoon.

How does per-token pricing keep collapsing while total bills explode?

Here's the paradox in two numbers.

Per-token prices have dropped between 60% and 97% since early 2025. Analysis of 2.4 billion enterprise API calls shows the blended cost fell from $18.40 to $6.07 per million tokens year-over-year. The cheapest models — Kimi K3 at $0.40 per million tokens, the open-weight models racing toward zero — make the unit economics look irresistible.

Total AI coding bills, meanwhile, are up 320%.

The mechanism is simple and brutal: consumption is growing faster than prices are falling. Way faster. Faros AI's research pegs agentic coding tools at driving 18.6 times more token consumption per developer than earlier copilot-style autocomplete. Every time a model gets cheaper, the agent runs more loops, checks more edge cases, generates more alternatives. The price elasticity works backwards from what your CFO's spreadsheet assumes.

I've stared at an API bill that made my stomach drop. If you haven't yet, you probably will.

What's actually driving the consumption surge?

Three things, all of them accelerating.

First, agentic coding loops. These aren't single prompts. An agent like Claude Code or Codex's autonomous mode runs chains of reasoning — it reads files, generates code, runs tests, reads error output, regenerates, and loops again. One "generate this feature" request might burn 200,000 tokens before you see the result. You only see the output. The meter was running the whole time.

Second, context windows are enormous now. GPT-5.6, Claude 4, Gemini 2.5 — these models swallow entire codebases as context. That's incredible for accuracy. It's also incredible for your bill. Every request ships your entire project state through the tokeniser, and you're paying for input tokens on every single turn.

Third, adoption rates compound the maths. Uber hit 95% monthly active AI usage among engineers. 70% of committed code is AI-generated. When nearly everyone on payroll is hitting the API constantly, the per-engineer numbers stop being a rounding error and start being a line item bigger than some people's salaries. Tunguz's analysis shows the top 1% of companies now spend $89,000 per engineer per year on AI — that's 40% of a fully loaded senior engineer. Gartner projects AI coding costs will surpass the average developer salary by 2028.

Let that land: the tool might cost more than the person using it.

Does this actually affect no-code builders, or just big engineering orgs?

Solo builders and small teams aren't immune. The dynamics are identical; the scale just makes them easier to miss until the invoice arrives.

GitHub Copilot killed its flat-rate $10/month plan on June 1, 2026, moving everyone to usage-based billing. That $10 plan used to cap your exposure. Now Copilot Pro gives you $15 in credits and meters everything beyond it. Pro+ bumps to $70 in credits. Max to $200. Theo from t3.gg documented burning through thousands of dollars worth of tokens while paying $40 flat — a loophole that usage-based billing was explicitly designed to close.

On Reddit's r/SaaS, solo founders report bills jumping from $200 one month to $900 the next "with no clear explanation." Another builder on r/microsaas hit $340 in a single week running Claude API agents unsupervised before they realised what was happening and added prompt guards. One of the recurring refrains: "I fixed it after the first bill, but that first bill hurt."

If you're building a no-code app that calls AI APIs — whether through Bubble's API connector, a WeWeb function, or direct integration from your Stacker portal — you are exposed to the same consumption dynamics as Uber. You just have fewer engineers to spread the blame across.

How do you model costs before they model you?

I've started treating AI API costs the way I used to treat cloud infrastructure: assume your estimate is wrong by a factor of 3x and build from there.

Here's what a practical forecast looks like for a no-code builder with moderate AI usage:

• Baseline: Count your expected API calls. Got a number? Now multiply by the average token burn per agentic request, which is rarely under 50,000 tokens round-trip for anything non-trivial. A "simple" feature generation might be 200,000.
• Consumption growth: Agent loops get longer as context windows expand and models get more capable. Assume at least 2x consumption growth year-over-year even if your product usage stays flat.
• Price declines: Yes, per-token keeps dropping. But at maybe 50% per year, not 97%. The easy gains happened already. Budget for prices to fall, but don't bet your runway on it.
• The multiplier that matters: Your real exposure is (API calls x tokens per call x price per token). Most people only budget for the first variable. The second one eats them alive.

For a concrete example: a no-code app generating 10,000 AI-assisted features per month at 150,000 tokens per feature, at $6 per million tokens, runs about $9,000 a month. That same app a year ago — fewer tokens per request, higher per-token price — might have been $4,500. The tool got cheaper. The bill doubled. That's the paradox in spreadsheet form.

What does "not getting obliterated by your AI bill" actually look like?

A few things I've seen work:

Hard caps per user, per day, per feature. Not soft warnings. Actually cutting off the API call. The solo builders who got burned all describe the same pattern: they saw the bill after the fact. By then the tokens are spent. Usage-based billing turns every uncapped endpoint into an uncapped liability.

Platform abstraction. Platforms like Stacker handle token costs behind the scenes as part of a bundled model, so builders aren't configuring API keys and praying. You pay for the platform, not the token meter. For no-code teams that want to ship AI features without becoming amateur token economists, that abstraction stops being a "nice to have" and starts being the difference between predictable costs and a quarterly surprise that wipes out your margin.

Prompt efficiency is underrated. The solo builder who fixed their $340/week Claude bill didn't switch models. They shortened their prompts, reduced context windows, and added stop conditions. Boring work. Saved them 85% on the next bill. Most AI cost overruns aren't sophisticated — they're just nobody having the job of watching the meter.

The takeaway

The per-token price chart is the most misleading graph in tech right now. It tells a story of democratisation and falling barriers. The total-spend chart tells the real story: AI is getting cheaper per unit and vastly more expensive in aggregate, because we're using more of it than anyone budgeted for.

Uber's four-month budget burn isn't a cautionary tale about big companies being sloppy. It's a preview of what happens when AI adoption hits escape velocity inside an organisation that didn't build the financial controls first. If you're scaling AI features in a no-code product, you're in the same position — just with fewer zeros on the invoice and less room to absorb the hit.

Model your costs assuming consumption grows faster than prices drop. Set hard caps before you need them. And if you're not sure you want to think about token economics at all, use a platform that abstracts them away. Your future self, staring at a monthly bill, will thank you.