OpenAI adds API credits to ChatGPT Pro and Business

Eligible ChatGPT Pro and Business subscribers can claim promotional OpenAI API credits, potentially offsetting spending on applications and agents. The practical benefit depends on the plan, paid seat mix, remaining billing period and successful activation in the API organisation that will consume the grant.

OpenAI's developer guidance lists monthly allowances of $100, $200 or $500 for the corresponding Pro tiers. Business grants contribute $20 per paid Standard seat and $100 per paid Premium seat, pooled subject to a $500 monthly workspace cap. The initial grant is prorated, so the full-period allowance is not necessarily what an owner receives when activating partway through a cycle.

“ChatGPT and API billing remain separate,” OpenAI says in its help-centre guidance. That is an institutional statement, not an individually attributed interview. It is also the central qualification for finance teams: paying for a ChatGPT workspace does not merge its billing controls, access permissions or usage allowances with those of an API organisation.

The activation requirements reinforce that separation. The eligible paid subscription must be at least seven days old. The claimant needs ownership on both sides and the same account email for linking. For Business, workspace membership or an administrator role alone does not establish the required ownership. The offer's visibility can also depend on the enabled cohort and country, so eligibility should be checked in the actual billing flow.

A useful budgeting example is a monthly workspace with four paid Standard seats and one paid Premium seat. At the published contributions, the full-cycle grant would be $180: four times $20, plus $100. That is below the workspace cap. This arithmetic describes the allowance under the stated assumptions, not a guaranteed immediate grant, a cash refund or a reason to buy seats a business does not otherwise need.

The value to a particular team depends on how much eligible API consumption it would incur before expiry. An allowance exceeding that consumption cannot be treated as equivalent cash savings. A purchasing comparison should therefore place the expected usable grant alongside the subscription cost and planned workload, rather than subtract the headline maximum from every team's budget.

The billing cadence changes the expiry calculation. Monthly credits expire at the end of the monthly subscription cycle. Annually prepaid Business workspaces receive the year's grant together, subject to the $6,000 annual cap and the remaining paid term for an initial grant. Neither arrangement provides indefinite rollover. Teams need the actual grant record and expiry date when planning work.

Activation also does not give every Business teammate access to the linked API organisation or its projects. Nor does a credit balance remove model or request-rate limits. The documented exclusions include Codex use through API keys; the API grant does not expand ChatGPT or signed-in Codex allowances. These distinctions matter when a department budgets several AI products under one subscription heading.

For workspace owners, the immediate action is to verify the receiving organisation, displayed grant and expiry before committing the benefit to a project forecast. For finance and platform teams, the useful record is the amount actually issued and consumed against the intended workload. The headline credit cap is a ceiling on the offer, not a measure of savings already realised.

Sources

• OpenAI — API credits developer guide — Primary source
• OpenAI — eligibility, billing and grant guidance — Primary source