Your Subscription Is Now an API Budget: OpenAI Gives Pro and Business Up to $500 a Month in API Credits

In one sentence: your subscription fee can now pay your API bill

On 28 October 2026, OpenAI added a modest but genuinely useful benefit to its API changelog: eligible ChatGPT Pro and Business subscribers can now claim free monthly API credits of up to $500. The way it works is to link your subscription to an API organization you own; credits then arrive automatically when the subscription renews. For the first time, two previously separate ledgers are connected — the monthly fee you pay for ChatGPT on one side, and the usage fees you pay for API calls on the other. For Pro users who already build with the API, the subscription stops being just chat access and becomes a development budget as well. For users who only chat and never touch the API, the money effectively does not exist, and claiming it changes nothing about the chat experience. That premise has to be clear before any of the judgments below can hold.

The allowance table: Pro gets a fixed amount, Business pools seats

The amount follows your subscription tier exactly, with no formula to work out. Pro's three tiers each get their own number: $100 a month on the $100 tier, $200 on the $200 tier, and $500 on the $500 tier — the credit matches the subscription price one to one. Business works by pooling seats: each paid Standard seat contributes $20, each paid Premium seat contributes $100, and the whole workspace is capped at $500 a month. As OpenAI's own guide calculates it, 5 Standard seats plus 3 Premium seats come to $100 plus $300, exactly $400; 10 Standard seats plus 4 Premium seats come to $600 before the cap, so the workspace allowance is still $500. Business workspaces that prepay annually do not receive monthly grants; instead they get the full year's grant at once, capped at $6,000, expiring at the end of the annual billing cycle. One more detail on the first grant: it is prorated for the time left in the billing period, so it is not the full amount. Always check the actual number shown on the billing page before confirming.

How to claim: two paths, one organization

There are two claim paths, and either one gets you there. From the ChatGPT side: sign in with the account that owns the subscription, open Settings and then Billing, find the API credits benefit, start the claim flow, select the API organization that will receive the credits, and confirm. From the API Platform side: open the organization's billing settings, find the benefit, select an eligible subscription or workspace you own, and confirm the link. Both paths share three requirements, and all three are mandatory. First, the subscription must be paid and active for at least seven days; free trials and complimentary subscriptions do not qualify. Second, the person claiming must own both the subscription or workspace and the receiving API organization — an admin role alone is not enough. Third, the ChatGPT account and the API account must use the same email address. Once linked, no separate API payment method is needed to start spending, and free credits are consumed before any credits you purchased yourself. After claiming, verify in the API Platform billing page: the benefit is only real once a grant with an amount and an expiry date appears there. Linking the organization and receiving the credits are two separate steps; do not mistake the first for the second.

What it covers — and what it does not: the Codex exclusion matters most

The coverage is broad and covers most ordinary development usage: the Responses API for text, code, and image understanding; the Agents API, including OpenAI-hosted sandbox charges; the Decisions API for structured decisions; GPT-Live and the Realtime API for real-time voice; the Images API for image generation and editing; and built-in tools plus their associated usage and storage charges, such as web search, file search, and Code Interpreter. Two exclusions deserve a red line. First, Codex usage billed through API keys is not supported by this benefit — that sentence is from OpenAI's own guide, and it means you cannot use these credits against Codex calls made with an API key. Second, the credits do not raise your limits in ChatGPT or in signed-in Codex; chat allowances and API credits are two wallets that do not connect. Remember both, and you will not end up wondering why $500 of credits did nothing for your Codex usage. When the credits run out, there are two cases: if the organization still holds purchased credits, usage continues against those; if nothing remains, requests fail with HTTP 429 and the error code credit_balance_exhausted, at which point you either add credits or set up auto recharge.

Four traps to avoid

The first trap is the prorated first grant. Many people plan their first month against the full amount, only to find that half a billing period remains and the grant is half the size, so usage stops midway. Treat the first period as a trial run for the process, and plan against the full amount only from the second month. The second trap is expiry without rollover. Credits expire at the end of the billing cycle and never carry over; the annual workspace grant likewise expires at the end of the annual cycle. Rushing to burn credits at month's end achieves nothing — it is better to move a fixed monthly cost into the allowance. The third trap is picking the wrong organization. The organization you select at claim time is the one that receives the money, and changing it later requires contacting support; it is not a self-serve switch. Company accounts should be especially careful not to link a personal subscription's credits to a company organization, or vice versa. The fourth trap is losing the link on downgrade. If you drop from Pro to Plus, Go, or Free, the API organization link is removed at the end of the billing cycle; moving from Pro to Business ends the Pro link too, and the Business workspace can only claim its own benefit after its paid subscription has been active for seven days. Cancelling alone does not immediately revoke credits already issued — you can use them until they expire — but no new grants will arrive.

