ChatGPT Pro API Credits: Claim, Upgrade, or Buy API Separately?

The help article’s included plans are Pro 100, Pro 200, Pro 500, and eligible Business workspaces with paid Standard or Premium seats. Plus does not qualify. Free trials do not qualify. The developer guide adds that complimentary subscriptions do not qualify. The help article says Enterprise, Edu, and legacy Codex seats are not established eligible plans or seats for this offer. The developer guide’s short eligibility list does not restate Edu or legacy Codex seats. Use the help article for those exclusions. Downgrade targets named later, Plus, Go, and Free, are ineligible plans.

The paid eligible subscription must have been active for at least 7 days before claiming. For Pro, the person who activates has to be the subscription owner and an owner of the receiving API organization. For Business, that person has to own both the ChatGPT workspace and the receiving API organization. Workspace membership is not enough. An admin role alone is not enough. Permission to manage billing in the API organization is required. A custom billing role does not replace API organization ownership.

One eligible ChatGPT subscription or workspace can link to one API organization. An API organization can have only one such active link. Use the same email on the ChatGPT account and on the API account used to link. If you are new to the API, you can link the subscription to your Personal API Organization with that email. You do not need to finish API onboarding before you claim inside ChatGPT. A ChatGPT seat does not give other workspace members API organization or project access. They need that access separately.

Availability also depends on the enabled cohort and country. The troubleshooting section says to check the plan, the paid age, the selected workspace, and the email, and then to contact Support if the offer should be there and is not. Do not treat a Pro receipt as proof that your account is in the cohort.

The developer guide’s table matches those Pro amounts and the per-seat Business amounts. The help article adds the workspace cap in the same table. For a monthly Business workspace, the full-period allowance is the smaller of ($20 × paid Standard seats + $100 × paid Premium seats) and $500. The help article’s own examples: 5 Standard seats and 3 Premium seats are $100 + $300 = $400. Ten Standard seats and 4 Premium seats are $600 before the cap, so the allowance is $500.

The first grant is prorated for the time remaining in the paid billing period. A full-period figure is not the number you will see if you claim partway through the period. Read the amount on the ChatGPT billing screen before you confirm. Business workspaces billed annually upfront receive the full year’s grant at once, capped at $6,000 per annual billing cycle. That first annual grant is prorated for the time left in the current cycle and expires when the cycle ends. The developer guide states the annual upfront issuance and the end-of-cycle expiry. The help article states the $6,000 cap and the proration. This article uses both.

Monthly grants expire at the end of the subscription billing cycle. Unused credits do not roll over. After you activate, later grants are issued when the eligible subscription renews. You do not claim again each month, as long as the benefit is still offered and the subscription is still eligible. These are promotional credits in an API organization. They are not ChatGPT Business plugin credits. The help article says plugin promotions add workspace credits under a separate offer.

Credits apply only to the linked API organization. Promotional credits are used before purchased API credits. You do not need an API payment method on file to spend an active grant. Adding a payment method, or buying API credits, is a separate act from paying the ChatGPT subscription. Your usage tier can still move up as you qualify. A credit balance does not remove request-rate, token-rate, model, organization, or project limits.

The help article says the free credits cover paid API Platform usage billed to the linked organization, including Responses and Chat Completions, Agents, Decisions, GPT-Live and Realtime, Images, and built-in tools with their usage and storage charges. The developer guide’s list is Responses for text, code, and image understanding; the Agents API, including OpenAI-hosted sandbox charges; the Decisions API; GPT-Live and the Realtime API; the Images API; built-in tools and their usage and storage, naming web search, file search, and Code Interpreter; and other APIs available through API Platform. Chat Completions appears by name on the help article. The developer guide folds remaining platform APIs into “other APIs.” Use a covered endpoint if you want the grant to be the thing that pays.

Codex usage through API keys is not supported by this benefit. The credits do not increase your ChatGPT usage allowance, your signed-in Codex usage allowance, your personal usage-credit balance, or a Business workspace credit balance. API usage and API limits do not transfer into ChatGPT Business. A reported API cost in a usage report is not the same number as cash charged after credits. Usage reports and credit-grant records answer different questions. Business teammates still need their own API organization and project access. Their ChatGPT seat does not grant it.

