Quick answer
Codex documents post-allowance continuation as Additional credits or API-key usage. Plus and Pro can purchase credits, while API-key chats use standard API billing.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| post-allowance continuationPlus and Pro can purchase credits, while API-key chats use standard API billing. | Additional credits or API-key usage | Plan dependent | OpenAIAug 22, 2026 |
Why does this limit matter?
Subscription usage and metered API usage are separate cost paths even when used through the same local interface.
This value is scoped to Plan dependent; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Confirm the billing identity and review the usage dashboard before accepting a metered continuation.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- Credit consumption varies by model, cached input, output, context, tools, images, and speed configuration.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related