Who actually benefits, and who gets nothing

Start with who benefits. If you already spend close to your subscription price on the API every month, the credits flow straight back: a Pro 100 user spending around $100 a month on API calls effectively sees that bill go to zero, with headroom left over for experiments — as long as usage does not jump above $100. For a solo developer or a small team, the best use is to move one stable monthly cost — a scheduled job, a test script, an internal assistant — into the allowance, turning it into a predictable fixed cost. Now the other side: users who only chat in ChatGPT and never open the API Platform gain no extra chat allowance from claiming; Plus, Go, Free, and Enterprise users are not eligible at all; and most importantly, if your main spend happens to be Codex through API keys, this money cannot help, so do not upgrade a subscription for it. OpenAI's guide also leaves an opening: credits arrive on renewal while the benefit is still available and the subscription is still eligible, so the rules may change later. The rational way to treat this is as a monthly development budget, not as a permanent promise that the subscription got cheaper.

Three worked scenarios: what the money is really worth

The allowance table alone does not tell you what the money is worth; three concrete scenarios do. Scenario one: a fictional solo developer, Xiao Lin, spends about $30 a month on the API, mostly scheduled scripts and tests. His Pro 100 allowance is $100, so claiming it zeroes that $30 bill and leaves $70 of headroom for trying new features — provided he does not suddenly expand usage beyond $100. Scenario two: a five-person team on Business with 4 Standard seats and 2 Premium seats pools $80 plus $200, a total of $280, under the $500 cap, so the full amount can be claimed; if the team grows to 10 Standard and 4 Premium seats, the math gives $600, but the cap still holds it at $500 — extra seats do not raise the ceiling. Scenario three: a heavy user already spending more than $500 a month on the API only gets the first $500 covered; everything beyond that settles against purchased credits as usual, and no subscription tier lifts that ceiling. Together, the scenarios make one point: the money works best for people whose usage sits inside the allowance and recurs steadily, letting a fixed cost move entirely inside it. For spiky usage, or usage already far above the allowance, the effect is a smaller bill, not a different cost structure.

A near-identical offer across the street: same numbers, different details

There is also an industry backdrop worth noting: according to multiple reports, Anthropic introduced a similar API credit for Claude Max and Team subscriptions in early October, with the same Business-side shape — $20 per Standard seat, $100 per Premium seat, and a $500 monthly workspace cap. Two vendors landing on almost identical numbers suggests this is not a one-off promotion but a competition over converting chat subscribers into API users: whichever vendor first turns a subscription fee into a development budget gets the first shot at those users' API spending. But identical numbers do not mean identical rules, and at least three details cannot be carried across. First, OpenAI's Pro credits are fixed per tier at $100, $200, and $500, while Anthropic's offer follows its own Max and Team subscription shapes, so the tier structures differ. Second, OpenAI explicitly excludes Codex usage through API keys; the other vendor's corresponding exclusion must be read in its own documentation, not assumed. Third, OpenAI's claim requirements — seven days paid, matching email, dual ownership — are very specific and must be checked one by one rather than assumed from “I'm a subscriber, so I qualify.” The comparison is here not to judge who is more generous, but to warn that copying a claim flow from “the other vendor has it too” is the fastest way to get stuck at the claim step.

Pre-claim checklist: six boxes, all ticked, before you confirm

Finally, a pre-claim checklist: tick all six boxes before confirming. One: has the subscription been paid for at least seven days? If not, wait a few days — starting the flow early earns nothing. Two: do the ChatGPT account and the API account share the same email? If not, unify them first, or the link will fail. Three: are you the owner of the subscription or workspace and also the owner of the receiving API organization? An ordinary admin role is not enough here. Four: did you pick the right receiving organization? Personal projects go to a personal organization; company projects need a word with whoever owns them first, because changing the organization later means going through support. Five: did you read the prorated first grant? The number shown on the billing page is the actual amount; do not plan against the full-period figure. Six: is your main usage Codex through API keys? If so, these credits will not help — do not upgrade a subscription for them. If any box is uncertain, stop and check before continuing: the claim flow itself is simple, but fixing a wrong claim is expensive. Once the checklist is done, the allowance table, coverage, and expiry rules above actually land in your account instead of staying in the news.

