ChatGPT Pro and Business Subscribers Can Claim Up to $500 in API Credits
OpenAI is adding monthly API credits to eligible ChatGPT Pro and Business subscriptions, but the benefit funds API use rather than providing a separate app-building environment. In a demonstration, developer Romain Huet shows how a subscriber can link credits to an API organization and use them to power features in an app; the allowance ranges from $20 per paid Business Standard seat to $500 per month, depending on plan and workspace limits.
The subscription benefit is API credit, not a separate building environment
Eligible ChatGPT Pro and Business subscribers can claim monthly credits for use across the OpenAI platform. The amount depends on the plan: Pro subscribers receive $100, $200 or $500 per month; Business subscribers receive $20 per paid Standard seat or $100 per paid Premium seat, with credits pooled across the workspace up to $500.†
The practical implication is that the benefit is attached to an API organization, where a developer can use it for API projects. In Romain Huet, the claim screen shows a Pro plan with $200 in monthly credits and offers to add them to a Personal API Organization. After linking, the confirmation says the credits will appear in that organization once processing is complete. The organization can be renamed.
To claim the credits, subscribers go to Billing in the ChatGPT app and link an API organization. That step connects the subscription benefit to the place where API work is managed; it does not, by itself, create an application or determine how the credits will be used.
The organization and project key connect the benefit to an app
Once an API organization is linked, a project can be configured to make API calls. Huet’s example uses Codex and the OpenAI Developers plugin to create an API key for a small Mac writing app. Codex asks which organization to use, then helps set up a key for the app. The setup screen identifies the organization, project and key expiration, and explains where the key will be created.
That distinction matters for understanding what a subscriber is claiming: credits are added to an API organization, while an application uses an API key configured for its project. The developer dashboard shown in the demo brings these tasks together with quick actions to create a key, build an agent or explore app ideas. It also displays API usage and a credits balance.
The allowance can support API features inside a working tool
Huet’s app checks writing as the user types, wherever they are working. He describes using the Decisions API to assess whether a message is ready to send, needs a small adjustment or needs a more substantial rewrite. For suggested edits, he uses the Responses API and a model he describes as suited to writing and cost-efficient.
In the demonstrated workflow, a message about hot-dog app icons—“Neon is cool corners are distracting make those less”—receives a suggestion: “Neon is cool, but the corners are distracting. Could you make them less prominent?” The user can insert that edit in the chat where the draft was written. Huet also shows a more pointed draft being softened from “As I already said, this approach won't work” to “As I already said, this approach won't work. Please review the requirements before sending this over again.”
The example makes the credit benefit concrete: API calls can power a feature within a tool, rather than being used only through a standalone chat interface. Huet says the app runs on the credits included with his subscription. The monthly amount available for a particular build depends on the subscriber’s plan, and for Business it depends on paid seat types and the workspace cap.