The OpenAI API is not included with a ChatGPT subscription. ChatGPT and the API platform use separate billing systems, so paying for ChatGPT Plus, Pro, Business or another workspace plan does not add API credits to an API organization.
To use the API beyond any credits that may already appear on an eligible account, an organization owner sets up API billing separately. OpenAI’s current help documentation says new API accounts use prepaid billing, while some existing and enterprise arrangements can be billed differently.
ChatGPT billing and API billing are separate
The split is easiest to see in the settings. ChatGPT subscriptions are managed in ChatGPT or the workspace admin area. API organization owners use the API billing overview.
OpenAI’s billing guide says API charges depend on the models and features used. That can include token usage plus applicable tool or storage charges. Current unit prices belong on the API pricing page, because they can change independently of a ChatGPT plan.
This separation also means there are two different questions:
- Can I use ChatGPT? That depends on the ChatGPT account or workspace plan.
- Can this API organization send requests? That depends on its API billing state, credits and limits.
A payment method saved for one product does not automatically fund the other.
Is there a free OpenAI API tier?
Do not assume that creating an account or buying ChatGPT includes free API usage. OpenAI’s prepaid-billing documentation says that if an API account has free credits, those credits are used before purchased credits. It does not promise a free-credit grant to every new account.
The reliable check is the API organization’s billing overview. If the credit balance is zero and no other billing arrangement is active, requests can fail with a billing error even while ChatGPT works normally.
The API playground also uses API capacity. It is a developer interface for the same platform, not a way to spend a ChatGPT subscription.
How prepaid API billing works
Under OpenAI’s prepaid billing guide, an organization owner adds payment details and buys credits before making paid API calls.
As checked on October 11, 2026, the guide states:
| Setting | Current documented behavior |
|---|---|
| Minimum initial purchase | $5 |
| Default initial amount | $10 |
| Credit expiration | One year after purchase |
| Auto-reload during setup | On by default unless switched off |
| Minimum automatic recharge | $5 |
| Maximum balance or recharge | Depends on the account’s trust tier |
Purchased credits are generally non-refundable unless law, contract or an approved exception requires otherwise. OpenAI lists verified billing errors, confirmed unauthorized activity and certain confirmed service or account failures as examples that may qualify for review.
A successful purchase can take a few minutes to appear. Buying more credits is therefore not an instantaneous recovery step for a production service.
Auto-reload limits are not usage limits
Auto-reload buys more credits when the balance drops below the threshold you choose. You can set the balance to restore and an optional monthly cap on automatic purchases.
That monthly cap controls only automatic recharges. Manual purchases do not count toward it, and the cap does not prevent the organization from using credits it already holds. A team that treats the reload cap as a hard spending ceiling can still spend more through manual purchases or a balance acquired earlier.
Use separate application budgets, alerts and organization limits for cost control. Also keep product-level retry behavior in the calculation. A failed job can consume tokens before failing, and an automatic retry can repeat that cost.
Why a prepaid balance can go negative
OpenAI says API access may not stop immediately when prepaid credits run out. Usage processed during that delay can create a negative balance, which is deducted from the next purchase.
This is another reason not to treat the displayed balance as a real-time circuit breaker. Billing data and usage processing can lag behind requests. A production system needs its own request caps and monitoring if an abrupt stop matters.
When the balance is exhausted, requests can return a billing error with the code credit_balance_exhausted. Allow time for a new purchase to post before retrying.
Credit balance, spend limits and rate limits are different
A positive balance answers only one question: whether prepaid value is available. Requests can still fail because of:
- request or token rate limits;
- the organization’s approved monthly usage limit;
- an enforced spend limit;
- unsupported access to a model or feature;
- an ordinary API validation or server error.
Our guide to OpenAI API rate limits and 429 errors separates retryable capacity errors from account and billing problems. Repeating a request with insufficient credits does not fix the account, and aggressive retries can make a separate rate-limit problem worse.
Estimate the bill from the workload
Start with the model and feature rates on the pricing page, then add the behavior of the application:
- Count input, cached input and output tokens separately when the model’s pricing does.
- Include tool calls, storage or other metered features used by the workflow.
- Estimate how often requests fail after consuming work.
- Include automatic retries and duplicate jobs.
- Test a representative batch before setting a monthly budget.
For delay-tolerant work, the OpenAI Batch API can change the price and completion model. For repeated context, prompt caching may reduce eligible input cost. Neither feature makes the API part of a ChatGPT subscription.
Which billing page should you open?
Use the page that matches the charge:
| Problem | Where to look |
|---|---|
| ChatGPT web subscription or invoice | ChatGPT Settings, Billing |
| ChatGPT Business workspace | Workspace settings, Billing |
| API credits, payment method or usage | API organization billing overview |
| Current API unit prices | OpenAI API pricing page |
| API rate or usage errors | API limits, usage and error details |
For API billing, confirm the organization selector before changing anything. One login can belong to several organizations, each with its own owners, balance and limits.