Quick answers to the six most common questions

Can Plus users claim? No. Only the three Pro tiers and Business workspaces qualify; Plus, Go, Free, and Enterprise are out, and Edu is not on the guide's eligible list either. Can credits be cashed out or transferred? No. They can only be spent inside the linked API organization — no transfers to other accounts, no cash value. Will claiming raise my ChatGPT message limits? No. The guide states plainly that the credits do not increase ChatGPT or signed-in Codex usage limits; the two wallets do not connect. How does this work for annually billed Pro users? The guide describes allowances per monthly billing period — $100, $200, $500 for Pro — and the amount actually granted in an annual billing setup should be read from the billing page; do not extrapolate from the monthly table without checking the prorated first grant. What happens if a Business workspace changes owners? Eligibility attaches to the owner identity of the subscription or workspace, not to an admin title, so a new owner must re-establish the link; the old link does not transfer automatically. Will OpenAI warn you before credits expire? The guide promises no expiry reminder, so the safe habit is to check the API Platform billing page a week before the cycle ends and schedule fixed costs inside the cycle rather than discovering a zero balance at month's end. These six answers cover most claim-time sticking points; for anything beyond them, check the official guide first rather than a second-hand summary — with allowance rules, one wrong number in a summary throws off the whole budget.

Do not confuse this with the other October Pro news: this is the API bill, not chat limits

October brought more than one piece of Pro news from OpenAI, and they are easy to mix up. In the same week, OpenAI also announced that Work and Codex allowances would double across Pro tiers and cancelled the planned Pro 200 cut — that is about usage rules on the chat and Codex side, which this site already covered separately in cycle127. This article is about a different ledger: development credits on the API Platform side. Both landed in the same week for the same Pro users, but the wallets, rules, and expiry behavior differ: the limit doubling affects how much you can use inside ChatGPT and Codex, while the API credits affect how much you can spend on the API Platform. Only by keeping the two ledgers apart can you work out your true total cost. For vibe developers, the practical conclusion is: if you already pay an API bill for your product, go claim the credits, link the right organization, and confirm the grant landed, and only then judge whether upgrading a tier pays off. If you have not started using the API yet, the news simply means “remember this money exists when you start” — not a reason to spend an extra cent today.

One action to take: claim first, upgrade later

If you take one action from this article, make it this: claim the credits, link the right organization, confirm the amount and expiry date on the billing page, and only then discuss upgrading a tier. Many people react to this kind of news by first calculating whether the $500 tier is “more worth it,” but the correct order is the reverse: first check whether your current tier's allowance already covers your current API spending, then judge whether the extra allowance from an upgrade would actually be spent. The most common miscalculation in upgrade math is treating the “allowance ceiling” as “actual benefit”: the $500 tier's allowance is indeed $500, but if your monthly API spending is only $80, the extra $420 does not come back to you as cash — it simply expires at the end of the cycle. Conversely, if your monthly API spending sits stably above $300, the gap between the Pro 200 allowance of $200 and the Pro 500 allowance of $500 is a real cost difference, and only then does upgrading have a number behind it. Credits, chat limits, and subscription prices are three separate ledgers; claiming solves the first, upgrading addresses the second and third, and mixing them together guarantees a wrong answer.

One more note for vibe developers: the best use of these credits is to write them into your budget as a fixed cost, not to treat them as free chips for experiments. A fixed cost means the jobs that run every month without fail — scheduled syncs, test scripts, calls from a small internal tool — moved into the allowance first, so the monthly API bill becomes a predictable number. Volatile usage, like trying a new feature or running a large batch experiment, should still go against purchased credits, so that a sudden spike in one month does not wreck cash flow. Used on fixed costs, the allowance saves you a definite amount every month; used on experiments, it merely postpones the first real payment. OpenAI has not handed out a discount here, but a monthly budget with an expiry date, and budgets are always best spent securing fixed costs before funding elastic tries. Claimed, linked correctly, confirmed landed, and pointed at fixed costs — that is when this news actually pays off for you.