Incidents/ By cause/ Caps that didn't enforce/ chatgpt-removed-cap-1100
BLOCK Caps that didn't enforce OpenAI developer 2025

Account billed $1,100 after hard monthly cap was removed

A user reported a $1,100 bill after the platform's hard monthly spending cap was removed, turning the budget setting into a notification rather than an enforced limit.

Reported loss$1,100
Which rule would have stopped this?

A spend limit was set but not honored by the provider, so the agent kept spending past it. The fix is an independent, deterministic pre-spend check outside the provider's billing. independent per-tx cap would have rejected or flagged this transaction before any money moved.

Per-transaction cap
A single runaway purchase, a fat-finger API call, or an attacker testing how much they can move at once.
max_amount_usd: 500
Merchant allowlist
Prompt-injected purchases at unknown or malicious merchants.
allow: [openai.com, stripe.com]

Don't let this happen to your agents

sipi.bot evaluates every transaction an autonomous agent proposes and returns APPROVED, BLOCKED, or FLAGGED in under 5ms — before the money moves. Self-host the MIT core free, or use the hosted dashboard with human-in-the-loop approvals.

What happened

A user reported a $1,100 bill after the platform's hard monthly spending cap was removed, turning the budget setting into a notification rather than an enforced limit.

The root cause was classified as Platform cap failed to enforce. A spend limit was set but not honored by the provider, so the agent kept spending past it. The fix is an independent, deterministic pre-spend check outside the provider's billing.

This is one of 14 documented incidents in the open registry. Every entry is sourced to a public URL; amounts and dates are as reported by the source.

Related incidents

Caps that didn't enforce

OpenAI charged $1,200 past a configured $50 hard limit

OpenAI · 2025
$1,200 →
Caps that didn't enforce

Account billed $1,100 after hard monthly cap was removed

OpenAI · 2025
$1,100 →