ChatGPT Pro and Business API credits: link the right org

Eligible ChatGPT Pro and Business subscribers can now claim free OpenAI API credits every month, up to $500. OpenAI announced the benefit in its API changelog on October 28, 2026, and its developer guide sets the amounts: Pro gets $100, $200 or $500 a month to match its tier, and Business gets $20 per paid Standard seat plus $100 per paid Premium seat, pooled and capped at $500 per workspace. The credits go to a single API organization that the subscription owner links once. That link is the decision to get right, because changing it means contacting OpenAI Support, with no guarantee that credits move with it.

How much API credit does each ChatGPT plan get?

Scroll sideways to see all 3 columns.

ChatGPT plan	Monthly API credits	How it is counted
Pro ($100 tier)	$100	Per subscription
Pro ($200 tier)	$200	Per subscription
Pro ($500 tier)	$500	Per subscription
Business, Standard seat	$20 per paid seat	Pooled for the workspace
Business, Premium seat	$100 per paid seat	Pooled for the workspace
Business workspace cap	$500 per month	$6,000 per annual billing cycle

A Business workspace gets the smaller of its per-seat total and $500. OpenAI's Help Center article gives two examples: 5 Standard and 3 Premium seats contribute $400, while 10 Standard and 4 Premium seats add up to $600 and are capped at $500. BaristaLabs arithmetic from those rates: an all-Standard workspace reaches the cap at 25 paid seats, and an all-Premium workspace reaches it at 5. A mixed workspace reaches it once its per-seat total hits $500, and seats past that point add no credits.

A few rules change how much is available in a given cycle:

• The first grant is prorated for the time left in the current billing cycle.
• Unused credits expire at the end of the billing cycle and do not roll over.
• Annual Business plans paid upfront receive the full year's grant at once, capped at $6,000, and it expires at the end of the annual cycle.
• Pro upgrades can add credits. Upgrading a Pro plan can provide extra prorated credits for the rest of the billing cycle.
• Seat changes count, reassignments do not. Adding paid seats or upgrading seat types mid-cycle can add prorated credits up to the cap. Reassigning an existing seat to another person creates no extra credits, and seat reductions take effect in the next cycle.

Who can claim ChatGPT API credits?

The paid Pro or Business subscription must have been active for at least seven days. Free trials, complimentary subscriptions and Plus do not qualify, and ChatGPT Enterprise is not eligible. The Help Center also does not list Edu or legacy Codex seats as eligible.

The person claiming must own both sides of the link: the ChatGPT subscription or Business workspace, and the API organization that receives the credits, using the same email address on both. For Business, OpenAI says workspace membership or an admin role alone is not enough. The Help Center also calls for permission to manage billing in the API organization. OpenAI also notes that availability depends on the enabled cohort and country, so an eligible plan may not show the offer.

There are two ways to claim. In ChatGPT, Pro owners use Settings → Billing, and Business owners use the workspace billing settings or the Admin Console. In the API Platform, an owner opens Billing in the organization to be linked and selects the subscription. No API payment method is required. After activation, a new grant arrives automatically at each renewal while the benefit remains available.

Which API organization should receive the credits?

The link is one-to-one in both directions. According to the Help Center, one eligible subscription or workspace can link to one API organization, and an API organization can have only one such active link. Changing the receiving organization requires a support request, and OpenAI says a change request "does not guarantee a credit transfer or an additional grant."

Three more rules shape the choice:

• Credits stay in the linked organization. Requests must use a project API key from that organization to draw on the grant.
• Seats do not grant API access. A ChatGPT Business seat does not give teammates access to the API organization or its projects, so they need to be added there separately.
• The link depends on the owner. If the owner who linked a Business workspace leaves that workspace, the link is removed, and neither the subscription nor the API organization can be relinked until the current billing cycle ends.

BaristaLabs recommendation: link the organization where the team already builds and tests, so the monthly grant gets used before it expires, and have the claim made by an owner who is expected to stay. If API spend is already tracked per project or key (see how OpenAI API-key cost reporting depends on workload ownership), link the organization whose reports the finance owner already reads.

