Uber Burned Its 2026 AI Budget by April — The Agentic Cost Crisis

Uber’s AI team ran out of budget in April. Their fiscal year started in January.

That sentence appeared on Hacker News and hit the front page in under two hours, accumulating hundreds of comments from engineers who recognized the pattern immediately. Not because Uber is uniquely reckless, but because the same story is playing out at organizations everywhere. The r/LocalLLaMA thread about compute cost frustration — 181 upvotes, hundreds of comments from engineers describing identical spiral — makes the same point from the other direction: whether you’re paying for cloud inference or running your own GPUs, agentic AI costs are destroying budgets that looked perfectly reasonable when the procurement approval was signed.

I cut my own agent pipeline costs by 74% over six weeks using a routing architecture I’ll show you here. The core insight is simple: you are almost certainly sending every task to the same expensive model regardless of complexity, and that single decision is costing you more than everything else combined.

According to Forrester’s 2026 enterprise AI deployment survey, 22% of agent deployments now report negative ROI — not because the agents don’t work, but because the infrastructure costs exceeded the productivity gains. The agents work. The bills are just bigger than anyone planned for.

Try it yourself: Free AI Prompt Cost Calculator — free, no signup, runs in your browser.

The Agentic Cost Explosion Nobody Planned For

The math that kills AI budgets is rarely the per-token pricing. It’s the multiplication factor that nobody writes into their procurement estimates.

When a product manager approves $10,000/month for an AI coding assistant, they’re imagining simple prompt-response pairs at a few cents each. What they’re actually getting is an agent that, for every user request, may run a planning step, 4-6 tool calls, 2-3 reflection passes, and a final synthesis — each of which hits the API separately. A task that looks like “one request” in the approval doc is 8-12 API calls in the billing dashboard.

Opus 4.7 is priced at $5 per million input tokens and $25 per million output tokens. GPT-5.5 runs $5 per million input and $30 per million output. At those rates, a simple agentic task that chains 10 LLM calls — each consuming 2,000 input tokens and producing 800 output tokens — costs roughly $0.40. That’s not alarming until you remember that a busy developer using an AI coding agent makes 50-100 such requests per day. Per developer. For a team of 20, that’s $400-$800 per day, $8,000-$16,000 per month, from a single team using a single tool.

Now multiply by the number of agent pipelines your organization has deployed since Q1 2026.

The Pro plan context also exhausts faster than most users expect. Heavy prompting — long context windows, multi-file codebase analysis, extended reasoning chains — depletes a Claude Pro plan after roughly 12 substantial prompts. Power users hit this limit before lunch. The response is either to throttle to cheaper sessions or to upgrade to API access with consumption-based billing, which removes the cap but also removes the cost ceiling that made the Pro plan feel “safe”.

This is the structural trap: fixed-price plans create a ceiling that users run into, pushing them to consumption billing. Consumption billing removes the ceiling and exposes the real cost of agentic usage patterns. Teams that made the switch in Q1 2026 are the ones showing up in that Forrester negative-ROI data.

Why Agent Tasks Cost 10-100x a Simple API Call

The cost multiplier is not a bug in the pricing model. It is the natural consequence of how agents work, and understanding it is the prerequisite to managing it.

A simple API call sends a prompt, receives a response, costs one unit of compute. An agent task is architecturally different. It starts with a planning phase where the model reasons about the task and decides what tools to use — that’s one or two LLM calls. Each tool call has a pre-call reasoning step, the execution itself (which may or may not be an LLM call), and a post-call evaluation where the agent decides whether the result was satisfactory — potentially another LLM call. If the tool result is ambiguous or the agent decides it needs more information, it loops. If the final output needs to be formatted or synthesized from multiple tool results, that’s another LLM call.

A conservative estimate puts a moderate-complexity agent task at 8-15 LLM calls. A complex task — multi-file code review, research synthesis across 10+ sources, multi-step data pipeline — can run 40-100 calls. At Opus 4.7 pricing, 100 calls with average context is not $0.04. It is $4.00-$8.00. Per task. That is the 10-100x multiplier, and it is baked into the architecture.

There is also a context accumulation problem that makes costs grow nonlinearly. Each step in an agent workflow adds to the running context: the original task, the plan, the results of each tool call, the evaluation of each result. By step 8 of a 10-step workflow, the input token count for each call includes all preceding steps. The 9th LLM call in a chain is not the same cost as the first — it may be 5-10x more expensive per call because the context window has grown. This is why agent tasks that “should” cost $2 based on per-call estimates end up costing $15 in production.

The naive solution is to use cheaper models. But for complex reasoning tasks — architectural decisions, security analysis, multi-file refactors — substituting Haiku 4.5 for Opus 4.7 does not save money. It produces wrong outputs that require expensive human correction or re-runs. The real solution is routing: expensive models for tasks that require them, cheap models for tasks that do not.

For a deeper look at how to evaluate whether your agent outputs are actually correct — not just whether they returned HTTP 200 — see our guide on AI agent observability and production monitoring.