ChatGPT Credits: Features, Plan Usage & API Billing Explained

Work/Codex credit scope and API error codes checked · October 10, 2026

This review verifies the shared Work/Codex pool, documented credit rates, connected-app boundary and API diagnostics. It does not verify a particular account’s allowance, credit-pack checkout, refund policy or ordinary-chat message cap.

Before buying credits, identify the product and the meter that stopped your task. ChatGPT Work and Codex share usage, credits and limits. That does not make credits an unlimited ordinary-chat pass, and it does not fund requests made with an OpenAI API key. A paid subscription, an included allowance and a credit balance answer different questions.

The short answer

Your plan’s included usage is used first. Buying credits does not change that plan or raise every ChatGPT limit.
Work and Codex draw on the same pool. Moving a task between them is not a new allowance; eligible connected apps can also use this pool.
For Work/Codex, check the usage dashboard. Eligible Work users can also see remaining usage in the web sidebar. Workspace controls apply only where the plan makes that activity eligible.
A credit estimate is not a message-count guarantee. Task context, model, tools and speed affect consumption.
If automatic purchasing is offered, review its actual trigger, amount, maximum and payment terms before enabling it. This guide does not assume one universal top-up flow.
ChatGPT and the OpenAI API have separate billing systems. A positive API balance does not fund ChatGPT credits, and a ChatGPT credit balance does not fund API calls.

Choose the meter before paying

The warning is inside ordinary ChatGPT chat: record the selected model or tool and the exact reset/access notice. Do not use the Work/Codex rate card below as proof that buying credits removes that warning. If the paid plan itself is missing, follow our subscription-not-showing checks instead.
A delegated Work task or Codex task stopped: check the shared usage dashboard and the account/workspace in which the task runs. In the Codex CLI, /status shows remaining limits. Included usage and paid credits are distinct; read which one the notice identifies.
A third-party app stopped: establish its active billing mode. A ChatGPT login can be sign-in only. In a supported app, eligible Plus/Pro users can separately approve Use your ChatGPT plan; those requests use existing Work/Codex capacity, not a bonus pool. An API-key mode or the app’s own credits is a different route.
A script returned an API error: inspect the API organization/project and error.code, not the consumer subscription receipt. Use the 429 decision table below before either retrying or adding funds.

The connected-app distinction is documented in Sign in with ChatGPT. Connecting an app does not increase the allowance, and the app can still have its own fees. “Uses my ChatGPT account” is not enough information to identify the bill.

If a workspace is involved: ask its owner which activity is eligible for workspace credits and which effective user limit applies. Workspace spend controls do not cover every Codex session or govern API Platform billing. Changing a limit does not itself grant feature access or add credits.

What are ChatGPT credits?

OpenAI describes personal ChatGPT credits as an add-on that lets eligible users continue using supported features after their included plan allowance is reached. The credit balance is tied to the applicable OpenAI account and supported feature, rather than being a universal number of extra ChatGPT messages.

The word supported matters. The current Work/Codex pricing documentation describes eligible credit-based usage and additional credits after included limits. It is not a rate card for every ordinary ChatGPT conversation. Check the supported activity and rate card for the account you are actually using.

Do not mix these five balances

Balance or limit	What it controls	Where to check it
Work/Codex credits	Eligible paid continuation, separate from included plan capacity.	The Work/Codex usage dashboard; eligible workspace billing where applicable.
Included plan usage	The allowance bundled with Free, Go, Plus, Pro, or another plan; limits vary by plan and feature.	The feature’s usage meter and plan details in your account.
ChatGPT subscription billing	The recurring payment for the plan itself. It governs plan access, not a separate API wallet.	ChatGPT Settings → Billing or the platform that processed the subscription.
OpenAI API prepaid credits	Programmatic API calls made by an API organization, with token/tool/storage charges and separate limits.	API platform billing overview for the organization.
Other wallet, gift or promotion balance, if shown	Only the redemption scope established by that balance’s own offer—not an assumed universal credit.	The offer, receipt and eligible checkout. Verify what it can actually pay for.

A positive balance does not identify its spending scope. For API-key requests, balance, request rate, organization usage limits and enforced spend limits are separate checks. Do not transfer a rule from one row of this table to another.

How included usage and credits are applied

Your plan provides an included allowance for a feature or workflow.
You use that included allowance first.
When a supported feature reaches its included limit, ChatGPT may offer an option to add credits if your account is eligible.
If you confirm and have a positive balance, eligible activity can draw from the shared supported-feature credit balance.
Your subscription remains the same; credits simply provide a paid overflow path for the features they support.

This is why buying credits does not necessarily remove a “message limit” notice in ordinary ChatGPT chat. A limit can belong to a model, plan, tool, workspace, or safety/rate-control system that credits do not cover.

