ChatGPT Pro and Business API Credits: How to Claim Them and What They Don't Cover
Eligible ChatGPT Pro and Business subscribers can claim API credits for one linked OpenAI API organization. Learn the grant amounts, activation paths, expiration rules, Codex exclusions, and how billing changes or HTTP 429 errors affect your API budget.
Contents
Claim ChatGPT Pro and Business API credits if you already have an eligible subscription and OpenAI API workloads. Pro grants provide $100, $200, or $500 per monthly billing period. Business grants pool paid-seat contributions, up to $500 per workspace per monthly billing period.
The grant funds one linked API organization. It does not increase ChatGPT or signed-in Codex allowances, and it excludes Codex usage through API keys.
The terms below reflect OpenAI’s official API credits benefit rules, read on 2026-11-01. The developer guide also confirms the amounts, claim paths, and Codex exclusion.
How much API credit does each ChatGPT plan provide?
Pro grants follow the plan tier. Business grants combine paid Standard and Premium seat contributions before applying one workspace cap. All amounts below are USD.
| Subscription or seat type | Full-period API grant |
|---|---|
| Pro $100 tier | $100 per monthly billing period |
| Pro $200 tier | $200 per monthly billing period |
| Pro $500 tier | $500 per monthly billing period |
| Business Standard | $20 per paid Standard seat |
| Business Premium | $100 per paid Premium seat |
| Business workspace | $500 maximum per monthly billing period across both seat types |
For a monthly Business workspace, use:
min(($20 × paid Standard seats) + ($100 × paid Premium seats), $500)
Five Standard seats and three Premium seats contribute $100 + $300 = $400. Ten Standard seats and four Premium seats contribute $600 before the cap, so the grant is $500.
Count paid Standard and Premium seats. Free trial subscriptions do not qualify. Do not infer whether a paid but unassigned seat counts from its assignment status alone.
What is the annual Business maximum?
Annually prepaid Business workspaces receive the full-year grant upfront, capped at $6,000 per annual billing cycle.
For unchanged paid seats over a complete year, a $400 monthly allowance corresponds to $400 × 12 = $4,800. A workspace at the $500 monthly cap reaches $500 × 12 = $6,000.
The first grant is prorated for the remaining paid term. This applies to both monthly and annual billing. Review the displayed claim amount rather than assuming you will receive a full-period grant.
Monthly credits expire at the subscription billing-cycle end, not necessarily the calendar month’s end. Annual credits expire at the annual billing-cycle end. Unused credits do not roll over.
Who can claim the credits?
The paid eligible subscription must have been active for at least seven days. Plan eligibility alone does not mean a grant has been issued.
The offer lists Pro 100, Pro 200, Pro 500, and eligible Business workspaces with paid Standard or Premium seats. Plus and free trials do not qualify. Enterprise, Edu, and legacy Codex seats are not listed as eligible.
Use the same email address for ChatGPT and the API account that links the organization. For Pro, the person activating must own the subscription and the receiving API organization. For Business, they must own both the workspace and the API organization.
You also need API billing-management permission. A Business admin role or custom API billing role does not replace the required ownership.
One eligible subscription or workspace can link to one API organization. That organization can have only one active link for this benefit.
New API users can link their Personal API Organization using the eligible subscription’s email. Completing API onboarding first is not required when claiming through ChatGPT.
How do you claim ChatGPT API credits?
Start from either ChatGPT billing or API Platform billing. Both paths activate the same benefit for your selected API organization.
Route 1: Claim from ChatGPT billing
- Sign in as the eligible Pro subscription owner. For Business, select the eligible workspace as an owner.
- For Pro, open Settings → Billing. For Business, open workspace billing in ChatGPT or the Admin Console.
- Find the API credits benefit and start the claim flow.
- Review the receiving API organization. Select the intended organization when several are available.
- Review the displayed grant amount, then confirm activation.
- Open API Platform billing settings for the linked organization and check the grant.
Route 2: Claim from API Platform billing
- Sign in with the email associated with the eligible ChatGPT subscription.
- Select the API organization you own and want to link.
- Open Billing and find the API credits benefit.
- Select the eligible subscription or Business workspace you own.
- Review the offer and confirm activation.
- Check the linked organization’s API billing settings for the grant.
An active promotional grant does not require an API payment method. Purchasing API credits or adding API billing details remains separate from paying for ChatGPT.
After activation, renewal grants are automatic while the subscription stays eligible and the benefit remains available. You do not need to claim every month. OpenAI may change or remove the benefit.
How can you confirm that the grant arrived?
Check the receiving organization’s credit-grant record, not just the linking confirmation.
Select the linked organization in API Platform. Open its billing overview, then Credit grants. Check the issued amount and expiration date.
OpenAI’s usage and cost reporting guide distinguishes credit records from API activity. Review both when reconciling consumption; an activity report alone does not prove that the grant arrived.
If linking succeeds but no grant appears, contact Support with the organization ID and attempted activation time. Include the subscription or workspace and any error message. Remove sensitive information from screenshots.
What do these credits cover, and what is excluded?
The grant pays for eligible API Platform usage billed to the linked organization. It does not create a general ChatGPT credit balance.
OpenAI lists Responses, Chat Completions, Agents, Decisions, GPT-Live, Realtime, Images, and built-in tools within the coverage. Applicable tool usage and storage charges still consume the API balance.
| Usage | Grant treatment |
|---|---|
| Eligible application API calls | Covered when billed to the linked organization |
| API Playground activity | Draws on that organization’s applicable API balance |
| ChatGPT conversations | No additional allowance |
| Signed-in Codex | No additional allowance |
| Codex through API keys | Excluded |
| Usage billed to an unlinked API organization | Not covered |
The receiving API organization determines the billing boundary. A ChatGPT workspace label does not independently determine which application requests the grant pays for.
Can you use the grant with Codex?
Neither Codex authentication route gains extra usage from this grant.
Signing in to Codex with ChatGPT continues to use the applicable subscription allowance. Configuring Codex with an API key does not help: the benefit explicitly excludes that usage.
Check authentication when comparing Codex CLI, the Codex app, and the VS Code extension. The interface name alone does not establish which billing system pays for a request.
Can Business teammates share the API credits?
Developers can use the receiving API organization’s balance only through separately authorized API access.
A Business seat does not grant API organization or project permissions. The workspace’s paid seats determine the pooled grant. The linked API organization separately controls access to its projects and API keys.
Why is the API credits benefit missing?
Check eligibility and ownership before assuming the feature is broken.
Confirm the paid plan and seven-day subscription age first. Then check the selected workspace, matching email, ownership on both sides, and API billing-management permission. Also check whether the subscription or receiving organization already has an active link.
For Business, ask a workspace owner to inspect billing. An admin or member cannot substitute for the owner during activation.
Availability also depends on the enabled cohort and country. The benefit page does not enumerate those cohorts or countries. Meeting the plan requirement alone therefore does not establish availability.
When the offer should be available, contact Support with the account, workspace, subscription age, and exact missing step. Do not send passwords or API keys.
Does country availability matter?
Yes. Promotion eligibility and API country support are separate checks.
Read the official API supported-country list before deploying. OpenAI warns that access outside supported countries or territories may result in account blocking or suspension.
A payment method, subscription, or visible claim page does not replace the API’s regional requirements. Do not treat another service as a way to make an unsupported OpenAI account eligible.
What happens when credits expire or run out?
Requests can continue after promotional credits run out if the organization still has purchased API credits. Promotional credits are consumed first.
When no credits remain, the documented response is HTTP 429 with credit_balance_exhausted. Add paid API credits or configure Auto Recharge to restore a usable balance.
Before enabling Auto Recharge, review its threshold, target balance, and monthly purchase limit. These are API billing settings, not an extension of your ChatGPT subscription.
How is credit_balance_exhausted different from a rate-limit 429?
Inspect error.code and the message before retrying. HTTP 429 can identify depleted credits, traffic limits, or spending controls.
The following distinctions are documented in OpenAI’s API error reference and usage-limit troubleshooting guide.
| Error or condition | Meaning | Next action |
|---|---|---|
credit_balance_exhausted | No prepaid credits remain | Add API credits |
| Request-rate limit | Requests arrive too quickly | Pace requests |
| Token-rate limit | Token throughput exceeds the allowed rate | Reduce token throughput |
slow_down | Request traffic increased too quickly | Reduce traffic, then increase it gradually |
organization_spend_limit_exceeded | An enforced organization spend cap was reached | Review and, if approved, raise or remove that cap |
project_spend_limit_exceeded | An enforced project spend cap was reached | Review and, if approved, raise or remove that cap |
organization_usage_limit_exceeded | The OpenAI-assigned organization usage limit was reached | Request a higher approved limit or contact Support |
A spending alert is not necessarily an enforced cap. OpenAI’s spend-limit documentation distinguishes notifications from hard limits that stop affected traffic.
For rate errors, follow a valid Retry-After header when provided. Otherwise, use exponential backoff with jitter under OpenAI’s retry guidance. Retrying cannot restore credits or change a spending limit.
The HTTP 429 retry and backoff guide explains the implementation pattern.
A positive grant does not remove request, token, model, organization, or project limits. Before buying more credits, check the request’s organization and project, grant expiry, remaining balances, and exact error.
What happens if you downgrade, cancel, or change organizations?
Use the specific lifecycle rule, rather than assuming every change revokes credits immediately. OpenAI documents these effects in the benefit page’s subscription-change provisions.
| Change | Documented effect |
|---|---|
| Schedule cancellation | Does not automatically refund the subscription |
| Subscription ends or becomes ineligible | Future grants stop |
| Cancellation alone | Issued credits remain usable until the current billing-cycle end |
| Downgrade to an ineligible plan, such as Plus, Go, or Free | Organization link ends at billing-cycle end |
| Upgrade Pro | Additional prorated credits may apply for the remaining cycle |
| Add paid Business seats or upgrade seat types | Additional prorated credits may apply, subject to the workspace cap |
| Reduce Business seats | Affects the next billing cycle |
| Reassign an existing Business seat | Does not create extra credits |
| Move Business to Enterprise | Organization link ends at billing-cycle end; Enterprise is ineligible |
Joining a Business workspace is different from changing a subscription. Joining alone does not replace a separately continuing Pro subscription.
Moving from Pro to Business ends the Pro link. A Business owner can create a new link after the workspace’s paid subscription has been active for seven days.
If the owner who linked a Business workspace leaves, the link is removed. Neither the subscription nor API organization can be relinked until the current billing cycle ends.
Contact Support to change the receiving API organization. A change request does not guarantee a transfer of credits or another grant.
What about refunds?
An approved full subscription refund removes unused promotional API credits associated with the refunded charge. The benefit terms explicitly establish this consequence.
This does not turn the free promotional balance into a cash refund. Check OpenAI’s refund instructions for the request route and eligibility.
The credit-removal statement concerns an approved full refund. Do not extend it to every partial refund or billing adjustment. Check the actual credit-grant record after a billing change.
A practical checklist before relying on the grant
Verify the grant, expiration, and billing path before routing production traffic.
Check that the correct organization received the expected amount. Confirm that developers have API permissions and that the application distinguishes billing failures from traffic limits. Decide whether purchased credits or Auto Recharge should fund traffic after the promotional balance expires.
For multi-model workloads, BetterToken is a separate API access layer. It is not a destination for redeeming this OpenAI grant. Compare current pricing for the same workload rather than assuming another route is cheaper.
Claiming an available benefit is useful when you already pay for an eligible plan and have covered API usage. Do not count excluded Codex activity, unlinked organizations, or credits that expire before use as savings.
