Latest in AI
ChatGPT Pro and Business API Credits: Amounts, Eligibility and How to Claim
OpenAI is linking eligible subscriptions to API credits, but the billing cycle, organization ownership and exclusions matter before you build around them.
OpenAI announced API credits for eligible ChatGPT Pro and Business subscribers on October 28. The benefit provides up to $500 a month to build apps and agents through a linked API organization. It does not add more ChatGPT usage, and the maximum is not what every subscriber receives.
For someone already paying for an eligible plan, this creates a useful budget for testing a product idea. The important questions are how much actually arrives, when it expires and which account spends it.
How much API credit does each plan get?
The announcement lists these full-period amounts:
| Subscription | API credit allowance |
|---|---|
| Pro 100 | $100 per monthly billing period |
| Pro 200 | $200 per monthly billing period |
| Pro 500 | $500 per monthly billing period |
| Business Standard | $20 per paid seat |
| Business Premium | $100 per paid seat |
Business contributions share a $500 monthly workspace cap. This is a pooled allocation, not a separate $500 grant for every employee.
The first grant is prorated for the remaining billing period. Annually prepaid Business workspaces receive a yearly grant upfront, capped at $6,000, with the initial amount also prorated. Unused credits expire with the relevant billing cycle rather than rolling over.
Who can claim, and where?
OpenAI's eligibility guidance requires an eligible paid subscription active for at least seven days. The person linking it must own both the subscription or Business workspace and the receiving API organization, using the same account email. Business membership or an admin role alone is insufficient.
Plus and free trials do not qualify. Availability also depends on the enabled country and cohort, so a qualifying plan does not guarantee the offer is visible immediately.
Open the eligible account's billing settings in ChatGPT, choose the API credit benefit and confirm the receiving organization. Then verify the grant in API Platform billing. Linking an account and receiving credits are separate outcomes. Choose carefully: the link is one subscription or workspace to one API organization.
What the credits cover, and what they do not
The developer guide covers paid API usage such as Responses, Agents, voice, images and built-in tools, including applicable usage and storage charges. Codex usage through API keys is excluded. Signed-in Codex and ChatGPT allowances do not increase either.
An API payment method is unnecessary while an active grant covers usage. Promotional credits are spent before purchased credits. If neither balance remains, requests fail with HTTP 429 and credit_balance_exhausted; ordinary rate limits still apply even with credits available.
That makes this a useful experimentation budget, but a poor substitute for production cost planning. A prototype can work comfortably within a grant while the same workflow becomes expensive when more users arrive or tool calls multiply. Track cost per completed task before treating the subsidy as sustainable economics.
After activation, grants renew automatically while the subscription remains eligible and the benefit is offered. OpenAI says the benefit can change or end. Build around the API's actual costs and treat the credits as room to learn, rather than a permanent discount your product depends on.
I’m Paras. I work at the intersection of AI, engineering and distribution.
I help technical founders turn product launches and engineering decisions into clear content developers can understand and share.