Frequently asked questions

Check the following: 1) the Authorization Header format (include one space after Bearer before the API Key); 2) whether the API Key has expired or someone deleted it; and 3) whether you are using an API Key from the correct workspace.

HTTP 429 means the request was rate limited. Follow Retry-After in the response and retry with exponential backoff. To request a higher limit, contact support or an administrator.

Open the console’s “Usage Logs” page. Filter by time, model, and API Key to view detailed consumption records and charges for each call.

Balance is the workspace's available funds for API requests. HTTP 402 uniformly indicates available balance or insufficient quota to the outside world. Top-ups increase the balance but do not automatically increase the quota; the balance is not a subscription plan.

Quota is the maximum amount currently available to an account. Balance is available funds, while quota is available allowance; they are independent. Contact support or an administrator to request a limit adjustment.

HTTP 402 indicates insufficient available balance or quota. Please confirm the balance and upper limit on the bill, API Key and workspace usage pages; recharging can only increase the balance and cannot automatically increase the quota. After confirming that both are sufficient, check that the model is available and that the request uses the correct workspace.

Confirm that the API Key for this request belongs to the adjusted workspace, and check whether someone disabled the Key, it has expired, or it has a lower individual quota. Usage and balance can take a moment to synchronize. If console status has updated but requests still fail, contact support with the request time, a redacted Key identifier, and the request ID; do not send the full API Key.

502 and 504 are gateway-layer errors. A 502 usually means the gateway received an invalid response from, or failed to connect to, the upstream provider; a 504 means the upstream provider or the gateway’s waiting path timed out. The status alone cannot identify whether the fault is upstream or inside Token Market, so use the request ID, routed provider, and error reason in request logs to investigate. For safe-to-retry requests, use jittered exponential backoff and consider enabling fallbacks or broadening filters. Do not blindly replay streaming or non-idempotent generations because you could be charged or generate duplicate output. If the problem persists, contact support with the request time, model, provider, and request ID.

Submit a support ticket through the “Feedback” option in the lower-right corner of the console, or email support@tokensmarket.ai.