Which ChatGPT features can use credits?

The current documentation explicitly puts ChatGPT Work and Codex on the same usage, credit and limit system. It also describes shared usage with other agentic features once their pricing is effective, currently including ChatGPT for Excel on Plus and Pro. Availability and account permissions still matter. This is not a promise that every ordinary-chat message, model, image or voice session accepts these credits.

If the account does not show Add credits after a supported limit, that may mean the purchase flow has not rolled out to the account, plan, region, or feature. It is not evidence that an API purchase will unlock it.

A worked Work/Codex credit example—not a message allowance

Suppose an eligible task uses GPT-6.1 Sol at Standard speed and records 8,000 uncached input tokens, 2,000 cached input tokens and 1,000 output tokens. This is an invented teaching example, not a HiseHub account test. Using the published Standard credit rates checked October 10:

Component	Example tokens	Credits per million	Calculation
Uncached input	8,000	50	8,000 ÷ 1,000,000 × 50 = 0.400
Cached input	2,000	2.5	2,000 ÷ 1,000,000 × 2.5 = 0.005
Output	1,000	250	1,000 ÷ 1,000,000 × 250 = 0.250
Standard total	10,000 total input; 1,000 output	Different rates by component	0.655 credits

The cached 2,000 tokens are part of the 10,000 input total, not an extra charge on all 10,000 at the uncached rate. For this same hypothetical token mix, eligible purchased-credit Fast usage at 2× would be 1.310 credits; eligible GPT-6.1 Sol Ultrafast at 6× would be 3.930 credits. Do not infer that either speed is available to your plan or workspace.

Do not convert this into “my subscription includes X such tasks.” Included subscription usage uses different speed multipliers: the documentation gives 2.5× for Fast and 8× for the listed Ultrafast modes, versus 2× and 6× for purchased credits. Published credit prices alone do not determine included capacity. Nor is 0.655 credits a US-dollar price: purchase prices and discounts depend on the plan or agreement.

A real task can read conversation history, files and tool results, retrieve more context and produce more output than this example. Repeat runs can change the token mix or cache reuse. For budgeting, record the actual surface, model, speed, visible consumption and task outcome; do not use prompt length or a third-party “messages per month” estimate as a meter.

Where to see your balance and usage

Sign in to the ChatGPT account that owns the balance.
For Work/Codex, open the official usage dashboard. Eligible personal and Business Work users can also see remaining usage in the web sidebar; the Codex CLI supports /status.
Review the credit balance, recent consumption, supported feature, and any rate card or limits shown.
For a connected app using your plan, open ChatGPT Settings → Usage and inspect its app limit. A percentage cap is not a new allowance or a reserved slice. Before any purchase, check the actual offer, payment method and automatic-purchase terms.

If you use multiple logins, check the account identity carefully. A personal account, work account, Apple sign-in, and Google sign-in can look similar while holding separate plans and balances. A balance on one account cannot be assumed to appear on another.

How auto top-up works

If your eligible account offers automatic purchasing, read the terms shown there before switching it on. Verify the trigger, purchase amount or target, billing period, maximum, payment method and whether enabling it can immediately charge you. This review has not established one current universal threshold, reload flow or maximum for every account.

Check which purchases a displayed cap actually covers, including whether manual purchases sit outside it. Do not assume an alert is an enforced spending cap. Keep automatic purchasing off until you understand the eligible activity and can reconcile its usage with a receipt. A spending boundary is not a guaranteed number of tasks.

Leave auto top-up off until you know which feature is using the balance.
If offered, choose a conservative purchase amount and enforced maximum for an unfamiliar workflow.
Recheck the default payment method and recent usage after the first run.
Disable automatic reload when a temporary project is finished.

Credits, API prepaid balance, and service credits

ChatGPT feature credits live in the consumer ChatGPT/Codex usage flow. OpenAI API prepaid credits live in an API organization’s billing overview and are consumed by programmatic requests. OpenAI’s billing guidance says the two products have separate billing systems. API usage can also have token, request, organization, and spend limits even when the prepaid balance is positive.

Read the terms attached to the specific service and offer before purchase. A generic service-credit label is not evidence that funds transfer across products, that a promotion follows a paid pack’s terms, or that every pack has the same expiry. This technical review does not verify current credit-pack refund, expiry or transfer rights.

For API work, use the HiseHub AI API Cost Calculator to model tokens and calls, then open the API organization’s official billing page. For plan selection, the AI Plan Finder and AI Subscription Price Comparison answer different questions from a credit balance.

API 429: credit balance, rate limit or enforced cap?

An HTTP 429 alone does not tell you to recharge. OpenAI’s API error reference distinguishes these cases; inspect error.code even if the broader error.type says insufficient_quota.

