OpenAI confirms monthly API credits for ChatGPT Pro/Business subscribers — up to $500 a month
OpenAI docs confirm ChatGPT Pro plans now include up to $500 in monthly API credits, Business by seat, claimable after 7 days in Settings → Billing.
On October 28, OpenAI published a “ChatGPT Subscription API Credits” guide in its developer documentation: paid ChatGPT Pro and Business subscribers can link their subscription to an API organization and draw a monthly credit grant — $100, $200 or $500 per month matching the three Pro tiers, and per-seat credits for Business capped at $500 per workspace each month. The claim flow lives in ChatGPT’s Settings → Billing, and subscriptions qualify once they are at least 7 days old. So the answer to “does ChatGPT Pro give you API credits” is now yes, in writing.
Key points
- Every Pro tier gets a monthly grant equal to its price: the $100 plan gets $100, the $200 plan gets $200, the $500 plan gets $500. Business gets $20 per Standard seat or $100 per Premium seat, pooled and capped at $500 per workspace per month; annual workspaces receive the whole year at once, capped at $6,000.
- Claiming takes three prerequisites: a subscription at least 7 days old (free trials don’t count), the same email address on the ChatGPT and API accounts, and ownership of both the paying workspace and the receiving API organization.
- The credits cover API platform usage only — Codex calls through API keys are excluded; unused credits expire at the end of each billing cycle with no rollover, and an exhausted balance returns HTTP 429 (
credit_balance_exhausted).
Background
The benefit closes a loop we flagged in our September 28 coverage of the ChatGPT Pro revamp. Back then the pricing page had renamed the two Pro tiers Pro Standard and Pro More, and a merged PR in the openai/codex repository leaked a $500/month “Pro Max” tier — a placeholder until OpenAI confirmed it. A month later the official docs list that $500 tier and attach a $500 monthly API credit grant to it. The industry context is just as direct: Anthropic announced monthly API credits for Claude Max and Team plans on October 7, with Max 20x getting $200 and Team capped at $500. The two schemes are near-identical in shape, three weeks apart.
The facts
The official documentation spells out the grant per tier (per the developers.openai.com guide page, dated October 28):
| Subscription tier | Monthly API credit |
|---|---|
| Pro ($100 plan) | $100 |
| Pro ($200 plan) | $200 |
| Pro ($500 plan) | $500 |
| Business Standard seat | $20 per seat |
| Business Premium seat | $100 per seat |
Business seat credits pool across the workspace and cap at $500 per month. The Japanese blog Apsis did the arithmetic: the grant stops growing past 25 Standard seats or 5 Premium seats. Annual Business workspaces receive the full year’s grant in one issuance, capped at $6,000, expiring only at the end of the annual cycle.
Issuance and expiry, per the docs: monthly subscriptions get a grant each cycle, prorated for the time left in the first cycle; credits expire at the end of the billing cycle without rolling over; free credits burn before purchased ones. Upgrades (a plan change or added seats) can add prorated credits; downgrading to Plus, Go or Free unlinks the organization at the end of the cycle. Cancelling stops future grants, but credits already issued remain usable until they expire.
Coverage spans 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, including their storage charges. Two exclusions sit on the same page: Codex usage through API keys doesn’t count, and the credits don’t raise ChatGPT’s or signed-in Codex’s usage limits. Once the balance runs dry, requests fail with HTTP 429 and error code credit_balance_exhausted; if the account also holds purchased credits, billing falls through to those.
How to claim
OpenAI documents two routes. In ChatGPT: Pro users open Settings → Billing; Business users go to workspace billing settings or the Admin Console, find the API credits benefit, and pick the API organization to receive the grant. On the API platform: sign in with the subscription email, select the organization, and claim from its Billing page.
Two details beyond the prerequisites are easy to miss: no payment method is required on the API account while free credits remain active, and a Pro-to-Business switch breaks the old link — the new workspace must be paid for 7 days before a fresh claim.
What others say
Crypto Briefing reads the benefit as OpenAI nudging paying chat users toward the developer platform — turning subscribers into builders rather than just rewarding heavy chatters. It also flags the flip side of the $500 workspace cap: mid-sized teams get nothing like per-seat parity, making this a sweetener for small teams, not a substitute for real API budgets. ChainCatcher published the most complete walkthrough of the claim flow and proration rules, matching the official docs item for item. The Japanese blog Apsis warns seat planners that grants stop growing past 25 Standard or 5 Premium seats, so don’t budget by headcount. As of publication, OpenAI has issued no separate press release or executive statement; every report traces back to the docs and the changelog.
Our take
For developers paying for both a Pro subscription and an API bill, this is a straight offset: the $200 tier’s $200 monthly grant, fully used, halves the effective subscription cost. But two exclusions decide who actually benefits. Codex usage through API keys doesn’t count, so heavy Codex users gain nothing real. And with no rollover, someone who calls the API occasionally loses the balance every month — the real winners are teams with steady, predictable API consumption. The $500 workspace cap means Business credits are designed for small teams, and stop there. One more caveat: OpenAI announced nothing beyond the docs, and this company has a record of adjusting such details quietly — treat the fine print as moveable.