ChatGPT Pro and Business Now Include Up to $500 a Month in Free API Credits

OpenAI now hands eligible ChatGPT Pro and Business subscribers up to $500 a month in free API credits. The API changelog entry dated October 28, 2026 describes it as a subscription benefit: link an API organization you own, and credits arrive when the subscription renews. The details live in OpenAI's guide, API credits for ChatGPT subscribers.

In plain terms, a Pro subscription now pays itself back in API spend, and small Business teams get a per-seat credit. It is also a direct answer to a comparison readers have been making for weeks, which we covered in SemiAnalysis: Claude plans give 5x more API value than ChatGPT. Anthropic made a similar move earlier this month, covered in Claude Max and Team API credits: how to claim.

TL;DR: the benefit in one table

How much does each plan get?

For Pro, the rule is simple: the credit matches the tier price. The $100 tier gets $100, the $200 tier gets $200, and the $500 tier gets $500. OpenAI's guide lists exactly that table. If you upgrade mid-cycle, the guide says you can receive extra prorated credits for the rest of the billing cycle, and later grants reflect the new plan's allowance, up to $500 per billing cycle.

Business works per seat. Standard seats bring $20 each and Premium seats bring $100 each, but the whole workspace is capped at $500 per month. By simple arithmetic, the cap is reached at 25 paid Standard seats or 5 paid Premium seats. A 60-seat Standard workspace therefore gets the same $500 pool as a 25-seat one. Workspaces that pay annually upfront receive the full year's grant in one issuance, and that grant expires at the end of the annual billing cycle. The guide gives a $6,000 ceiling for annual cycles.

Seat changes matter too. Adding paid seats or upgrading seat types mid-cycle can provide extra prorated credits, still subject to the shared cap. Seat reductions affect the next cycle, and reassigning an existing seat to another person creates no extra credit. For background on the Premium seat itself, see ChatGPT Business Premium seats at $100.

Balance scale weighing a subscription card against token chips, showing ChatGPT API credits versus plan price

What do the credits actually pay for?

The credits cover paid API Platform usage billed to the linked organization. OpenAI lists these surfaces:

• The Responses API for text, code, and image understanding.
• The Agents API, including OpenAI-hosted sandbox charges.
• The Decisions API for structured decisions.
• GPT-Live and the Realtime API for real-time voice.
• The Images API for generation and editing.
• Built-in tools and their usage and storage charges, such as web search, file search, and Code Interpreter.

That is a broad list, and it includes the pieces most builders actually spend on. Sandboxes and hosted tools are often the surprise line items on an agent bill, so having them eligible is useful. What each dollar buys depends on the model. OpenAI's API pricing page is the source of truth, and our reporting on the cheaper flagship tier is in GPT-6.1 Terra launch pricing and benchmarks. For a view across tiers, see GPT-6.1 Sol versus Astra cost efficiency.

The Codex catch

The most important exclusion is in one sentence of the guide: "Codex usage through API keys is not supported by this benefit." The credits also "don't increase your ChatGPT or signed-in Codex usage limits."

That matters because many Pro subscribers are heavy Codex users. If your workflow is Codex signed in with ChatGPT, nothing changes. If you run Codex against an API key, those calls cannot burn the free credits. The credits only help if you also build something on the Responses, Agents, Realtime, or Images APIs. OpenAI's earlier programs followed a different pattern; our piece on Codex for open source grants shows how Codex-specific perks were handled there.

Who qualifies, and how do you claim?

OpenAI lists three conditions:

1. An active, paid ChatGPT Pro or Business subscription that is at least seven days old. Free trials and complimentary subscriptions do not qualify.
2. You own the ChatGPT subscription or Business workspace and also own the API organization that will receive the credits.
3. The ChatGPT account and the API account use the same email address.

There are two ways to claim, and both link the same benefit to the API organization you choose.

From ChatGPT: sign in with the account that owns the subscription. For Pro, open Settings, then Billing. For Business, open your workspace billing settings or the Admin Console. Find the API credits benefit, review the organization that will receive the credits, and confirm.

From the API Platform: sign in with the email tied to your subscription, pick the API organization, open Billing, find the API credit benefit, choose the eligible subscription or workspace, and confirm.

New API users can link their subscription to a Personal API Organization. After claiming, the Billing settings in API Platform show the credits. The guide also points to the OpenAI Developers plugin in ChatGPT, which can create API keys for you securely.

