The short version: A leaked API key or a runaway agent can turn a $180 month into an $82,000 bill in 48 hours, and the providers most people assume will stop it usually will not. Google Cloud budgets are alerts, not caps. OpenAI removed its hard spending limit and left a notification behind. Anthropic is the outlier with real per-workspace spend limits. The reliable defense is a stack that combines independent metering with a balance or budget store, anomaly detection, and an application-side circuit breaker that can actually revoke access. UsageBox can supply the metering record; the inline balance and blocking decision still belong in your gateway or policy system.
The story repeats often enough that it has become a genre. A small team's Google Cloud key is exposed, an attacker drives Gemini calls around the clock, and the owner wakes up to a bill that could end the company. One widely shared case on r/googlecloud was titled "$82,000 in 48 Hours from stolen Gemini API Key. My monthly Usage Is $180. Facing Bankruptcy." Another team, a small company in Japan, reported about $128,000 in unauthorized Gemini usage, and the charges kept climbing even after they paused the API.
The reactions in those threads are not about one stolen key. They are about a structural gap: people assume usage-based billing comes with a hard ceiling, and it almost never does. As one commenter put it, "Google do not allow spend caps... how on earth can they allow anyone to run up bills like this with no financial checks is beyond me." This is about closing that gap, including the parts your provider cannot help you with.
Why a budget alert is not a kill-switch
The most expensive misunderstanding in usage-based spend is treating an alert as a control. An alert tells a human something happened. A cap stops the thing from happening. The major providers draw that line in different places.
| Provider | What the "limit" actually does | Hard cutoff available? |
|---|---|---|
| Google Cloud / Gemini API | Budgets send alert emails and Pub/Sub messages. Google's own docs state that "setting a budget does not automatically cap" usage or spending. | Not natively. You build it yourself with a Pub/Sub topic and a Cloud Function that disables billing on the project. |
| OpenAI API | A monthly budget is a soft threshold. Once exceeded, "API requests will continue to be processed without interruption." The old hard cap was removed in late 2025. | No. Notification only. |
| Anthropic / Claude API | Per-tier monthly spend limits, plus custom per-workspace spend and rate limits, and per-user limits on the Claude Code workspace. Hit the limit and the API stops until the next cycle. | Yes, the closest to a real native cap of the three. |
Two of the three big AI vendors give you a doorbell, not a deadbolt. And even the deadbolt has a delay, which is the next trap.
The reporting-lag trap that turns a cap into a leak
Even when you act fast, billing data does not arrive in real time. Google documents that it "might take up to two days for usage charges in the project to be reported," and that after you disable billing, "usage charges that accrue prior to disabling billing... are billed," including charges not yet in the transaction history. That is exactly what the Japanese team hit: they paused at roughly $44k and watched it climb past $128k as already-incurred usage caught up.
The lesson is precise. A control that depends on the provider's billing pipeline to notice the overspend is always running minutes-to-days behind the attack. To stop a runaway in seconds you need a meter you own, in the request path, counting before the provider's invoice does. That is the difference between watching the bill and stopping the spend.
The four controls that actually contain a runaway
Containment is not one feature, it is a short stack of them, applied cheapest-first. None requires you to trust the provider's billing lag.
1. A real-time balance, not an end-of-month total
Every billable call should update a live balance or budget counter in the request path you control. You cannot enforce a cap you only compute at invoice time. UsageBox can record the same billable quantities independently for audit and reconciliation, but it does not hold or authorize against a live remaining balance. The enforcement architecture shows how to keep the fast policy decision and the durable meter separate.
2. Hard caps scoped to the blast radius
One global monthly cap is too coarse. A stolen key should be able to burn only its own slice, not the whole account. Set caps per API key, per customer, and per environment, so a compromised production key trips long before it can touch the org-wide ceiling. Scoping caps tightly is also how multi-tenant platforms keep one bad actor from spending another tenant's budget, an extension of the isolation work in securing API keys for multi-tenant systems.
3. Anomaly and spike alerts measured in seconds
An $82k incident from a $180 baseline is a 455x spike. That is not subtle, and a rate-of-change detector catches it in the first minutes if it is watching the live meter rather than the daily billing export. Alert on velocity (spend per minute against the trailing baseline), not just on absolute thresholds, so a slow drain and a fast burst both trip. The event-driven alerting pattern in the real-time usage alerting architecture is built for exactly this: invalidate on each event, collapse bursts, and fire without polling lag. This is the early-warning sibling of margin billing drift detection, except here the stakes are a fraud bill, not a slow margin leak.
4. A circuit breaker that revokes, not just warns
The alert has to be able to pull the cord. When velocity or balance crosses the line, the breaker revokes the offending key, flips a feature flag, or returns a hard error at your gateway, before the next expensive call leaves your network. Because the decision runs against a meter you control, it triggers in seconds rather than waiting on the provider's two-day reporting window. The enforcement loop in the usage enforcement guide shows the mechanics: check the balance, flag a hard-stop policy, refuse the request.
Where the metering layer ends and the provider begins
This is not a silver bullet, so here is the boundary. A meter in your request path stops spend that flows through your application. It cannot stop spend on a key an attacker is calling the provider with directly, outside your infrastructure, using a credential that leaked to a public repo. For that exposure you still need provider-side controls: Anthropic's workspace spend limits, a Google Cloud Pub/Sub-to-Cloud-Function killswitch that disables billing, key rotation, and not committing secrets in the first place. The honest architecture is both layers. Your meter contains the runaway agent and the leaked key used through your app in seconds; the provider cap and good key hygiene contain the key used against the provider directly. The metering layer shrinks the blast radius, but it sits next to provider caps, it does not replace them.
An incident runbook worth writing down before you need it
- Detect: Velocity alert fires when spend-per-minute exceeds the trailing baseline by your multiple (a small multiple catches the slow drains too).
- Contain: The circuit breaker revokes the implicated key and flips the tenant or environment into a refuse-and-log mode at the gateway.
- Pull provider levers in parallel: Disable the API or project upstream, rotate the credential, and on Anthropic let the workspace spend limit hold the line.
- Reconcile: Expect the provider total to keep climbing for hours as lagged usage reports in. Reconcile your meter against the eventual invoice and keep the timestamped trace for any dispute, the same audit discipline behind defending unexpected bills.
- Tune: Lower the scoped cap for that key class and shorten the alert window. Almost every horror story shares one detail: no cap, no alert, or both set far too loose.
The teams who avoid the front-page bill are not the ones who never get a key stolen. They are the ones whose meter noticed in the first two minutes and whose breaker had the authority to say no. The flat-rate era is ending and variable spend is now permanent, which is exactly why a cap you control beats a budget you only get notified about. We cover the budgeting side of that shift in budgeting when flat-rate plans disappear.