<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel>
<title>sipi.bot — AI Agent Spending Incidents</title>
<link>https://incidents.sipi.bot/</link>
<description>Sourced registry of runaway-spend incidents caused by autonomous AI agents.</description>
<language>en</language>
<item>
<title>Autonomous agent ran up a $6,531.30 AWS bill in a retry loop</title>
<link>https://incidents.sipi.bot/incidents/aws-dn42-6531-retry/</link>
<guid>https://incidents.sipi.bot/incidents/aws-dn42-6531-retry/</guid>
<pubDate>Mon, 01 Jun 2026 00:00:00 +0000</pubDate>
<description>An autonomous agent tasked with registering for and scanning the DN42 hobbyist network became stuck in a retry loop, repeatedly spinning up duplicate CloudFormation stacks on every error because nothing told it to stop. Cause: Retry / infinite loop. Loss: $6,531.30.</description>
</item><item>
<title>AI coding agent bills hit $2,000–$20,000 per developer per month</title>
<link>https://incidents.sipi.bot/incidents/coding-agent-bills-20k-month/</link>
<guid>https://incidents.sipi.bot/incidents/coding-agent-bills-20k-month/</guid>
<pubDate>Mon, 01 Jun 2026 00:00:00 +0000</pubDate>
<description>AI coding-assistant bills were documented leaping from $20–$100 to $2,000–$5,000 per developer per month, with extreme cases reaching $20,000/mo in token charges — now exceeding a developer&#x27;s base salary in some firms. Reported by The Register, June 2026. Cause: Unattended / overnight session. Loss: $2,000–$20,000/mo.</description>
</item><item>
<title>Developer spent $11,922 on Cursor in under four weeks</title>
<link>https://incidents.sipi.bot/incidents/cursor-11922-4weeks/</link>
<guid>https://incidents.sipi.bot/incidents/cursor-11922-4weeks/</guid>
<pubDate>Sun, 01 Feb 2026 00:00:00 +0000</pubDate>
<description>A developer ran six Cursor windows in parallel, each pointed at a different project with autonomous agents. Context length and token costs compounded across two billing cycles ($4,339 then $7,583), with a single premium model accounting for over $9,400. Cause: Unattended / overnight session. Loss: $11,922.</description>
</item><item>
<title>Developer spent $4,000 on AI coding when prod behaved like dev</title>
<link>https://incidents.sipi.bot/incidents/ai-coding-4000-dev-prod/</link>
<guid>https://incidents.sipi.bot/incidents/ai-coding-4000-dev-prod/</guid>
<pubDate>Mon, 01 Dec 2025 00:00:00 +0000</pubDate>
<description>A developer reported burning through $4,000 in AI-coding API costs because behavior that worked in development kept looping in production. Cause: Retry / infinite loop. Loss: $4,000.</description>
</item><item>
<title>No-code agent silently burned $800+ in API calls overnight</title>
<link>https://incidents.sipi.bot/incidents/nocode-agent-800-overnight/</link>
<guid>https://incidents.sipi.bot/incidents/nocode-agent-800-overnight/</guid>
<pubDate>Sat, 01 Nov 2025 00:00:00 +0000</pubDate>
<description>A developer woke up to $800+ in API charges from a rogue agent loop. No alerts, no circuit breaker, and no spend cap were in place. Cause: Retry / infinite loop. Loss: $800+.</description>
</item><item>
<title>Background orchestration agent stuck in an error-handling loop</title>
<link>https://incidents.sipi.bot/incidents/langchain-orchestration-loop/</link>
<guid>https://incidents.sipi.bot/incidents/langchain-orchestration-loop/</guid>
<pubDate>Sat, 01 Nov 2025 00:00:00 +0000</pubDate>
<description>A background orchestration agent entered an error-handling retry loop and consumed its API budget before anyone noticed. Part of a community megathread of runaway-agent stories. Cause: Retry / infinite loop. Loss: Cost not disclosed.</description>
</item><item>
<title>OpenAI agents burned $72,000 in a single night</title>
<link>https://incidents.sipi.bot/incidents/openai-72k-overnight/</link>
<guid>https://incidents.sipi.bot/incidents/openai-72k-overnight/</guid>
<pubDate>Wed, 01 Oct 2025 00:00:00 +0000</pubDate>
<description>Autonomous agents on the OpenAI API Platform ran up roughly $72,000 in charges in one night before any limit intervened. The incident prompted OpenAI to expand hard spend limits to all API accounts. Cause: Unattended / overnight session. Loss: $72,000.</description>
</item><item>
<title>Account billed $1,100 after hard monthly cap was removed</title>
<link>https://incidents.sipi.bot/incidents/chatgpt-removed-cap-1100/</link>
<guid>https://incidents.sipi.bot/incidents/chatgpt-removed-cap-1100/</guid>
<pubDate>Wed, 01 Oct 2025 00:00:00 +0000</pubDate>
<description>A user reported a $1,100 bill after the platform&#x27;s hard monthly spending cap was removed, turning the budget setting into a notification rather than an enforced limit. Cause: Platform cap failed to enforce. Loss: $1,100.</description>
</item><item>
<title>OpenAI charged $1,200 past a configured $50 hard limit</title>
<link>https://incidents.sipi.bot/incidents/openai-hardlimit-ignored-1200/</link>
<guid>https://incidents.sipi.bot/incidents/openai-hardlimit-ignored-1200/</guid>
<pubDate>Mon, 01 Sep 2025 00:00:00 +0000</pubDate>
<description>A user reported being charged $1,200 despite setting a soft limit of $30 and a hard limit of $50, alleging the configured caps were not honored by the platform. Cause: Platform cap failed to enforce. Loss: $1,200.</description>
</item><item>
<title>Leaked Gemini API key led to a $55,444.78 Google Cloud bill</title>
<link>https://incidents.sipi.bot/incidents/gemini-key-55k-gcp/</link>
<guid>https://incidents.sipi.bot/incidents/gemini-key-55k-gcp/</guid>
<pubDate>Tue, 01 Jul 2025 00:00:00 +0000</pubDate>
<description>A student was billed $55,444.78 on Google Cloud after a Gemini API key was leaked through a public GitHub repository and abused. Cause: Leaked / stolen credential. Loss: $55,444.78.</description>
</item><item>
<title>Google Maps API bill hit ~$10,000 in four days</title>
<link>https://incidents.sipi.bot/incidents/google-maps-api-10k-4days/</link>
<guid>https://incidents.sipi.bot/incidents/google-maps-api-10k-4days/</guid>
<pubDate>Thu, 01 May 2025 00:00:00 +0000</pubDate>
<description>A developer reported a bill close to $10,000 after four days of working with the Google Maps API, with runaway calls outpacing expected usage. Cause: Retry / infinite loop. Loss: ~$10,000.</description>
</item><item>
<title>Fake bug report tricked an agent into leaking a live AWS key</title>
<link>https://incidents.sipi.bot/incidents/aws-key-fake-bug-report/</link>
<guid>https://incidents.sipi.bot/incidents/aws-key-fake-bug-report/</guid>
<pubDate>Thu, 01 May 2025 00:00:00 +0000</pubDate>
<description>A crafted bug report manipulated an autonomous agent into exfiltrating a live AWS access key, exposing the owner to arbitrary downstream spend. Dollar loss was not disclosed. Cause: Prompt injection / manipulation. Loss: Cost not disclosed.</description>
</item><item>
<title>Opaque per-token pricing triggered billing shock</title>
<link>https://incidents.sipi.bot/incidents/cline-burn-rate-shock/</link>
<guid>https://incidents.sipi.bot/incidents/cline-burn-rate-shock/</guid>
<pubDate>Tue, 01 Apr 2025 00:00:00 +0000</pubDate>
<description>Developers reported billing shock from high token burn rates and opaque pay-as-you-go pricing on coding agents, with several exceeding expected daily budgets by an order of magnitude. Cause: Unattended / overnight session. Loss: Cost not disclosed.</description>
</item><item>
<title>Founder spent $638 on Cursor AI coding in six weeks</title>
<link>https://incidents.sipi.bot/incidents/cursor-638-6weeks/</link>
<guid>https://incidents.sipi.bot/incidents/cursor-638-6weeks/</guid>
<pubDate>Fri, 01 Nov 2024 00:00:00 +0000</pubDate>
<description>A founder-CTO accumulated $638 in Cursor on-demand charges over about six weeks (later $928.45 over 70 days), driven by bursts of high-frequency requests and a premium thinking model. Cause: Retry / infinite loop. Loss: $638.</description>
</item>
</channel></rss>