When the free balance runs out, purchased API credits are next. If purchased credits remain, requests continue. If no credits remain, requests fail with HTTP 429 and error code credit_balance_exhausted. To continue, add paid API credits in billing settings or set up Auto Recharge. Read the recharge threshold, the target balance, and the monthly purchase limit before you enable Auto Recharge. A 429 from a rate limit is a different failure. Check the error code before you buy another block of credits.

You can start in ChatGPT or in the API Platform. Both paths link the same benefit to the organization you select.

In ChatGPT: sign in as the owner of the eligible Pro subscription, or select the eligible Business workspace as an owner. For Pro, open Settings, then Billing. For Business, open the workspace billing settings in ChatGPT or the Admin Console. Find the API credits benefit and start the claim. Review the API organization that will receive the credits. If you own more than one eligible organization, select the one you mean to link. Confirm. Then open API Platform billing and look for the credits in that organization.

In the API Platform: sign in with the email on the eligible ChatGPT subscription. Select the API organization you own and want to link. Open Billing, find the API credits benefit, select the eligible subscription or Business workspace you own, review the offer, and confirm. Then look at billing settings for the credits.

Linking and issuance are separate. If the accounts are linked and the grant is missing, the help article says to select the linked organization, inspect its billing page, and contact Support with the subscription or workspace, the organization id, the activation time, and the error. Do not send passwords or API keys. Do not file repeated claims to get around an existing link. If the amount or the expiry looks wrong, compare the full-period allowance with the seat mix, the billing cadence, the time left in the period, and the amount the claim screen displayed. Record the grant amount and expiry you actually see.

If you need to change the linked organization later, contact Support. A change request does not guarantee a credit transfer or a second grant.

Scheduling a cancellation does not automatically refund the subscription. Future grants stop when the subscription ends or becomes ineligible. Cancellation alone does not revoke credits already issued. They remain usable until the end of the current billing cycle.

Downgrading to an ineligible plan, Plus, Go, or Free, removes the API organization link at the end of the billing cycle. Upgrading a Pro plan, adding paid Business seats, or upgrading Business seat types can add prorated credits for the rest of the cycle, subject to the cap. The developer guide says later Pro grants reflect the eligible plan’s allowance, up to $500 per billing cycle. Adding paid Business seats creates a new invoice and an associated grant. Seat reductions affect the next billing cycle. Reassigning an existing seat to another person does not create extra credits.

Joining a Business workspace, merging personal content, and changing a subscription are different actions. If your personal Pro subscription continues separately, joining a workspace does not replace it. Moving from Pro to Business ends the Pro link. After the Business workspace’s paid subscription has been active for seven days, an owner can create a new Business link. Moving a Business subscription to Enterprise removes the API organization link at the end of the billing cycle. Enterprise is not eligible. If the owner who linked a Business workspace leaves that workspace, the link is removed. Neither side can be relinked until the current billing cycle ends.

An approved full refund removes the unused promotional API credits tied to the refunded charge. A subscription refund is not a cash refund of that free balance. Other refunds follow the refund policy. The help article names deletion, bans, and unbans as separate consequences and does not price them.

The decision is which cash you are already committed to spend.

If you already pay for an eligible Pro or Business plan for the chat and Codex limits in the linked guides, claim the grant. The subscription price does not change. The grant offsets covered API usage up to the allowance, and the rest expires. Skipping a claim that is on the billing page leaves that offset unissued. The claim does not cover Codex through an API key, and it does not enlarge the December shared allowance.

If you do not want the ChatGPT plan, and you are buying it only to receive the API grant, compare the subscription cash plus any API usage above the grant with the cost of buying the API usage directly. These pages do not publish a fee or a discount on purchased API credits. The illustrative math below treats a purchased API dollar as a dollar of prepaid API credit. If your invoice shows a different purchase price, use that price.

Every total below is illustrative. It is not a customer bill. Public assumption: a full monthly period, so the first-grant proration is zero; covered API usage only; no Codex-via-API-key spend; no taxes; the grant equals the full-period allowance because the claim is for a full period. Formula for extra API cash after a grant: max(0, covered API usage − grant). Formula for total cash if you buy the plan only for the credits: subscription price + extra API cash. Formula for buying the API directly: covered API usage, under the one-dollar-per-credit assumption.

Case 1. You already pay Pro $200, and covered API usage in the period is $150. Extra API cash = max(0, 150 − 200) = $0. Unused grant = 200 − 150 = $50, and it expires. The $200 subscription is still due because you were paying it for the plan. The claim avoids a $150 API purchase. It does not return the unused $50.

