$12,229 in API Calls — Developer Only Paid $50
A developer's AI agent ran up $12,229 in API charges against a $50 initial payment, with no spending cap or circuit breaker to prevent the runaway costs.
The developer put $50 in. The bill came out $12,229.
An AI agent with access to API endpoints ran up charges that exceeded the developer's deposit by a factor of 244x. No spending cap triggered. No circuit breaker fired. No alert warned the developer that their $50 had become twelve thousand dollars.
The tweet documenting the incident went viral — not because runaway AI costs are new, but because the ratio was so absurd. A $50 entry fee turned into a five-figure liability because the API provider allowed charges to accumulate indefinitely beyond the prepaid amount.
The agent wasn't doing anything malicious. It was running the tasks it was configured to run. The problem: those tasks generated API calls, those calls had costs, and nothing in the stack — not the agent, not the API, not the billing system — said stop.
$50 in, $12,229 out. The agent did its job. The guardrails didn't exist.
Original post
— Ziwen (@ziwenxu_) March 24, 2026
More nightmares like this
$82,314 in 48 Hours: Stolen Gemini API Key With No Rate Limit
A stolen Gemini API key was used to rack up $82,314 in charges within 48 hours — Google had no rate limiting or spending cap to stop it.
$47,000 Gone: Multi-Agent System Ran an Infinite Loop for 11 Days Undetected
A multi-agent AI system got stuck in an infinite loop that ran for 11 days before anyone noticed, burning through $47,000 in API costs.
$1,100 in Debt, Agent Lost Identity, Developer Lost Control of Machine
An AI agent accumulated $1,100 in API debt, lost its own identity mid-session, and the developer lost control of their machine until they could kill all processes.
A Runaway AI Agent Burned Through an Entire API Budget in Hours
A practitioner watched in horror as an autonomous AI agent chewed through their entire API budget in a matter of hours — no rate limit, no kill switch, no mercy.