Short answer
A visible balance does not guarantee that a specific request satisfies the model, token-group, permission, and estimated-cost requirements. Start with the actual error in call logs, then check the balance, token group, current model price, input size, endpoint, and upstream status. Prices, billing units, available models, and credit rules may change. Use the current console and call log as the source of truth. This page was last verified on September 2, 2026.Troubleshooting sequence
1. Record the actual error
Do not diagnose from a generic “insufficient balance” client message alone. Record:- request time and time zone;
- model ID and endpoint;
- API key group;
- HTTP status and platform error;
- whether the request produced usage or a charge.
2. Confirm current pricing and billing unit
Open the console pricing page and confirm whether the target model is billed by token, request, image, video duration, or another unit. Do not use an upstream provider’s price or an old static documentation table to predict the charge.3. Reduce input size
Long context, multiple images, large files, PDFs, videos, or a large output limit may increase estimated usage. Retry with a minimal input:- keep one short message;
- temporarily remove images, files, and tool calls;
- use an explicit, smaller output limit;
- keep other variables unchanged so the result is diagnostic.
4. Check group, permission, and endpoint
The same model name may use different routes depending on the API key group, billing type, or endpoint. Confirm that:- the key permits the target model and billing mode;
- the endpoint matches the current documentation;
- the model ID is exact;
- the account does not require a permission adjustment from the site owner or support.
5. Separate platform and upstream errors
If a minimal request still fails, check for rate limits, safety blocks, upstream unavailability, timeouts, or temporary routing problems. Do not retry indefinitely. Fix parameters, permissions, or balance for non-retryable errors; use bounded retries and backoff for temporary errors.What to provide to support
- account email or username;
- request time and time zone;
- model ID, endpoint, and API key group;
- redacted error and request identifier;
- screenshots of the console balance and pricing page;
- result of a minimal reproduction.