TokensClubTokensClub documentation
Troubleshooting
Check the address, protocol, key group, complete model ID and balance first, then investigate the error details.
| Error | Check first |
|---|---|
| 400 | Request format and model-supported parameters; reduce to a minimal example. |
| 401 | Whether the key is complete, valid or disabled, and whether the authentication header is correct. |
| 403 | Group, model permissions, IP or other access restrictions. |
| 404 | Repeated paths, an incorrect model ID or an unsupported endpoint. |
| 429 | Request rate, concurrency, quota or upstream limits. |
| 5xx / timeout | Check usage first, then retry a limited number of times after a delay. |
Text works, but tools or multi-turn requests fail
A basic text request does not verify every feature. Record the protocol, model, failure time and request ID, then test the features you need individually.
An HTML response
Confirm that you are calling an API path. An incorrect URL or a proxy verification page may return HTML; do not parse it as JSON.
Information for troubleshooting
Time and timezone:
Client and version:
Model ID / group:
Protocol and endpoint:
HTTP status / error body:
Request ID:
Reproducible:Remove API keys, passwords and private conversation content before sharing diagnostic information.