OpenAI’s subscription API credits have separate eligibility and expiry rules

OpenAI’s [October 28 changelog](https://developers.openai.com/api/docs/changelog) announces API credits for eligible ChatGPT Pro and Business subscriptions. The [official guide](https://developers.openai.com/api/docs/guides/chatgpt‑api‑credits) requires an active paid subscription at least seven days old, ownership of both the subscription or workspace and receiving API organization, and matching account email addresses. Trials and complimentary subscriptions are excluded. The useful planning record therefore has two sides: the subscription that supplies the benefit and the API organization intended to receive it. An email match alone does not establish ownership of each. A person discussing the benefit with a workspace administrator can identify which role is missing before treating the subscription as an application’s available balance. That distinction matters when a person belongs to more than one organization. A subscription name, an account identity and a receiving organization are different pieces of information. Treating them as interchangeable can make a budget discussion look settled while the destination remains unclear. This article explains the documented conditions; it does not determine any reader’s account eligibility.

The [guide](https://developers.openai.com/api/docs/guides/chatgpt‑api‑credits) says the initial grant is prorated and unused credits expire without rollover. Monthly grants expire with that billing cycle; annually prepaid Business receives a yearly issuance expiring with its annual cycle. For an application plan, the amount and the time available to use it answer different questions. An expiry date can limit a project even when a headline allowance sounds sufficient. A planning note can distinguish the intended work, its estimate and the grant’s actual validity period rather than divide an advertised monthly amount into an assumed permanent daily budget. The annual Business exception also makes a generic “resets next month” assumption unreliable. The relevant record is the actual subscription cycle and grant, not the calendar month in which someone first read about the offer. This is a bounded explanation of eligibility, expiry and exclusions, rather than a complete guide to every amount, subscription change or billing condition.

The [benefit](https://developers.openai.com/api/docs/guides/chatgpt‑api‑credits) excludes API‑key Codex usage and does not increase ChatGPT or signed‑in Codex limits. A team should therefore name the usage route before asking whether the benefit covers its work. The same product name in two workflows does not establish the same billing treatment. A description of the intended application and its billing organization is more useful than a general request for additional AI capacity. OpenTools read the public documentation. It did not inspect an account, activate a benefit, create a key, make an API request or change a payment setting. The new benefit is documented product availability, not evidence that a particular account received credits or gained subscription headroom. Archival photograph of 1515 Third Street in San Francisco, June 15, 2025, identified by the photographer as OpenAI’s headquarters at that time. It provides company context, not evidence of an API credit balance, account eligibility or a billing setting. Photo: [Coolcaesar / Wikimedia Commons](https://commons.wikimedia.org/wiki/File:1515_Third_Street.jpg), [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Cropped for display.