Code or symptom	What to verify	Safe next action
`credit_balance_exhausted`	The API organization has no prepaid balance remaining.	Check that organization’s billing and available credits. A ChatGPT top-up is the wrong product.
`slow_down`, or the error identifies request-rate limiting	Traffic rose too quickly or requests arrived too fast.	Reduce request rate and follow `Retry-After` when present. Buying consumer-chat credits does not pace requests.
`organization_spend_limit_exceeded`	The organization’s enforced spending limit was reached.	Have an authorized owner review the limit and budget. Do not remove a spending guardrail blindly.
`project_spend_limit_exceeded`	The project’s enforced spending limit was reached.	Review the correct project’s spend settings; another project’s balance does not identify this cap.
`organization_usage_limit_exceeded`	The organization reached its OpenAI-assigned usage limit.	Review the approved usage limit and support/increase route. Repeated retries do not grant approval.

Keep a useful failure record: API organization/project name, active authentication mode, time with timezone, HTTP status, exact error code and any retry guidance. Redact API keys, tokens, personal data and payment details before sharing it. A balance error needs a billing check; a rate error needs traffic control. Retrying billing, spend or quota errors does not restore access by itself.

Should you buy credits, change plans, or use the API?

Your situation	Start here	Reasoning
You occasionally hit a supported Codex or Excel limit and need to finish now.	Check whether ChatGPT offers credits, then set a small cap.	Credits can be useful as targeted overflow when the feature and account are eligible.
You regularly hit the same included limit.	Compare the next plan tier and the actual monthly overflow.	Credits do not change the plan; repeated top-ups may be harder to budget.
You need ordinary ChatGPT messages or a model that does not show credit eligibility.	Check the plan/model limit and wait for its reset or review plan access.	A credit balance is not a universal message-limit bypass.
You use an external app or build an automation.	Identify API-key, approved plan-backed, or app-credit mode first.	API-key requests use API billing; eligible approved plan-backed requests can use existing Work/Codex capacity. App fees remain a separate check.

Our subscription vs API cost guide helps compare the boundary at a workflow level. The right answer depends on the feature, frequency, account eligibility, and whether you need a finished interface or programmatic control.

Why credits may not work

Unsupported feature: the balance only covers features OpenAI makes eligible for that account.
Plan or rollout difference: purchase availability can vary by plan, account, region, and feature rollout.
Wrong account or workspace: confirm the account and personal/work context that owns the balance.
Separate API limit: an API organization may have a rate, token, monthly, or spend limit unrelated to balance.
Receipt does not match the expected balance: reconcile the purchased product, account and receipt with the relevant usage screen before buying twice or assuming a failed charge.
Automatic purchasing boundary: if offered, inspect the displayed cap, trigger and payment status rather than assuming every low balance must reload.
Connected-app or workspace cap: a plan-backed app’s cap is not extra capacity, and a workspace user limit is not an entitlement grant. Identify the effective restriction.

If credits were consumed because of a confirmed account compromise, use OpenAI’s unauthorized-activity/support route. Do not post a credit claim link, API key, receipt, or account screenshot publicly.

Expiry, refunds, and transfers

Before purchasing, check the expiry date, unused-balance treatment, refund conditions, transfer restrictions and eligible service in the governing offer and receipt. Save that evidence privately. Do not assume a promotion, another product’s prepaid balance or an old screenshot has identical conditions. The October 10 technical review did not verify a current universal 12-month expiry or refund rule, so this guide does not promise either.

Frequently asked questions

Do ChatGPT credits replace Plus or Pro?

No. They are a pay-as-you-go add-on for supported features. Your plan and its included allowance remain separate.

Can credits remove every ChatGPT message limit?

No. Credits currently apply only to eligible features shown for your account. A model, rate, safety, workspace, or plan limit may remain unaffected.

Are ChatGPT credits the same as API credits?

No. OpenAI documents ChatGPT and API as separate billing systems. Check the product and organization shown before adding funds.

Does auto top-up charge my card immediately?

Do not assume enabling automatic purchasing is free of an immediate charge. If offered, read the actual confirmation screen for its trigger, amount and payment timing before enabling it. This review has not verified a universal flow.

Why did my wallet balance not pay for credits?

A balance label alone does not establish redemption rights. Check that offer’s eligible product and payment screen. This review does not verify current wallet-to-credit conversion or gift-balance eligibility.

Official sources

Scope reviewed October 10, 2026: Work/Codex shared usage and published rates, eligible connected-app usage, workspace-control boundaries and API error diagnostics. No paid inference, account allowance, checkout or refund test was performed. Ordinary-chat caps and credit-pack terms are not certified by this review. HiseHub is independent and not affiliated with OpenAI.