Check allowance and usage before a long Codex task
Review your balance, subscription status, and recent usage before starting continuous project work.
· GetToken
Before a long Codex session, confirm the active account and its source of usage allowance. A short check helps distinguish allowance problems from configuration errors and task issues.
Confirm the active connection
Check the account and connection selected in GetTokenSwitch. A Codex official account and a GetToken API Key use different allowance sources. Web mirror services also have separate rules. A completed purchase alone does not establish that the current tool can use it.
This workflow applies to GetToken API Keys. Open the console and review the balance and subscription status shown for the account.
Review balance and subscription
Balance top-ups pay for actual usage, and topped-up allowance does not expire with a subscription cycle. Subscription plans have their own cycles and allowance windows. Check the current rules on the pricing page before purchasing, and use the console for available amounts.
If you have paid but cannot use the service, open orders and review payment and delivery status. A confirmed payment, an active subscription, and a successful tool request are separate results to check.
For a scheduled subscription, check when it can activate. Do not count pending allowance as available for the current task.
Run one representative small task
Choose a small task similar to the upcoming work, such as reading one module and suggesting a change. Record the time and model, then review consumption on the usage page.
One request gives you a concrete observation, not a fixed cost estimate for a long session. Context length, model choice, and repeated revisions affect consumption. Split a long task into stages, checking results and usage between them.
Investigate interruptions in order
- Save the full error and time
- Check that the active account is still the one you intended
- Review the balance, active subscription, and available allowance
- Confirm that the API Key and model configuration have not changed
- Consult troubleshooting before deciding to retry
Avoid repeatedly resubmitting the entire task. Check whether the previous attempt changed files or consumed allowance, then continue from a clear checkpoint.
For help, share a redacted error and timestamp through support. Keep API Keys, login credentials, and private project context out of the report.