Grants are organization-specific. Use one of the linked organization's project API keys, or your requests will not draw on the credits. If you need to change the linked organization later, OpenAI says to contact support.

What happens when the credits run out?

Tap above a usage meter counting drops, illustrating free OpenAI API credits being spent down

The organization uses free credits before purchased credits. If you have purchased balance, usage continues on it. If you have none, requests fail with HTTP 429 and the error code credit_balance_exhausted. To keep running, add paid credits or set up Auto Recharge.

This is worth designing around before you ship an agent. An exhausted balance is a hard stop, not a slowdown. If an app of yours depends on these credits, add handling for that exact error code, alert on remaining balance, and decide whether you want Auto Recharge to quietly convert a free benefit into a paid bill. Since the credits expire monthly, a usage spike at the end of a cycle is cheap, while a spike at the start can leave you dry for weeks.

What changes when your plan changes?

The guide spells out several edge cases that are easy to miss:

• Cancellation: new grants stop, but cancelling alone does not revoke credits already issued. You can use them until they expire.
• Downgrade to Plus, Go, or Free: the API organization link is removed at the end of the billing cycle.
• Pro to Business: moving to Business ends the Pro link. After the Business workspace has been paid for seven days, a workspace owner can create a new link.
• Business to Enterprise: the link is removed at the end of the billing cycle, because Enterprise is not eligible.
• Rate limits and terms: the benefit is subject to API terms and policies, including API rate limits for your organization and models.

Who comes out ahead?

This is our read, not OpenAI's.

API builders already on Pro. If you spend at least your tier price on the API each month, the subscription effectively pays for itself. If your API spend is lower, you leave credit unused, because it does not roll over.

Small Business teams. Up to the cap, every seat brings its full credit. A five-seat Premium team gets $500 of API room to prototype internal agents without a separate billing setup.

Large Business workspaces. The fixed $500 cap means the per-seat value shrinks as you add people. It is a nice bonus, not a budget line.

Codex-first developers. Little changes unless you also call the API outside Codex.

Teams comparing vendors. The benefit narrows a gap that analysts had pointed at. In the SemiAnalysis comparison, the question was how much API value each plan hides inside the subscription. OpenAI's move converts part of a subscription into explicit API money, which is easier to reason about than opaque usage windows. Whether it matches Anthropic's version depends on tier and workload, so test your own usage rather than trusting a headline number.

What we do not know yet

OpenAI's guide says credits arrive "while these benefits are available," and gives no end date or commitment. We could not find a statement on whether Plus will ever be included, or whether Codex via API keys could be added later. Treat the benefit as a perk that can change, not a contract term. If you plan a product around it, keep a paid fallback.

Our summary of the situation: the credits are real, documented in OpenAI's own docs, and useful for experimentation. They are not a reason to buy Pro by themselves unless you were going to spend that much on the API anyway. If you are on the fence, run a month of normal API usage first and compare it to the credit you would have received.

How to make the most of it this week

1. Confirm you own both the ChatGPT subscription and the API organization, with matching emails.
2. Claim from Settings, Billing in ChatGPT, or from API Platform Billing.
3. Check the credit balance in the API Platform billing page.
4. Point a side project or prototype agent at a project key from the linked organization.
5. Add handling for the HTTP 429 credit_balance_exhausted error so a spent balance fails gracefully.
6. Set a calendar reminder a week before the cycle ends to burn leftover credit on evals or batch jobs.

If you build agents that touch real systems, remember that cheap or free tokens also lower the cost of mistakes at scale. Keep permissions narrow and watch spend, and see the OpenAI-specific guidance in our 28-day Astra update log for how quickly the platform around these plans keeps changing.

Related reading

• SemiAnalysis: Claude plans give 5x more API value than ChatGPT
• Claude Max and Team API credits: how to claim
• ChatGPT Business Premium seats at $100
• GPT-6.1 Terra launch: pricing and benchmarks
• GPT-6.1 Sol and Astra cost efficiency
• Codex for open source grants: $100 versus $200 Pro
• Official: API credits for ChatGPT subscribers and the OpenAI API changelog

Plan terms, amounts, and eligibility are accurate as of October 29, 2026 and may change. Check OpenAI's guide before relying on them.