Real AI bills that blew up, and what each one teaches
Publicly reported cases of AI spend running away, from one developer to the biggest companies. Each one is taken apart: what happened, why, and the habit that would have caught it sooner. Figures are as reported by the source linked under each case.
May 2026
$1.3 million in one month from 100 coding agents
What happened. Peter Steinberger, the developer behind OpenClaw, posted his OpenAI usage dashboard showing $1,305,088.81 over 30 days: 603 billion tokens across 7.6 million requests from about 100 coding agents.
Why. Many agents running around the clock, each paying for its own context on every call. Nothing was broken: this is what agent swarms cost at API prices.
The lesson. Know your burn rate per hour, not per month. A forecast of where the month will land tells you on day 2 what the invoice will say on day 30.
Source: Tom's Hardware
December 2025 to April 2026
A whole year's AI coding budget, gone in four months
What happened. Uber gave most of its engineers Claude Code in December 2025. By April 2026, the budget planned for the whole year was reportedly used up.
Why. Agentic coding reads files, runs tests, reads errors and loops again. Usage grew much faster than the plan assumed.
The lesson. Budgets set once a year don't survive agents. Check spend against budget every day, with alerts at 50%, 80% and 100%.
Source: NoCode.tech
Reported June 2026
Microsoft ran through its annual AI budget
What happened. After inviting thousands of developers to use Claude Code in December, Microsoft reportedly exhausted its annual AI budget because of token-based billing and began ending those licenses.
Why. Token billing scales with how much people use the tool, and enthusiastic developers use it a lot.
The lesson. If even Microsoft gets surprised, a solo developer can too. Put a monthly number on it and get pinged before you cross it.
Source: Cybernews
Reported May 28, 2026
A reported $500 million Claude bill in one month
What happened. Axios reported that an unnamed US company was billed about $500 million for one month of Claude use. The company hasn't been named, so treat the figure as reported, not confirmed.
Why. Reportedly: licenses and agents with no usage caps, plus long-context workflows.
The lesson. Caps and alerts are boring until the month they aren't. Every key should have a budget attached.
Source: Cybernews
February 2026
A $3,800 Claude API fork bomb
What happened. A developer wrote up how they accidentally created a Claude API "fork bomb", a process that kept multiplying itself, and ran up a bill of about $3,800.
Why. Something that copies itself with no stop condition. Every copy makes its own paid calls.
The lesson. Runaway loops look like a sudden jump in spend per hour. That is exactly the pattern an hourly burn alert watches for.
Source: Write-up summary on Fooqux
The pattern behind all of them
None of these were a single expensive request. They were normal-looking calls repeated many times: agents looping, context growing, usage nobody was watching between invoices. Watching the bill hourly, with a budget and a forecast, turns a surprise invoice into an alert while it's still happening.
Start free What would a loop cost you?
Checked November 13, 2026. Know a public case we should add, or see something out of date? Tell us and we'll fix it.