ChatGPT API Credits Arrive for Pro and Business

ChatGPT API credits became a subscription benefit for eligible paid Pro and Business customers on October 28. Owners can activate the benefit by linking an API organization they own, then use the grant for eligible Platform usage. Pro grants match the $100, $200 and $500 monthly tiers; Business grants depend on paid seats and have a workspace cap. The benefit requires activation and does not increase signed-in Codex usage limits.

ChatGPT API credits: the grant and its limits

OpenAI’s benefit guide lists monthly Pro grants of $100, $200 and $500. Business Standard seats contribute $20 each and Premium seats $100 each, with a $500 monthly workspace cap. The first grant is prorated for the remaining billing cycle. Monthly unused credits expire at the cycle boundary instead of rolling over; prepaid annual Business grants follow their annual billing cycle.

Eligibility requires a paid Pro or Business subscription at least seven days old, ownership of the subscription or workspace, ownership of the receiving API organization, and matching ChatGPT and API account email addresses. Free trials and complimentary subscriptions do not qualify. These conditions matter before a developer treats an advertised grant as an available application budget.

The new benefit creates a practical entry point for subscribers who want to build a small application. It also makes the choice of organization important: the grant belongs to the organization linked during activation. An API key from a different organization will not spend that balance. Keep the receiving organization visible in the project’s setup notes.

Activate the benefit in the correct account

The official guide provides claim flows from ChatGPT billing and API Platform billing. In either flow, inspect the subscription and receiving organization before confirming the link. A person who belongs to several workspaces should verify ownership rather than assuming that membership is sufficient. The organization used for an existing project may differ from the personal organization offered to a new API user.

After activation, open Platform billing and confirm the actual credit balance. Record the current cycle end date with the project budget. The first partial-cycle grant can be smaller than the monthly headline amount, which makes a full-month estimate unsuitable for the first few days. Later grants depend on continuing eligibility and the benefit remaining available.

Then create or select a project within that organization and use its project key in the application. Store the key in the application’s secret configuration, keep it out of client-side code and check the organization shown in your API logs. The API setup guide explains the site’s existing request and error-checking workflow.

What an application can spend the grant on

OpenAI lists eligible Platform services including Responses, Agents, Decisions, realtime voice, image generation and built-in tools. Codex usage through API keys is excluded. The grant also does not expand ChatGPT or signed-in Codex limits. Treat a subscription allowance, purchased ChatGPT credits and a Platform API grant as separate balances when comparing the cost of a workflow.

This distinction is especially relevant for a developer using Codex to build an application. The coding session and the finished application’s API requests can have different billing paths. Receiving API credits for an organization does not establish that the coding agent’s API-key usage is covered. Check which product makes each request and where its usage appears.

The pricing guide separates these budgets. Use the pricing calculator to estimate text-token costs for a candidate model, then add the other services the application uses. A tool-heavy agent or image workflow needs more than a text-token estimate, even when both spend the same organization balance.

Build a trial with an explicit spending boundary

Start with a small, measurable workflow. For example, choose a fixed set of support messages, define the output fields and compare the result against labels a reviewer can check. Keep the evaluation dataset stable while changing prompts or models. The goal is to learn whether the application solves the intended task within the available budget.

Track requests, input, cached input, billable output and any tool charges. Set an internal application budget below the remaining credit balance so an unexpected loop or retry pattern does not consume the trial allowance. A request limit and an emergency stop are useful even when the initial experiments are manual. These are suggested project controls, not additional conditions imposed by the benefit.

When estimating runway, divide the available balance by the observed cost of a successful result, including retries. Use the actual prorated grant and its expiry date. A low average cost can still exceed the remaining cycle’s budget if traffic increases, and unused credits do not become a permanent reserve for later experiments.

Plan for expiry and exhausted credits

The official guide says free API credits are used before purchased API credits. When the free grant runs out, purchased credits can keep requests running. With no remaining credits, requests fail with HTTP 429 and the credit_balance_exhausted error code. Monitor the balance and handle that error before giving other people access to the application.

For an experiment, an explicit pause at the budget boundary may be the intended behavior. For a service that must continue, decide who owns paid credits and renewal monitoring before launch. Record that decision with the application’s operating notes. The benefit helps fund a trial; a working billing and failure-handling plan keeps the trial’s behavior understandable when the grant ends.