OpenAI's usage limit won't stop your spending — here's what actually does (2026)

Russel — Tue, 30 Jun 2026 11:00:00 +0000

You set an OpenAI usage limit. You felt responsible. Then the invoice landed higher than the number you typed, and you sat there wondering what the limit was even for.

The short version, up front: OpenAI's "usage limit" does not stop your spending. It sends an email when you cross a threshold while your requests keep going. It's a smoke alarm, not a circuit breaker. The only things that actually cap an OpenAI bill are running out of prepaid credit and your auto-recharge settings. Below is how that works in 2026, what changed this year, and what to bolt on so the bad number reaches you before your card does.

One disclosure first: I build a tool in this space — BillGuard — so read the last section as biased and judge it on the merits. Everything before it is just how the billing works.

Does the OpenAI usage limit actually stop spending? No.

Open Settings → Limits and you'll find a "monthly budget" or usage limit. It looks like a cap. It reads like a cap. It is not a cap.

Cross that number and OpenAI emails you. Your requests keep going. There used to be a real hard limit that suspended API access at the ceiling, and OpenAI removed it — quietly, with the old setting relabeled from a cut-off to an alert. There's a whole "OpenAI removed budget limits, you can only get warnings" thread on Hacker News, and the developer forum still has standing requests to bring the hard cap back, because prepaid billing leaves no upper bound if a key leaks or a loop runs wild.

So the mental model most of us carry — "I set a limit, so I'm safe" — is wrong. You set an alert. The meter keeps running while you're asleep, in a meeting, or just not refreshing the dashboard.

So what actually stops an OpenAI runaway bill?

Mostly one thing: running out of prepaid credit.

New API accounts are on prepaid billing. You buy credits, usage burns them down, and per OpenAI's own docs, "your API usage will be halted once your account balance reaches $0." That's the real hard stop. Not the usage limit. The empty wallet.

Now the trap: auto-recharge. It's offered when you set up prepaid billing, and it tops your balance back up the moment it dips below a threshold. So the one mechanism that would halt a runaway loop — hitting zero — never fires. The balance refills itself, the loop keeps calling, and you meet the damage on the receipt.

That's the surprise-bill machine in two parts: a soft "limit" that only notifies, plus an auto-recharge that quietly removes the only real brake.

Wait — didn't per-project limits used to work?

They did, loosely, and this is the part most 2026 guides haven't caught up to. Until recently the standard advice was: put production behind a project-scoped key, set a per-project hard limit, and OpenAI would stop that project a few dollars over the cap. Imperfect, but real.

Around May 2026, developers started reporting that this stopped working too. In one forum thread, an org owner watched a project run to $1,800 on a $1,000 cap while still showing green, and the "set a budget" buttons disappeared for both projects and the organization — replaced with alert-only language. Other owners in the same thread confirmed the per-project enforcement they'd relied on was gone, leaving a "x used of y limit" progress bar that no longer does anything.

I'm flagging this as reported behavior, not a documented OpenAI change — your account may differ, so check yours. But if your safety plan is "production runs on a project key with a hard limit," it's worth re-testing, because for a lot of people that net quietly disappeared this year.

The OpenAI controls that still help, ranked

OpenAI does give you real knobs. They're just not the ones the name implies, and after this year the useful list is shorter.

Auto-recharge settings — your closest thing to a real ceiling. Turn auto-recharge off and you hard-stop at $0 when credits run out. Leave it on but set a low monthly recharge cap and it can't top up past that amount in a given month. Pair that with a modest balance and your trust-tier limit caps how much can be in the account at once. This is now the main lever people actually have.
Project-scoped API keys — for blast radius, not budgets. Create a project, generate a key tied to it, and that key only touches that project's resources. If it leaks, the damage is one project, not your whole org. Still the most underused safety feature OpenAI ships — docs here. Just don't count on the per-project spend limit to stop anything in 2026 (see above).
The Usage and Cost APIs. OpenAI exposes spend programmatically, including a /v1/organization/costs endpoint broken down by minute, hour, and day and filterable by key, project, or model. You can't watch a dashboard you've closed — but you can poll an API. This is the hook everything external hangs off.

Is Anthropic any better at capping spend?

Cleaner story, fewer feet-guns. Anthropic's API has an actual spend cap that behaves like one. Per the Claude rate-limits docs, each usage tier carries a monthly spend cap — $500 on Start, $1,000 on Build, $200,000 on Scale — and "once you reach your tier's spend cap, API usage pauses until the next month." You can also set your own lower spend limit beneath the tier cap, and apply custom per-workspace spend and rate limits.

