Introduction: the two bills I have been paying for years
For years I have lived with two separate OpenAI bills. One is the ChatGPT subscription I pay to chat, brainstorm, and draft. The other is the API bill I pay when I actually build something — a tool, an agent, or a small automation that calls a model in the background. Same company, same models, yet the money never crossed over.
On October 28, 2026, OpenAI finally connected them. The company added the benefit to its API changelog and announced it on its developer account: eligible ChatGPT Pro and Business subscribers can now claim free API credits every billing cycle, worth up to $500 a month. This is not a trial or a one-time promotion. As long as your subscription stays eligible, the credits keep coming each cycle — and if you don't use them, they disappear. Here is the honest version.
What OpenAI actually announced
OpenAI's developer documentation now has a page titled "API credits for ChatGPT subscribers," and the company's developer community post lays out the claim flow in a few lines: claim your API credits in ChatGPT billing, then use the OpenAI Developers plugin in ChatGPT or Codex to create an API key and start your next project.
The deal is simple: OpenAI is turning paying chat subscribers into API customers. Instead of asking a Pro subscriber to also open a separate API account and fund it from zero, it hands them a monthly budget for the developer platform. The subscription and the API still bill separately — this does not merge them — but the credit bridges the gap. A subscriber who has already paid is far more likely to build something if the first experiments cost nothing extra.
Anthropic announced a near-identical structure on October 7, 2026, so this looks like the new normal, not a gimmick.
How much you actually get
If you are on ChatGPT Pro, your credit equals your tier: the $100 tier gets $100 a month in API credits, the $200 tier gets $200, and the $500 tier gets $500. At the top end that is genuinely generous — a $500 Pro subscriber effectively gets their subscription amount back as API spend every month, as long as they use it.
If you are on ChatGPT Business, the credit is calculated per paid seat and pooled across the workspace. Standard seats contribute $20 each per month, and Premium seats contribute $100 each, but the workspace cap is $500 per month. A workspace reaches the cap with 25 Standard seats, or just five Premium seats — and seats beyond that add nothing. A 40-person Standard workspace does not get $800. It gets $500.
Annual billing has its own twist. A Business workspace that pays for a full year upfront receives the whole year's credit in one grant, capped at $6,000, expiring at the end of the annual billing cycle. That is a bigger pot to waste if you leave it untouched. For everyone, the first grant is prorated: claim halfway through your cycle and you get roughly half a cycle's worth, still expiring at the end of that cycle. Claim as close to the start of your cycle as you can.
Who qualifies — and who does not
You qualify if you have an eligible ChatGPT Pro or Business subscription active for at least seven days, you own that subscription or Business workspace, and you own the API organization that will receive the credits. Your ChatGPT account and your API organization must also use the same email address. All of those conditions have to hold at once. Being a subscriber is not enough if someone else owns the workspace, and owning an API organization is not enough if it sits under a different email.
You do not qualify on ChatGPT Free, Go, Plus, Enterprise, or Edu plans. That Plus exclusion will sting, because Plus is by far the most common paid plan. If you are on Plus and hoping for a free API budget, this benefit is not for you, at least not as OpenAI has defined it today. Finally, you have to claim the benefit — it is not automatic. If you never go into billing and link an organization, nothing arrives. Treat it like a rebate you have to activate.
How to claim it, step by step
First, confirm you are on an eligible plan active for at least seven days. If you just upgraded to Pro yesterday, wait out the seven days rather than fighting a claim screen that will not cooperate yet.
Second, check your emails match. Sign in to ChatGPT with the account that owns the subscription, and make sure your API organization is under the same email address. Fix a personal-versus-work email mismatch before you claim, because the link depends on it.
Third, claim in ChatGPT billing. Pro users claim under Settings, then Billing. Business users claim through workspace billing settings or the Admin Console. You will be asked to confirm which API organization receives the credits. Choose deliberately: if you run client work and personal experiments, keep the credited organization separate from production client billing, so an expiry surprise never touches a client's project.
Fourth, verify the grant landed. Check your API organization's billing view for the actual balance and expiry date — remember the first grant is prorated — then create an API key and test with a tiny request, watching the free balance move before any purchased credits.
What the credits cover — and what they do not
The coverage is broad. The credits cover usage charges on the API Platform for the Responses API, the Agents API, the Decisions API, GPT-Live and the Realtime API for voice, and the Images API, plus built-in tools such as web search, file search, and Code Interpreter, including their associated fees. That covers the main ways developers build today: completions, agents that take actions, voice features, image generation, and retrieval over your own documents.
Two exclusions matter. Usage via an API key for Codex is not covered, so if Codex is your main API spend, these credits will not help you. And the credits do not increase your usage limits for ChatGPT or Codex — they are API money, not a subscription upgrade.
Free credits are applied before purchased credits. When they are exhausted with no other balance left, requests fail with HTTP 429 and the code credit_balance_exhausted — a hard stop. Never let anything others depend on run on free credits alone without a paid fallback. You can spend the grant without adding a payment method, but still guard the key.
Why this matters for WordPress and web developers
Model prices have been falling fast — I wrote earlier this month about OpenAI and Anthropic cutting LLM prices by up to 80 percent — so a $100 to $500 monthly credit now stretches much further than it would have a year ago. A budget that once bought a weekend of experiments can now fund months of prototyping.
For WordPress developers, this is well timed. So much WordPress work is repetitive and document-heavy — pre-sales questions, product descriptions, support triage, help articles — and those are exactly the jobs the Responses API and file search are built for. A $100 credit is enough to prototype a support assistant over your own docs without asking a client to fund an API bill first.
It also changes how I judge a subscription: not just the chatbot's value, but the chatbot plus the API credit. For a developer who builds, that flips the answer quickly.
What I would actually build with it
With a $100 credit, I would run three small experiments: a support assistant over my own docs with a human approving every reply; a WordPress content helper drafting descriptions and FAQs for a human editor, never auto-publishing to a client site; and one voice or image demo, since those are hardest to judge from reading alone.
With a $500 credit, I would add one discipline: usage alerts at 50 and 80 percent, and a rule that no client-facing feature runs on expiring credits alone. Free money is the worst foundation for something other people depend on, because it vanishes on a schedule you do not control. Use it to learn and prototype. Pay for the thing you ship.
The honest caveats
The expiry rule is the biggest trap. Unused credits do not roll over, monthly or annually. Set a reminder a few days before your cycle ends, and treat an untouched balance as a task, not a savings account. The cap is the second trap: more Business seats do not mean more credit past $500 a month, so do not add seats to grow the pool. The ownership and email rules are the third: shared workspaces and personal-versus-work email splits cause friction, so sort out ownership before you claim, not after a grant lands in the wrong organization. And do not confuse this with a price cut on everything — Codex via API key is excluded, chat limits do not rise, and Plus users are excluded entirely.
Conclusion: claim it, then spend it on learning
OpenAI's new API credits are a real benefit with real strings attached. For eligible Pro and Business subscribers, $100 to $500 a month of recurring API spend is enough to prototype agents and AI features that would previously have needed a separate budget conversation. My advice is simple: if you qualify, claim it this week, verify the prorated grant actually landed, and spend the first cycle on small experiments with a human in the loop. The worst outcome is not spending the credits badly. It is letting them expire untouched while you meant to get around to them.
FAQ
Who gets OpenAI's free API credits?
Eligible ChatGPT Pro and Business subscribers whose subscription has been active at least seven days, who own the subscription or workspace, and who own the receiving API organization under the same email address. Free, Go, Plus, Enterprise, and Edu plans are not eligible.
How much API credit do Pro and Business subscribers get?
Pro: $100, $200, or $500 per month by tier. Business: $20 per paid Standard seat or $100 per paid Premium seat, pooled and capped at $500 per month, or $6,000 for an annual workspace paid upfront.
How do I claim the API credits?
Pro users claim under Settings, then Billing, in ChatGPT. Business users claim through workspace billing settings or the Admin Console, confirming the API organization that receives the credits.
Do the credits expire?
Yes. Monthly credits expire at the end of each billing cycle and do not roll over. Annual Business grants expire at the end of the annual cycle. The first grant is prorated to the time left in your current cycle.
What can I use the API credits for?
The Responses, Agents, and Decisions APIs, GPT-Live and the Realtime API, the Images API, and built-in tools such as web search, file search, and Code Interpreter. Codex usage via API key is not covered, and the credits do not raise ChatGPT or Codex limits.
What happens when the credits run out?
Free credits are applied before purchased credits. When they are exhausted with no other balance left, requests fail with HTTP 429 and the code credit_balance_exhausted. You can spend the grant without adding a payment method, but production features need a paid fallback.
