AI usage credits vs API billing: how to choose and govern top-ups
Updated September 30, 2026 · first published September 30, 2026
A top-up is not a universal wallet. “Credits” may mean prepaid API balance, paid-plan overage, or a plan-specific feature allowance. Treat each product’s balance and controls separately; a credit purchase usually does not upgrade a subscription or fund a different billing system.
This guide compares the options documented by Anthropic for paid Claude plans, Anthropic Console API billing, OpenAI ChatGPT plan credits, and OpenAI API prepaid billing. Availability, terms, and controls can vary by account, plan, region, and contract; check your billing screen and applicable agreement before buying.
Choose the billing path that matches the work
| Path | What the balance pays for | How it starts | Good fit | Key control |
|---|---|---|---|---|
| Claude Pro or Max included allowance | Claude conversations and supported plan usage within included limits | Included in the paid subscription | Predictable recurring individual use | Watch plan limits; wait for reset or change plan if usage is consistently insufficient |
| Claude paid-plan usage credits | Eligible Claude and Claude Code usage after a paid plan limit, at standard API rates | Enable under Claude Settings > Usage, add funds, then confirm continuation when prompted | Occasional overage where keeping the same workflow matters | Monthly spend cap, alerts, and optional auto-reload; disable to return to included usage only |
| Anthropic Console prepaid credits | Anthropic API, Workbench, and Claude Code Console usage | Prepay to the Console organization; requests stop when credits run out unless replenished | Applications and development workloads billed by API consumption | Auto-reload threshold and refill target; standard-rate-limit organizations should also consider spend limits and key controls |
| ChatGPT plan usage credits | Only eligible ChatGPT features after included allowance, such as Codex or ChatGPT Work where available | Purchase in ChatGPT or Codex billing settings if offered to the account | Occasional overflow without changing the plan | Optional auto-reload, configured minimum/target and monthly maximum where available |
| OpenAI API billing or prepaid credits | API platform requests; this is separate from ChatGPT subscription and usage credits | Use API billing; eligible accounts can purchase prepaid credits | Product integration or programmatic workloads | API project/org budgets and billing controls; verify whether the account uses prepaid or monthly invoicing |
Claude has two different top-up routes
For individuals already on eligible Pro or Max plans, Anthropic’s paid-plan usage credits extend usage after the plan limit. You see a prompt and choose whether to continue; that continuation is billed at standard API rates, separately from the subscription. Anthropic documents a monthly spend limit, usage alerts, and optional auto-reload. The credits apply to Claude conversations and Claude Code, and the included plan limit still resets on its normal schedule. See Anthropic’s setup and usage-credit FAQ.
Anthropic Console prepaid credits are a separate organization balance for API, Workbench, and Console-based Claude Code. They must be purchased before use; the API and Workbench stop when the balance is exhausted. Auto-reload can buy credits when the balance falls below a chosen minimum and reload toward a chosen amount. Anthropic says purchased Console credits expire one year from purchase and cannot be extended. See Anthropic’s API billing guide.
Do not assume either balance carries into the other. In Claude Code, confirm which account and authentication route is active before enabling a top-up. A Console API key can expose the organization to API charges; separate keys by workload and monitor usage as Anthropic recommends in its API key security guidance.
OpenAI: plan credits are not API credits
OpenAI ChatGPT usage credits extend supported ChatGPT features after plan allowance is used. The supported feature set and purchase availability depend on account and plan. OpenAI explicitly says these are not API credits. If available, auto-reload purchases usage credits after the balance falls below a selected minimum; personal-plan documentation also describes a target balance and optional monthly maximum for automatic reloads. In-flight work may settle after the balance is depleted, leaving a negative credit balance, and a later top-up may first offset it. Personal-plan credits expire after 12 months. Review the ChatGPT credits terms.
OpenAI API billing lives on the API platform. Eligible accounts can use prepaid billing; API credits expire after one year, and usage processed during reporting delay may produce a negative balance. Do not use the ChatGPT usage-credit balance as an estimate of API funding. See OpenAI’s prepaid API billing guide. Business, Enterprise, and Edu ChatGPT workspaces have separate credit arrangements and contract-specific terms; do not apply personal-plan rules to a workspace without checking its agreement.
Govern the top-up before enabling it
- Name the ledger. Record provider, product, account or workspace, billing owner, and whether the balance is subscription usage, feature credits, or API funds.
- Set a stop point. Choose a monthly maximum or project budget where the product offers one. Treat an auto-reload amount as a purchase trigger, not a hard spend ceiling unless the provider explicitly makes it one.
- Start with alerts and manual top-ups. Compare a few weeks of actual usage with the forecast before switching on automatic reload. For continuous production, choose a threshold that gives an owner time to investigate unusual consumption.
- Account for in-flight work. Some credits can settle after a request began, so zero balance or zero overage configuration may not prevent a small negative settlement.
- Track expiration and scope. Keep purchase date, expiry date, eligible product, and account in the ledger. Avoid bulk buying when credit is non-refundable or expires.
- Review access and attribution. Use separate API keys or projects by environment/team where supported; review usage by key, project, model, and time period, and revoke credentials that are no longer needed.
- Reconcile monthly. Match top-up receipts and subscription invoices to provider usage exports and internal cost allocation. Alert on spend velocity, not only remaining balance.
What to choose
Use the included subscription allowance when the workload is interactive and predictable. Choose paid-plan overage credits for occasional continuity after a limit, with a cap and clear user confirmation. Use provider API billing for software workloads that need API access, project-level attribution, and engineering controls. Buy only a modest prepaid buffer if interruption is costly and the expiry window fits expected consumption. If your account exposes no relevant top-up option, do not infer eligibility from another plan or product.
Frequently asked questions
Does a subscription include API calls? Generally, no. Anthropic states that Claude subscriptions and Console API usage are billed separately. OpenAI also separates ChatGPT plan usage from API billing.
Does an auto-reload cap stop every charge? Not necessarily. Read the exact product’s control descriptions: reload settings govern replenishment, while a spend cap or project budget may be a distinct control. In-flight requests can settle after a balance check.
Do credits expire? There is no single rule. Anthropic Console API credits expire one year after purchase; Claude paid-plan usage credits generally do not expire, except the documented Japan rule for purchases from September 10, 2026; OpenAI ChatGPT personal usage credits expire after 12 months; OpenAI API prepaid credits expire after one year. Verify the account’s displayed terms.
Can a negative balance happen? OpenAI documents this for ChatGPT usage credits when concurrent work finishes after depletion and for API prepaid credits when usage reporting is delayed. The Anthropic docs cited here describe stopping API access at exhaustion and do not establish a negative-balance rule for its top-ups.
Related
Want this applied to your stack? Bring the provider bills, gateway logs, and top workflows; we will map the cost drivers and savings path. Book a free audit →