OpenAI has added a new benefit to its developer documentation: eligible ChatGPT Pro and Business subscribers can claim a monthly API credit and have it deposited into an API organization they own. The credit is issued automatically with each subscription renewal, with no separate application.
Pro users receive credits one for one with their plan tier: $100 a month on the $100 Pro plan, $200 on the $200 plan, and $500 on the $500 plan. Business workspaces are calculated by paid seat, at $20 per Standard seat and $100 per Premium seat, with a combined cap of $500 a month for the whole workspace. ChatGPT Enterprise is not included.
Eligibility requirements
The conditions in the documentation are fairly detailed. The subscription must be paid and have been active for at least 7 days; free trials and gifted subscriptions do not count. The person claiming the credit must be the owner of both the ChatGPT subscription (or Business workspace) and the API organization that will receive the credit, and both accounts must use the same email address.
There are two ways to activate, with the same result. In ChatGPT, open Settings, go to Billing and select the API organization to link; or start from the other side, choosing the organization on the Billing page of the API Platform and then linking the subscription. Business admins do this in the workspace billing settings or the Admin Console.
The first credit is prorated by the days remaining in the current billing cycle. Unused credit expires at the end of the cycle and does not roll over. Canceling a subscription does not claw back credit that has already been issued, so it can be used until it expires; it simply stops being issued afterward. If a subscriber downgrades to Plus, Go or the free tier, the link is removed at the end of the cycle. Switching from Pro to Business ends the Pro link immediately, and the account can be linked again only after the Business plan has been paid for 7 days.
Annual Business workspaces receive a full year of credit up front, which expires when the annual billing cycle ends. If seats are added or seat types upgraded mid-cycle, additional credit is issued for the remaining time, still subject to the $500 monthly and $6,000 annual caps.
Where the credit works, and where it doesn't
The credit can be applied to calls to APIs such as Responses, Agents, Realtime and Images. Usage and storage fees from built-in tools such as web search, file search and Code Interpreter also count. The documentation gives no list of eligible models; it says only that usage remains subject to the organization's usual rate limits and model restrictions.
Three limits matter most. The credit is valid only in the linked API organization, and requests must use a project API key from that organization. Calling Codex with an API key is not supported. And the credit does not raise the usage limits of ChatGPT or of Codex when signed in with a ChatGPT account. When the credit runs out and the organization has no self-purchased balance, requests return HTTP 429 with the error code credit_balance_exhausted. If credit has also been bought separately, the free credit is drawn down first, then the purchased balance.
The documentation does not say when the benefit starts or how long it will last, and it mentions no regional restrictions.
A rough calculation
For Pro users, this effectively sends the other half of the monthly fee back to a developer account. On the $200 plan, the subscription used to buy only high usage limits in ChatGPT and Codex; now it also adds $200 of API balance every month, provided you actually have programs calling the API.
For Business, the math depends on headcount. At $20 per Standard seat, 25 paid seats already reach the $500 workspace cap, and adding people beyond that does not increase the credit; with all Premium seats, 5 seats hit the cap. For teams of a few dozen or more, the money looks more like an experiment budget for the engineers handling the integration than something that can carry production traffic.
The no-rollover rule also shapes how it should be used. Because the credit resets every month, it suits prototypes, evaluations and powering small internal tools, not stockpiling for a spike in usage at month's end.
Subscriptions and the API start to connect
Until now, ChatGPT subscriptions and API billing were two separate ledgers, and a subscriber who wanted to write code had to open an API account and top it up. The new design ties the two accounts together by the same email and the same owner, turning part of the subscription fee into balance that can be spent on the API Platform. From the way the documentation is written, OpenAI deliberately keeps this money apart from Codex: Codex usage inside the subscription runs on its own quota, while the API credit covers only the calls developers write themselves.
For developers in China, the benefit itself does not change where the API is available, which still follows the countries and regions OpenAI supports; the documentation contains no terms aimed at any specific market.
Sources: OpenAI developer documentation (ChatGPT API credits page), CocoLoop; verified the three Pro credit tiers, Business per-seat prices, and the $500 monthly and $6,000 annual workspace caps.