ChatGPT Pro and Business Now Include Up to $500 a Month in OpenAI API Credits, but You Must Claim Them and They Expire Every Cycle
- What happened
- On 28 October 2026 OpenAI began letting eligible ChatGPT Pro and Business subscribers claim monthly API credits: $100 to $500 on Pro, $20 or $100 per Business seat, capped at $500 per workspace.
- Why it matters
- Nothing is granted until you claim it, unused credits expire each billing cycle, and Codex through API keys is excluded.
- What to do
- If you are eligible, claim the credits in billing settings and link the right API organization before your cycle ends.
Our verdict: if you pay for ChatGPT Pro or Business and also build on the OpenAI API, claim these credits today. It is free API spend that you lose by not clicking, and it works on the APIs we track as conditional picks, the OpenAI Agents API and the OpenAI Decisions API. It is not a subsidy for OpenAI Codex: Codex through API keys is excluded, and the credits do not raise any ChatGPT or Codex usage limit.
What happened
OpenAI's API changelog entry for 28 October 2026 reads: "Eligible ChatGPT Pro and Business subscribers can now claim up to $500 per month in free API credits as a subscription benefit." OpenAI's guide sets the amounts:
| Plan | Monthly API credits |
|---|---|
| Pro ($100 tier) | $100 |
| Pro ($200 tier) | $200 |
| Pro ($500 tier) | $500 |
| Business Standard | $20 per paid Standard seat |
| Business Premium | $100 per paid Premium seat |
"Business API Credits are pooled and capped at $500 per workspace per month." So "up to $500" means the top Pro tier or a Business workspace's ceiling, not what every subscriber gets. ChatGPT Enterprise is not eligible.
Who qualifies
Per the guide, you need an active, paid Pro or Business subscription that is at least seven days old. You must own both the subscription and the API organization that receives the credits, and you must use the same email address on your ChatGPT account and on the API account that links the organization.
What the credits pay for
The credits cover the Responses, Agents, Decisions, GPT-Live, Realtime and Images APIs, plus built-in tools such as web search and Code Interpreter. "Codex usage through API keys is not supported by this benefit."
Why it matters
- Nothing is automatic. The benefit sits in billing settings until you claim it and link an API organization.
- Use it or lose it. Unused credits expire at the end of each billing cycle and do not roll over. "Your first grant is prorated for the time left in your current subscription billing cycle."
- Credits-only apps stop, they do not bill. No API payment method is required. When the credits run out and you hold no purchased balance, "API requests fail with HTTP 429 and error code credit_balance_exhausted."
- Business value scales badly. At $20 or $100 per seat with a $500 workspace cap, the pool matters for a team of five and barely registers for a team of fifty.
For a Pro subscriber who already spends on the API, this is a straight monthly discount worth up to the tier price. The real catch is operational: anything you run on the credits alone goes down with a 429 the moment they are spent.
What changes for you
- Check eligibility. Paid Pro or Business plan at least seven days old, ownership of both the subscription and the API organization, same email on both accounts.
- Claim and link. Go to ChatGPT Settings, Billing (Pro), the workspace billing page (Business) or the Billing section of the API Platform, then pick the organization to link.
- Handle exhaustion. If an app runs on these credits alone, catch HTTP 429 with error code credit_balance_exhausted, or add a purchased balance.
- Leave Codex out of the plan. Codex API-key usage is excluded, so budget for it separately.
What to do
- 1 Check eligibility: a paid Pro or Business subscription at least seven days old, ownership of both the subscription and the API organization, and the same email on both accounts.
- 2 Claim the credits from ChatGPT Settings, Billing (Pro), workspace billing (Business) or the API Platform's Billing section, and link the API organization.
- 3 If an app runs on these credits alone, handle HTTP 429 with error code credit_balance_exhausted, or add a purchased balance.
- 4 Do not plan Codex API-key usage around these credits; it is excluded.
Affected tools & models
Never need to catch up again
The weekly delta: only verdict changes and act-now items. No digest filler.