Case 2. You would buy Pro $100 only for the credits, and covered usage is $150. Extra API cash = max(0, 150 − 100) = $50. Total cash = $150, and you hold Pro. Buying the API directly is also $150, without Pro. Buy the plan if you want the plan.

Case 3. You would buy Pro $500 only to obtain credits, and covered usage is $150. Total cash on the upgrade path is $500, because the grant covers the $150 and $350 expires. Buying the API directly is $150. The upgrade path spends $350 more on this assumption. Do not buy Pro $500 for a $150 API bill.

Case 4. You already pay Pro $500 for the usage limits in the other guides, and covered API usage is $150. Extra API cash is $0. Unused grant is $350 and expires. Claim it. The expiry is not a reason to skip the $150 offset, and it is not a reason to move usage onto Codex through an API key, which the grant does not cover.

Case 5. A monthly Business workspace has 5 paid Standard seats and 3 paid Premium seats. Allowance = min(20 × 5 + 100 × 3, 500) = min(400, 500) = $400. These two pages do not print the monthly price of a Standard or Premium seat, so this article does not invent a workspace invoice. If covered API usage is $250, extra API cash = max(0, 250 − 400) = $0, and $150 of the grant expires. If covered usage is $700, extra API cash = max(0, 700 − 400) = $300, which you buy as API credits. Ten Standard seats and 4 Premium seats still cap at $500, not at $600.

Case 6. You claim halfway through a monthly period. The screens show a prorated grant, not the full-period column. Replace the grant in the formula with the number on the screen. A $200 tier that shows $100 because half the period is left offsets $100 of covered usage, not $200.

Case 7. The offer is missing. Cohort, country, plan age, owner, or email can all do that. Buy the API credits you need, or contact Support with the facts the troubleshooting section asks for. Do not create a second organization and claim again to force a second grant. One subscription links once.

1. Confirm the plan is Pro 100, Pro 200, Pro 500, or a Business workspace with paid Standard or Premium seats. Stop if it is Plus, a free trial, a complimentary seat, Enterprise, Edu, or a legacy Codex seat.
2. Confirm the paid subscription has been active for 7 days.
3. Confirm you are the owner on both sides, and that the emails match.
4. Choose the one API organization you want linked. You do not get a second link for free.
5. Read the grant amount on the screen. If you are mid-cycle, expect a proration.
6. Confirm, then open the linked organization’s credit grants and write down the amount and the expiry.
7. Call a covered API with a key from that organization. Codex through an API key is the wrong test.
8. When the balance hits zero, expect credit_balance_exhausted if no purchased credits remain. Buy credits or set Auto Recharge only after you read the threshold and the monthly cap.
9. On renewal, check that a new grant arrived. You should not have to claim again. If the benefit has been withdrawn, the renewal will not invent one.
10. Revisit the three linked guides only if the question has moved back to chat limits, Pro 200 versus Pro 500, or the December shared allowance. Those meters are not this grant.

Does every ChatGPT Pro account get API credits?

No. The subscription has to be an eligible paid Pro or Business plan, active for at least 7 days, and you have to claim it as an owner on both sides with the same email. Plus, free trials, and complimentary subscriptions do not qualify. The help article also excludes Enterprise, Edu, and legacy Codex seats. Cohort and country can hide the offer. A paid plan does not prove a grant was issued.

Do the credits roll over?

No. Monthly grants expire at the end of the subscription billing cycle. Unused credits do not roll over. An annual upfront Business grant expires at the end of that annual cycle. The help article caps that annual grant at $6,000.

Does the grant cover Codex?

Codex usage through API keys is not covered. The credits also do not increase ChatGPT or signed-in Codex usage limits. The December shared allowance and the Pro tier limits are separate decisions, covered in the linked guides.

What happens when the balance is gone?

Purchased credits are used after the promotional grant. If none remain, the API returns HTTP 429 with error code credit_balance_exhausted. Add paid credits or configure Auto Recharge. A credit balance does not lift rate limits, so a different 429 can still be a rate limit.

Is a mid-cycle claim the full $100, $200, or $500?

Not necessarily. The first grant is prorated for the time left in the paid period. Read the amount on the claim screen. Business monthly pools are also capped at $500, so a seat formula above $500 still grants $500 for a full period.