OpenAI Adds Monthly API Credits for ChatGPT Subscribers
Learn how eligible ChatGPT Pro and Business subscribers can claim up to $500 per month in OpenAI API credits, manage limits, and handle billing cycles.
- OpenAI announced on 2026-10-28 that eligible ChatGPT Pro and Business users can claim up to $500 per month in free API credits.
- Pro users receive $100, $200, or $500 per month depending on tier, while Business workspaces receive $20 or $100 per paid seat up to a monthly $500 pooled ceiling.
- Grants do not roll over between billing cycles, and accounts must be at least seven days old under identical email addresses to qualify.
- Credit coverage includes text, agents, tool calls, voice, and structured decisions, but excludes Codex usage through API keys.
OpenAI Links ChatGPT Subscriptions to API Credits
On 2026-10-28, an update in the OpenAI API changelog introduced a subscription perk connecting consumer and enterprise ChatGPT tiers to developer billing. Eligible ChatGPT Pro and Business plan owners can now link their accounts to claim monthly API credits worth up to $500.
Historically, ChatGPT subscriptions and developer platform usage were billed completely separately. Developers paying for high-tier interactive ChatGPT access still needed to maintain a separate prefunded credit balance or credit card on the developer dashboard. Under the guidelines in API credits for ChatGPT subscribers, developers no longer need an active API payment method on file as long as their granted credits remain positive.
The monthly credits apply directly against usage accrued by the linked API organization. Unused allocations do not carry over to future cycles; they expire whenever the current ChatGPT subscription billing cycle concludes. To calculate how these amounts map to tokens across production workloads, consult the /tools/llm-api-cost-calculator/.
Credit Allowances Across Pro and Business Tiers
Credit sizes are determined strictly by the subscription tier or seat type held in ChatGPT. Pro accounts receive a fixed credit amount per month, whereas Business accounts accumulate credits calculated on an individual seat basis.
| ChatGPT subscription | Monthly API credits (USD) |
|---|---|
| Pro ($100 tier) | $100 |
| Pro ($200 tier) | $200 |
| Pro ($500 tier) | $500 |
| Business Standard | $20 per paid Standard seat |
| Business Premium | $100 per paid Premium seat |
For Business workspaces, monthly API credits are pooled across the workspace and subject to a hard ceiling of $500 per workspace per month. For example, five Business Premium seats reach the monthly $500 limit. If an organization pays annually upfront for a Business workspace, OpenAI issues the complete twelve-month total at once, which expires at the end of the annual cycle and is capped at $6,000 per annual billing cycle.
When an eligible subscriber activates the perk midway through a billing month, the initial credit grant is prorated according to the days remaining in that subscription period. Subsequent monthly disbursements arrive automatically upon plan renewal.
Account Eligibility Criteria and Activation Workflow
OpenAI enforces strict qualification requirements before an account can claim monthly grants. Subscriptions must meet three baseline criteria:
- The subscription must be an active, paid Pro or Business plan that has been active for at least seven days. Promotional plans, free tiers, and complimentary accounts do not qualify.
- The individual activating the perk must be an owner of both the ChatGPT plan (or Business workspace) and the destination API organization.
- The ChatGPT user profile and the API platform profile must share the identical email address.
Linking can be performed either from the ChatGPT interface or inside the developer portal. Developers starting with a brand-new API profile can connect their subscription to their default Personal API Organization.
- Via ChatGPT: Log in to ChatGPT. Pro users navigate to Settings → Billing, while workspace administrators open the Admin Console or workspace billing settings. Select the API credit option, pick the target API organization, and confirm.
- Via API Platform: Sign in to the API Platform, navigate to Billing, locate the API credit promotion, pick the matching ChatGPT account or workspace, and complete verification.
Once confirmed, the credit balance appears in the API Platform billing settings overview. Developers can monitor consumption by inspecting the Usage dashboard.
Covered Endpoints, Sandbox Workloads, and Exclusions
The granted credit balance applies across standard API usage billed to the linked organization. It offsets charges across foundational endpoints and hosted features:
- Text and multimodal calls via the Responses API.
- Agent orchestrations through the Agents API, encompassing OpenAI-hosted sandbox execution charges.
- High-reliability evaluations executed through the Decisions API.
- Real-time voice and audio sessions powered by GPT-Live and the Realtime API.
- Visual assets generated through the Images API.
- OpenAI built-in tools along with related compute and storage, including Code Interpreter, web search, and file search.
Important boundaries exist regarding developer access and consumer products. API key calls targeting Codex are explicitly excluded from this credit allowance. Furthermore, free developer credits do not raise rate caps on ChatGPT or signed-in Codex interfaces. Standard infrastructure throughput restrictions documented in API rate limits and /posts/rate-limits-and-usage-tiers-at-anthropic-openai-and-google/ still govern the API organization.
Credit Drawdown, Exhaustion Errors, and Plan Transitions
The platform drains complimentary API credits before tapping into purchased balances. Understanding exhaustion rules avoids unexpected operational downtime in automated workloads.
| Organization balance | What happens |
|---|---|
| Purchased API credits remain | API usage continues using your purchased credits. |
| No credits remain | API requests fail with HTTP 429 and error code credit_balance_exhausted. |
When the credit pool reaches zero and no paid credits exist, endpoints immediately return HTTP status code 429 with the error string credit_balance_exhausted. Teams seeking continuous uptime must configure Auto Recharge or manually purchase credits in organization billing settings. For guardrails on preventing automated runaways, review /posts/per-run-cost-cap-for-llm-api-calls/.
Subscription modifications also influence credit delivery. Elevating a Pro tier issues supplementary prorated credits up to the $500 monthly limit. Adding paid seats to Business plans generates additional prorated funds, keeping within the $500 monthly or $6,000 annual workspace ceilings. In contrast, seat removals take effect on the subsequent billing date, and reallocating an active seat to a different teammate produces no extra balance.
Canceling a paid subscription stops future recurring grants, but credits already distributed remain usable until their scheduled cycle expiration. Downgrading to unsupported plans like Plus, Go, or Free unlinks the organization when the cycle terminates. Similarly, transitions to ChatGPT Enterprise dismantle the connection at billing cycle close because Enterprise remains ineligible. Upgrading from Pro to Business severs the Pro connection; owners must wait until the Business workspace passes the mandatory seven days before initiating a new link. To redirect credits to an alternative organization, developers must submit a request to support.
Implementation and Billing Governance Checklist
Before depending on subscription-funded allowances for production tasks, verify account readiness against this checklist:
- Confirm the ChatGPT subscription has reached at least seven days of continuous paid status on an eligible Pro or Business tier.
- Verify that identical email credentials administer both the ChatGPT subscription and the target API organization.
- Inspect organizational quotas under the organization limits panel to ensure assigned rate limits match throughput targets.
- Determine whether background services require secondary paid credits with Auto Recharge to avoid HTTP 429 errors when monthly allotments run dry.
- Configure application API keys specifically beneath the linked organization ID, ensuring all client calls draw against the intended credit bucket.
Developers wanting to experiment with new prompts using these credits can open the Responses playground, test reasoning on the Decisions playground, build workflows in the Agents workspace, or connect the OpenAI Developers Plugin inside ChatGPT.