OpenAI offers up to $500 in monthly API credits to ChatGPT Pro and Business subscribers
Since October 29, paying ChatGPT Pro and Business subscribers can link their subscription to an API organization and receive free credits each month: from $100 to $500 depending on the Pro tier, $20 or $100 per Business seat, capped at $500 per workspace.

OpenAI announced overnight, on October 29 at 12:17 a.m. Paris time, that eligible ChatGPT Pro and ChatGPT Business subscribers can now claim up to $500 per month in API credits, to “build applications and agents.” Until now, the ChatGPT subscription and OpenAI’s API platform were two separately billed products: paying for ChatGPT gave you nothing on the developer side. Billing remains separate, but the subscription now entitles you to a monthly API budget.
How much, and for whom
OpenAI’s published documentation details the monthly amounts:
- Pro 100: $100; Pro 200: $200; Pro 500: $500;
- Business: $20 per paid Standard seat and $100 per paid Premium seat, pooled for the workspace and capped at $500 per month. OpenAI gives the example of 10 Standard seats and 4 Premium: $600 before the cap, so $500 paid out. A workspace billed annually receives the full amount at once, up to $6,000 per cycle.
Free trials, the Plus tier, as well as Enterprise, Edu, and legacy Codex seats are not eligible. The paid subscription must have been active for at least seven days.
How it works
The benefit is activated once, from ChatGPT’s billing settings or from the API platform. You must own the subscription (or the Business workspace) and the API organization that will receive the credits, with the same email address on both sides. For Business, a simple admin role is not enough. A subscription links to one API organization only, and an organization can have only one such link.
Credits are then deposited automatically at each renewal. They expire at the end of the billing cycle, with no rollover, and the first payment is prorated based on remaining time. No payment method is needed on the API side to use them; once the free balance is exhausted, without purchased credits, requests fail with a 429 error (credit_balance_exhausted).
What the credits cover
According to OpenAI, they fund paid usage of the API platform: Responses and Chat Completions, Agents (including OpenAI-hosted sandbox), Decisions, GPT-Live and Realtime for voice, Images, and built-in tools (web search, file search, Code Interpreter). However, they do not cover Codex used via API key and do not increase ChatGPT or signed-in Codex usage limits. Organization rate limits apply as normal.
What remains unclear
OpenAI warns that availability “also depends on the activated cohort and country,” without publishing the list of countries concerned: the offer may therefore not appear right away for all eligible subscribers. The company adds that the benefit “may change or be withdrawn in the future,” with no guaranteed duration.
Our take
This is a concrete bridge between consumer ChatGPT and the developer platform. For a Pro 500 subscriber, the offer reimburses the subscription price in API credits, making this tier much more attractive for anyone building prototypes or agents. For OpenAI, the goal seems clear: move its most engaged subscribers to the API, where usage is then paid by consumption. The limits are real: non-rollover credits, one linked organization only, Codex via API key excluded, and a phased rollout by country. For a Business team, the $500 per workspace cap remains modest against a real production load: it’s an experimentation budget, not an operating one.
Sources
- OpenAI Developers (X) — announcement of API credits for ChatGPT Pro and Business subscribers Primary source
- OpenAI Developers — API credits for ChatGPT subscribers Primary source
- OpenAI Help Center — API credits benefit for eligible ChatGPT subscriptions Primary source
- ChatGPT (X) — relay of the announcement with link to billing settings Primary source
A primary source comes directly from the company, lab or organization concerned. A secondary source reports the information without being its author: we flag it as such. Spotted an error? See our corrections policy.


