​

Set a Hard Spend Ceiling for Codex at OpenAI

Everything here was checked on 2026-07-28 and every claim carries its source link. OpenAI changes these controls. Open the linked page yourself before you commit a budget to it.

​

Fail closed vs fail open (read this first)

• You want fail closed for the number you’d have to explain to your board. One ceiling at OpenAI, set once, that nothing gets past.
• You want fail open for the day-to-day. Per-developer visibility, a weekly budget, and a nudge that stops a runaway session long before it becomes the board conversation. That’s Track Claude Code & Codex Spend.

​

Find your billing mode first

​

API key billing

1. Go to Organization limits (https://platform.openai.com/settings/organization/limits).
2. Under Spend, select Edit spend limit.
3. Enter the Monthly spend limit.
4. Turn on Enforce a hard limit. This step is the one that makes it a wall instead of a note.
5. Select Save.

curl -X POST https://api.openai.com/v1/organization/spend_limit \
  -H "Authorization: Bearer $OPENAI_ADMIN_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "threshold_amount": 10000,
    "currency": "USD",
    "interval": "month"
  }'

An Admin key isn’t a developer key. It can change your billing controls. Keep it in your secret manager and run this from a machine you control. It never belongs on a developer’s laptop, and MarginFront never asks for it.

• Monthly only. The cap covers a monthly cycle and resets with the next one. There’s no weekly or per-developer version here.
• It overshoots a little. OpenAI is explicit: “Enforcement is not instantaneous. The API Platform can process a small amount of extra usage while the limit state propagates, so recorded spend can slightly exceed the configured amount.” Treat the number as a ceiling with a small ledge on top, not a razor line.
• Turning it back on takes a moment too. “Raising or removing the reached limit allows traffic to resume after the update propagates.”
• Two limits can both apply. An organization hard limit covers traffic across every project. A project hard limit covers only that project. Reaching either one returns the 429.
• Your tier’s usage limit is a separate thing. OpenAI also assigns your organization an approved monthly usage limit based on its usage tier. That isn’t the limit you set, and hitting it looks different when you’re diagnosing a 429.

​

ChatGPT Enterprise and Edu

• Usage limits set a monthly limit for each user. You can apply a workspace default, group defaults, and per-user overrides on top. Only workspace admins and owners can configure them.
• The workspace overage limit caps eligible usage beyond your committed plan. Set it to 0 and the workspace can’t go into overage at all. Leaving it on “No limit” means no cap is configured on eligible overage usage. “No limit” doesn’t make credits free; eligible overage usage continues and may be billed under your agreement.

• chatgpt.enterprise.usage_limit.read to read the current usage-limit settings.
• chatgpt.enterprise.usage_limit.write to change them.

• Monthly only, same as every other ceiling on this page.
• “Eligible workspace” isn’t defined publicly. Confirm with your OpenAI account contact that your workspace has the Spend Controls API before anyone plans work around it. The console controls are the safe assumption; the API is the one to verify.
• The API’s exact routes sit behind an authenticated reference. You need to be signed in as an admin to read them, so budget a little time before writing any automation.
• This covers ChatGPT workspace usage, not your API Platform bill. If you also run API keys, that’s a second ceiling in a different place. See API key billing.

OpenAI’s help center blocks automated readers. We confirmed the linked article’s contents through a rendering proxy on 2026-07-28. Open it in a browser yourself before you set policy off it.

​

ChatGPT Business

1. Go to Workspace settings, then Billing.
2. Find the seat type you want to cap and select Add to set a credit maximum.
3. To cap one person instead, select Manage on that seat type, then Add to set that person’s limit. A per-user limit overrides the seat-type limit.

• Console only. The Spend Controls API is an Enterprise and Edu feature. On Business, somebody sets these by hand, so put a calendar reminder on reviewing them.
• Monthly only, same as the rest.
• Unset is the dangerous state, and it’s also the shipped state.

​

ChatGPT Plus and Pro

1. Move those developers to a billing mode that has a ceiling. An API key on your organization, or a Business, Enterprise, or Edu workspace seat. This is the only way to get a fail-closed stop for their Codex work.
2. Accept a fail-open guardrail and know what you bought. MarginFront’s device cap meters the spend and pauses work on machines where it’s installed. A developer can take it off, and it can’t see a machine that never installed it. For personal seats it’s the only control that exists, and it’s a seatbelt.

​

What none of these do

• Monthly only. Every OpenAI ceiling here runs on a monthly cycle. You can’t express “$200 per developer per week” at OpenAI. That shape of budget has to live somewhere else.
• One provider only. An OpenAI ceiling caps OpenAI. It knows nothing about what your team spends with Anthropic, Google, or xAI, so it can’t be your whole-company AI budget.
• Alerts notify. They don’t stop. The documented notification channel for spend alerts is email. An alert is a heads-up, not a brake.
• Codex has no dollar cap of its own. There’s no “cap Codex at $X” switch inside Codex. Every stop above is an account control that Codex activity draws against. OpenAI says it plainly about the workspace controls: they “aren’t a universal Codex limit system and don’t govern OpenAI API Platform billing.”
• Enforcement isn’t instant. Expect a small overshoot on the way up and a short delay on the way back down after you raise a limit.

​

Belt and suspenders