Home/ Incident database/uber-ai-coding-budget-2026-06
Financial loss API cost spike verified

Uber burns through its entire 2026 AI coding budget in four months

Uber · Jun 2, 2026 · Coding agent

What happened

Uber exhausted its full-year 2026 budget for AI coding tools by April, four months into the year, and responded by capping employee AI spending. TechCrunch reported the overrun as part of a broader industry reckoning over runaway token costs, noting that Microsoft had similarly revoked Claude Code licenses for developers months after enabling them.

Loss / impact
Jun 2
2026
API
Failure mode
Coding
Agent type

Causal vector

Uncapped per-developer token consumption across an engineering org — spend scaled with agent adoption faster than budget controls could absorb

Source

Reported by TechCrunch. Verified against the primary report.

Read the original report ↗

How a spend firewall would have helped

Org-level budgets fail exactly where per-agent controls succeed: at the individual call. Daily totals and velocity limits bound every developer's agent spend at the transaction level, so a full-year budget cannot be exhausted in a quarter without an explicit decision to raise it.

The six rule types that contain this class of failure

Per-transaction cap

Any single spend above your ceiling is BLOCKED before it moves.

Daily total

Cumulative spend across all agent calls, bounded per day.

Velocity limit

Stops runaway retry loops — the #1 cause of overnight losses.

Merchant allowlist

Only approved destinations can ever receive funds.

Category rules

Flag high-risk classes (crypto, infra, refunds) for review.

Approval threshold

Above a value, the action waits for a human.

Related incidents

Don't be the next entry

Every incident in this database is the result of trusting a prompt, a provider cap, or a human review cycle. sipi.bot replaces all three with one deterministic call. 67 documented failures, one control.