So if you assumed Anthropic was the loose one, flip it: hit the ceiling and it stops. The by-the-hour visibility is thinner than I'd like, and there's one caveat — on AWS Marketplace those spend limits aren't available — but the headline control actually works.

Soft vs hard, native vs external — the whole thing in one table

Mechanism	Stops spend, or just warns?
OpenAI "usage limit" / monthly budget	Warns. Requests keep going.
OpenAI per-project budget (historically)	Used to stop loosely; reported broken/removed in 2026.
OpenAI prepaid balance hits $0, auto-recharge OFF	Real stop.
OpenAI prepaid + auto-recharge ON, no monthly cap	No stop. Balance silently refills.
OpenAI auto-recharge with a low monthly cap	Soft ceiling — closest native control.
Anthropic spend limit / tier cap	Real stop. Pauses until next month.
External real-time alert (poll Usage/Cost API)	Early warning, by your actual spend.

How do I actually get warned before the invoice?

Every native control above shares one flaw. None of them reach you in real time, by your actual spend, somewhere you'll see it. A dashboard you check on Tuesday won't save you from a loop that starts Friday night. What "good" looks like is dumb and specific: the moment your real spend crosses a line you care about, a message lands on your phone that night, not on the 1st of next month. Three ways to get there:

Roll your own. Cron job, hit /v1/organization/costs hourly, compare to a number, ping a webhook. A weekend's work, and now you own a tiny billing service forever. Plenty of people do exactly this, and it's a perfectly good answer if you don't mind babysitting a cron job.

Use a FinOps platform. CloudZero, Vantage, Finout, Amnic — anomaly detection, team allocation, the lot. Built for finance orgs spreading real money across teams. For a solo dev shipping a side project, it's a freight train to fetch groceries.

Use a lightweight alerting tool. This is the indie-sized slot, and it's filling up. Capped does this — an hourly check against the cost API, pings at 80/100/150% of a cap you set. Worth a look. Helicone used to be the default recommendation, but it was acquired by Mintlify in March 2026 and is now in maintenance mode — security fixes only, no roadmap — and it typically sits in your request path as a proxy, which not everyone wants in front of production traffic.

Where BillGuard fits (the biased part)

Disclosure again: my product, weigh it accordingly.

BillGuard is the "roll your own" option without the weekend, and read-only by design. You hand it a read-only admin key for OpenAI or Anthropic — no proxy, no SDK, nothing in your request path — and it polls your real spend, forecasts where the month lands, and pings you on email, Telegram, or Slack the second you cross a line you set. Setup is about thirty seconds. Founding plan is $7/month.

The forecast is the part I actually care about: not just "you hit 80%," but "at this rate you'll land at $X by the 30th," while there's still time to do something. And because it never touches your traffic, it can't add latency or become a thing that goes down and takes you with it.

It does not stop your spend — nothing external can, short of pulling your key — but it makes the bad number reach your phone hours before it reaches your card.

If you've ever set a usage limit and assumed you were covered, that assumption is the whole reason this exists. And if you'd rather wire up the cron job — genuinely, go do it. The point of this post isn't the tool. It's that the native limit was never the safety net you thought it was, and in 2026 even the project-level one quietly went away. What you bolt on next is your call.

FAQ

Does setting a usage limit in OpenAI actually cap my spending?
No. The usage limit is a notification threshold, not an enforced cap. OpenAI emails you when you cross it and keeps processing your requests. The only native hard stop is your prepaid balance reaching $0 with auto-recharge off.

What actually stops an OpenAI API runaway bill?
Running out of prepaid credit. If auto-recharge is on with no monthly cap, the balance refills and nothing stops. Turning auto-recharge off, or setting a low monthly recharge cap, is the closest thing OpenAI gives you to a real ceiling.

Do per-project spending limits work in 2026?
They used to stop a project loosely a few dollars over its cap, but as of around May 2026 developers report that enforcement was removed and the UI now offers alerts only. Project-scoped keys are still worth using to limit blast radius if a key leaks — just don't rely on the per-project budget to halt spend.

Does Anthropic's Claude API have a real spending cap?
Yes. Each usage tier has a monthly spend cap (Start $500, Build $1,000, Scale $200,000) and usage pauses until the next month once you hit it. You can also set a lower spend limit yourself. The exception is AWS Marketplace, where spend limits aren't available.

How do I get a real-time alert before the bill arrives?
Poll OpenAI's /v1/organization/costs endpoint (or Anthropic's Usage & Cost API) on a schedule and alert when spend crosses a threshold. You can build this yourself with a cron job, or use a lightweight tool like Capped or BillGuard that does the polling and notifies you on email, Telegram, or Slack.

Written by Russell, who builds BillGuard. Originally published on the BillGuard blog.

DEV Community: Russel