What do the credits cover?

The grant pays for API Platform usage billed to the linked organization. The developer guide lists the Responses API, the Agents API (including OpenAI-hosted sandbox charges), the Decisions API, GPT-Live and the Realtime API, the Images API, and built-in tools such as web search, file search and Code Interpreter, with their usage and storage charges.

Four limits are easy to miss:

• Codex usage through API keys is not covered.
• ChatGPT and signed-in Codex limits do not increase. The credits sit in the API organization only.
• Rate limits still apply. OpenAI says a credit balance "does not remove request-rate, token-rate, model, organization or project limits."
• These are not ChatGPT Business plugin credits. Plugin credit promotions add workspace credits under a separate offer.

Reported cost and cash charged can also differ. OpenAI notes that a reported API cost "is not necessarily the cash charged after credits are applied," so a dashboard that treats reported cost as cash spend can overstate the bill while the grant lasts.

What happens when the credits run out?

The organization uses the free credits first, then any purchased credits. If no credits remain, requests fail with HTTP 429 and the error code credit_balance_exhausted. OpenAI's error code guide uses the same 429 status for rate limits and for spend limits, so the error code, not the status, tells the cause. A client that retries every 429 as a rate limit will keep retrying against an empty balance. The difference between these controls is covered in quota vs. rate limit vs. spend cap.

To keep going, an owner can buy credits or turn on Auto Recharge. The Help Center advises reviewing the recharge threshold, target balance and monthly purchase limit before enabling it. An organization with no purchased credits and no Auto Recharge stops when the grant runs out. BaristaLabs interpretation: that suits a prototype that should stay within the grant, but it can stop anything users rely on (see how OpenAI hard spend limits can stop production traffic).

Which plan changes remove the link?

• Downgrading to Plus, Go or Free removes the link at the end of the billing cycle.
• Moving from Pro to Business ends the Pro link. After the Business subscription has been paid and active for seven days, an owner can create a new Business link.
• Moving from Business to Enterprise removes the link at the end of the billing cycle.
• Canceling stops future grants but does not revoke credits already issued. They stay usable until the cycle ends. An approved full refund removes the unused credits tied to the refunded charge.

OpenAI also says the benefit may change or be removed in the future.

Why it matters for teams that pay for ChatGPT Business

BaristaLabs interpretation: an eligible Business workspace at the cap, such as one with 25 Standard seats or 5 Premium seats, can now claim $500 a month of API usage that would otherwise need its own budget. The pooled cap also limits what seat upgrades add. Each Premium seat counts $100 toward the pool, but once a workspace reaches $500, more Premium seats add nothing to the API grant. Premium upgrades still need to be justified by ChatGPT usage, as covered in assigning ChatGPT Business Premium seats from usage evidence.

Recommended first step: choose the org and owner, then claim

BaristaLabs recommendation: before anyone clicks claim, write down three things: the API organization that should receive the credits, the owner who will claim them (same email on both sides, expected to stay), and whether that organization should stop at zero or continue on purchased credits or Auto Recharge with a monthly purchase limit. Then claim, open Credit grants in the linked organization's billing settings, and record the grant amount and expiry date shown there. Add the teammates who will spend the credits to that organization's projects, since their ChatGPT seats do not include API access.

Sources and scope

• OpenAI API changelog, entry for October 28, 2026.
• OpenAI developer docs, API credits for ChatGPT subscribers, accessed October 31, 2026.
• OpenAI Help Center, API credits benefit for eligible ChatGPT subscriptions, accessed October 31, 2026.
• OpenAI developer docs, Error codes, accessed October 31, 2026.

The 25-seat (all Standard) and 5-seat (all Premium) cap thresholds are BaristaLabs arithmetic from OpenAI's published per-seat amounts. The amount shown at claim time can differ because of proration, billing cadence and seat changes, and OpenAI says availability varies by cohort and country. For help choosing the receiving organization and its spend controls, see AI consulting.