Every few months a thread pops up on r/OpenAI or the OpenAI developer forum asking the same question: "how do I set a hard cap so my API key literally stops working at $X?" The answer, as of today, is still: you can't - not for a personal/solo account, not through the dashboard.
Here's what actually exists, what it doesn't do, and what I ended up building after hitting this wall myself.
What OpenAI's dashboard actually gives you
The Usage page lets you set a monthly budget with email notifications at certain thresholds. Two important limitations:
- It's a notification, not a circuit breaker. Requests keep succeeding after you cross the number - you just get an email.
- Org-level hard caps exist, but they're built for teams with an admin managing seats, not a solo dev with one key.
If you've ever gotten the "you're at 100% of your budget" email a day after a retry loop already ran up the bill, you already know the gap.
The DIY fix (and why most people don't finish it)
OpenAI does expose a real usage API scoped to api.usage.read - an Admin key can be scoped to only that permission, no ability to spend or touch account settings. That's the right building block: read usage, compare to a threshold, alert yourself.
The DIY version is a cron job that polls the usage endpoint, keeps a running total, and fires an email past your threshold. Maybe 100 lines. The part that actually eats the time isn't the logic - it's everything around it: where does the cron run, how do you not lose state on restart, how do you get email delivery that doesn't land in spam, and who's going to remember to keep it patched six months from now when OpenAI tweaks the endpoint.
That maintenance tax is why most people who start this project don't finish it. I didn't, the first two times.
What I built instead
Fusebox is the hosted version of exactly that loop: you give it a read-only Admin key (scoped to api.usage.read, nothing else - it can see your usage numbers, it cannot spend a cent or touch your account), set a dollar ceiling, and it emails you before you blow past it. Free tier covers the basic ceiling-alert; a paid tier adds faster check intervals.
To be direct about what it isn't: it's not a hard stop. Nothing except OpenAI itself can actually refuse a request once you're over budget - that part of the original complaint is still unsolved by anyone, including me. What it does fix is the gap between "the bill already happened" and "you find out about it," which for a solo dev running agents or retry-prone pipelines is usually the actual problem.
If you've built your own version of this cron job, I'd genuinely like to hear how you handled the maintenance side - that's the part I'm least confident I've gotten right.
Top comments (0)