ChatGPT Pro and Business: up to $500 a month in API credits
Overnight on 28–29 October (Amsterdam time), OpenAI announced that eligible paid ChatGPT subscriptions can claim API credits. This is a subscription benefit that lets you build apps and agents with the OpenAI API. The maximum is up to $500 per month, depending on the Pro tier or the number and type of paid Business seats. So it is not a fixed amount that every Pro or Business subscriber receives: $500 is the ceiling, not the standard.
The announcement came in a post from @OpenAIDevs on X, to the effect that eligible ChatGPT Pro and Business subscribers can from that moment claim up to $500 per month in API credits. For the details, the OpenAI Help Center and OpenAI's developer docs are the primary sources. In this article we set out which amount belongs to which subscription, who is eligible, how you claim, what the credit does and does not cover, and what happens when your subscription changes.
Because this is about API usage, it helps to first be clear on how API costs are actually built up; that is explained in our overview of how pricing per token works. That way you can better estimate what a credit of, say, $100 means in practice for your project.
What OpenAI is announcing
According to OpenAI, eligible paid ChatGPT Pro and ChatGPT Business subscribers can claim free API credits as part of their subscription, with the aim of building apps and agents with the OpenAI API. That is stated in the Help Center article about the API credits benefit and in the developer docs. The headline OpenAI itself uses is "up to $500 per month".
The announcement was made via @OpenAIDevs on X, posted on 28 October 2026 at 23:17 UTC, which is 29 October 00:17 Amsterdam time. That post is an announcement, not a full specification; the exact amounts, conditions and exclusions come from the OpenAI Help Center and the developer docs.
The benefit is explicitly a subscription benefit: it is tied to your ChatGPT subscription and to a linked API organization. According to OpenAI, availability also depends on the enabled cohort and on the country. That means it is not automatically available to everyone with a suitable subscription at the moment you read this.
If you want to know what a credit translates into in tokens for your usage, you can work that out with our token cost calculator. That is especially useful because the credit is expressed in dollars while your consumption happens in tokens and requests.
How much credit per subscription
The amounts apply per full monthly billing period. With Pro, the amount depends on the tier you are in. With Business, the amount is built up from paid seats and then pooled for the workspace, with a workspace cap.
| Subscription | API credit per month |
|---|---|
| Pro ($100 tier) | $100 |
| Pro ($200 tier) | $200 |
| Pro ($500 tier) | $500 |
| Business Standard | $20 per paid Standard seat (pooled) |
| Business Premium | $100 per paid Premium seat (pooled) |
| Business workspace cap | max. $500 per month |
Note the wording: it is up to $500 per month, depending on the Pro tier or the number and type of paid Business seats. A Pro subscriber in the $200 tier gets $200, not $500. A Business workspace with only Standard seats builds up its credit slowly, because each Standard seat contributes $20. The $500 is the maximum a Business workspace can receive per monthly billing period, regardless of how many seats there are.
Because the credit is in dollars while your consumption is in requests and tokens, it also helps to look at rate limits and the cost of LLM APIs. That makes clear that a credit covers your costs, but does not automatically widen your limits.
Worked examples for Business workspaces
For Business, OpenAI uses a fixed formula. The full-period allowance is the smaller of two amounts: on the one hand the sum of $20 times the number of paid Standard seats plus $100 times the number of paid Premium seats, and on the other hand $500. The outcome is pooled: the whole workspace shares the credit, not the individual seat.
OpenAI's first worked example: a workspace with 5 Standard seats and 3 Premium seats. That is 5 × $20 = $100 plus 3 × $100 = $300, together $400. That is below the cap, so the period allowance is $400.
The second worked example: a workspace with 10 Standard seats and 4 Premium seats. That is 10 × $20 = $200 plus 4 × $100 = $400, together $600 before the cap. Because $600 is above the maximum, the allowance is $500. In that case, the extra seats above the cap yield no additional credit.
For planning, this means the number and type of seats are your control levers, but only up to the $500 per month cap. How you then draw the line in practice is closely tied to how you set up budgets and quotas technically; that is what our piece on hard cost limits, budget caps and a kill switch covers.
Who is eligible
According to OpenAI, the eligible plans are: Pro 100, Pro 200, Pro 500, and Business workspaces with paid Standard or Premium seats. Those are the subscriptions the benefit is intended for.
Not eligible are: Plus, free trials, Enterprise, Edu and legacy Codex seats. Those are explicitly outside the benefit. Complimentary subscriptions also do not qualify. In short: do not count on this credit if you are on Plus, a trial, Enterprise, Edu or a legacy Codex seat.
In addition, availability depends on the cohort OpenAI has enabled and on the country. So a suitable subscription is necessary, but not necessarily sufficient.
There is one more practical point for teams: Business teammates need separate access to the API organization and the projects within it. A ChatGPT seat does not grant that access. So a seat in ChatGPT Business does not automatically mean you can work in the linked API organization. How to set that up securely afterwards is covered in our article on managing API keys safely.
Requirements for claiming
OpenAI lists a number of requirements. The paid, eligible subscription must have been active for at least 7 days before you claim. The person activating must be the owner of the ChatGPT subscription (for Pro) or the owner of the Business workspace and the owner of the API organization that receives the credit. Workspace membership or an admin role alone is not enough.
Furthermore, the email address of your ChatGPT account and your API account must be the same, and you must have permission to manage billing in the API organization. One eligible subscription or workspace links to one API organization, and an API organization can have only one such active link.
New API users can link their Personal API Organization; you do not have to complete API onboarding before claiming in ChatGPT. That lowers the threshold if you mainly work in ChatGPT and have not used the API before.
How to claim the credit
There are two claim paths. In ChatGPT you can do it via Settings → Billing (for Pro) or via the workspace billing settings / the Admin Console (for Business). On the API Platform you can do it via Billing, where you select the eligible subscription or the Business workspace.
After claiming, the credits are visible in the API Platform billing settings, under Credit grants. From that point they are granted automatically on each renewal as long as the benefit is available and your subscription is eligible; re-claiming is not necessary.
Because this involves a link between your ChatGPT account and an API organization, it is sensible to decide in advance which API organization you link and who is its owner. Especially in teams, that prevents later discussion about who manages the credits.
What you can use the credits for
The credits apply only to the linked API organization and cover paid API Platform usage. According to OpenAI, that includes Responses and Chat Completions, the Agents API (including charges for the OpenAI-hosted sandbox), the Decisions API, GPT-Live and Realtime, Images, and built-in tools such as web search, file search and Code Interpreter, along with their usage and storage charges.
In practice, this means you can use the credit to build and run apps and agents within that one linked organization. It covers the API surfaces and tools listed above, and no more than that.
What a credit yields in tokens differs per model and per type of usage. If you are comparing several tools or categories, our overview of cost models of AI tools compared by category can help put that in perspective.
What is not covered
The credits do not cover Codex usage through API keys. They also do not increase your ChatGPT or signed-in Codex usage limits, and they change nothing about your personal usage-credit balance or your Business workspace credit balance. Those are separate matters.
If you use Codex, keep in mind that for this credit, Codex usage through API keys falls outside the benefit. If you run Codex through API keys, you should therefore not try to finance that from these credits.
Also do not confuse this benefit with the promotions around ChatGPT Business plugin credits. That is a separate offer with workspace credits, not the API credits at the centre of this article. And finally: ChatGPT billing and API billing remain separate.
Expiry, proration and annual subscriptions
After activation, credits are granted automatically on each renewal, as long as the benefit is available and the subscription is eligible. The monthly grants expire at the end of the billing cycle; unused credits do not roll over to the next period. The first grant is prorated for the time remaining in the billing period.
OpenAI also states that the benefit may change or be removed in the future. So do not count on it as something permanent; treat it as a periodic benefit.
For Business workspaces billed annually upfront, a separate rule applies: they receive the full year's grant at once, capped at $6,000 per annual billing cycle, expiring at the end of that annual cycle. Here too, the first grant is prorated.
When the credit runs out
No API payment method is needed to use an active grant. Free credits are consumed before purchased credits. If purchased credits remain, usage continues on them. If no credits remain, requests fail with HTTP 429 and the error code credit_balance_exhausted. You can then continue by adding paid credits or enabling Auto Recharge.
Important for your expectations: a credit balance does not remove any rate, token, model, organization or project limits. So your credit does not change your limits; it only determines what your usage is paid from as long as credits remain. Keep that distinction sharp when you do capacity planning.
Changes to your subscription
Upgrading your Pro subscription, or adding or upgrading paid Business seats, can yield extra prorated credits for the rest of the cycle, within the cap. Reducing seats only takes effect in the next cycle, and reassigning a seat yields no extra credits.
On cancellation, credits already issued are not revoked; they remain usable until they expire. Future grants do stop, however. If you downgrade to Plus, Go or Free, the link to the API organization is removed at the end of the cycle.
If you move from Pro to Business, the Pro link ends; a new Business link is possible once the subscription has been paid for 7 days. If you move from Business to Enterprise, the link is removed at the end of the cycle. With an approved full refund, unused promotional API credits tied to the refunded charge are removed.
What this means for developers and teams
For individual developers on an eligible Pro tier, this is mainly a way to cover API usage without immediately attaching a payment method, as long as there is an active grant. The amount depends on the tier: $100, $200 or $500 per month. You do have to take into account that unused credits expire at the end of the cycle and do not roll over, so it pays to spread or plan your usage somewhat.
For teams, the most important thing is that the credit is pooled at workspace level and that the cap for Business is $500 per month. So more seats do not mean unlimited extra credit. With 5 Standard and 3 Premium seats you reach $400; with 10 Standard and 4 Premium seats you are at $600 before the cap and therefore at $500. The type of seat weighs more heavily than the number: a Premium seat contributes $100, a Standard seat $20.
Beyond that, the link is strict: one eligible subscription or workspace links to one API organization, and an API organization can have only one such active link. For teams that means a deliberate choice in advance: which organization becomes the organization that receives this benefit? And who is the owner there, given that workspace membership or an admin role alone is not sufficient?
In addition, the distinction between ChatGPT and API billing remains. This credit covers API usage in the linked organization, but not your ChatGPT or signed-in Codex limits, and not Codex through API keys. Teams that work both in ChatGPT and through the API therefore have to keep tracking two things separately: their ChatGPT usage and their API consumption.
Finally: because availability depends on cohort and country, it is sensible to first check in ChatGPT or the API Platform whether you can actually claim the benefit before you build it into your planning. If you do not see it, your subscription may (not yet) be in the enabled cohort, or may not be in a supported country.
Checklist
- Check whether you are on an eligible plan: Pro 100, Pro 200, Pro 500 or a Business workspace with paid Standard or Premium seats.
- Remember that Plus, free trials, Enterprise, Edu and legacy Codex seats are not eligible, and that complimentary subscriptions do not qualify.
- Make sure your paid subscription has been active for at least 7 days before you claim.
- Claim as owner: owner of the ChatGPT subscription (Pro) or owner of the Business workspace and owner of the receiving API organization.
- Use the same email address for your ChatGPT account and your API account.
- Make sure you are allowed to manage billing in the API organization.
- Be aware that one eligible subscription or workspace links to one API organization, and that an API organization can have only one such active link.
- Claim via Settings → Billing (Pro) or the workspace billing / Admin Console (Business), or via Billing on the API Platform.
- Then check your Credit grants in the API Platform billing settings.
- For Business, calculate with the formula: the smaller of ($20 × paid Standard seats + $100 × paid Premium seats) and $500.
- Bear in mind that monthly grants expire at the end of the billing cycle and do not roll over.
- With annual Business billing, expect the full year's grant at once, capped at $6,000 per annual cycle.
- Know that an empty credit balance can give you HTTP 429 with
credit_balance_exhausted, and that you then need paid credits or Auto Recharge. - Do not confuse this credit with ChatGPT Business plugin credits; that is a separate offer.
- Do not expect this benefit to widen your rate, token, model, organization or project limits.
- Plan a check on cohort and country availability before you include this in your cost model.
In summary: eligible ChatGPT Pro and Business subscribers can claim up to $500 per month in API credits, depending on the Pro tier or the number and type of paid Business seats, with a Business workspace cap of $500 per month and an annual Business cap of $6,000. The credit is linked to one API organization and covers paid API Platform usage within that organization; unused credits expire at the end of the cycle. The credit is entirely separate from your ChatGPT and signed-in Codex limits and from Codex through API keys.
Checked on 2026-10-29.
This article was compiled with AI assistance and editorially reviewed; sources are listed below.
Sources
- OpenAI Help Center: "API credits benefit for eligible ChatGPT subscriptions" — https://help.openai.com/en/articles/20001626-api-credits-benefit-for-eligible-chatgpt-subscriptions
- OpenAI developer docs: "API credits for ChatGPT subscribers" — https://developers.openai.com/api/docs/guides/chatgpt-api-credits
- X post by @OpenAIDevs (announcement), 28 October 2026 23:17 UTC (29 October 00:17 Amsterdam time) — https://x.com/OpenAIDevs/status/2115583698074755078


