Company hit with a reported $500 million Claude bill after leaving usage limits off
Unnamed enterprise (reported via Axios) · May 28, 2026 · Coding agent
What happened
TechCrunch reported that one company found itself with a $500 million Claude bill after forgetting to set usage limits for employees, citing Axios. The bill is the extreme end of a pattern the article documents: enterprises overshooting AI token budgets by 3x or more in early 2026 as agentic tools multiplied token consumption.
Causal vector
Missing usage limits on an enterprise Anthropic account — consumption scaled with no ceiling in place
Source
Reported by TechCrunch (citing Axios). Verified against the primary report.
A spend firewall is a usage limit that cannot be forgotten: per-transaction caps, daily totals, and velocity limits are enforced by policy at the API boundary, independent of whatever the account owner remembered to configure.
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
Uber burns through its entire 2026 AI coding budget in four months
Uber · Jun 2, 2026
OpenAI o3 ARC-AGI benchmark run estimated to cost ~$346,000+ in compute
OpenAI · Dec 20, 2024
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.