FAQ and Troubleshooting

Use a fixed diagnostic order and keep the HTTP status code and a redacted response body. Change one variable at a time so you can identify which change resolves the issue.

Diagnostic order

1. Confirm the API base URL came from the console and contains no duplicated path.
2. Confirm the API key is active, has no surrounding whitespace, and has the required permissions.
3. Confirm the model identifier matches the marketplace and remains available.
4. Validate the JSON, message structure, and protocol-specific parameters.
5. Confirm the account has available balance or quota.
6. Check the local network, proxy, firewall, and platform status.

Common failures

400: invalid request

Check that the JSON is valid, field types are correct, messages is an array, and the selected model supports every supplied parameter.

401 / 403: authentication or permission failure

Verify the API Key, Bearer authentication format, and key permissions. Never send a complete key in a support request.

404 or model not found

Check the endpoint path and model identifier. Return to the marketplace to confirm current availability and copy the name instead of retyping it.

429: too many requests

Reduce concurrency and request frequency, then use exponential backoff. Also check account quota and platform limits.

5xx or network timeout

Retry later, reduce context and output size, and check the network. Avoid unlimited immediate retries, which can amplify an outage and increase cost.

Insufficient balance or quota

Review balance, quota, billing status, and recent usage in the console. Add capacity or select a lower-cost model only after confirming the cause.

The client connects but shows no content

Disable streaming for a test. If non-streaming requests work, update the client or review its SSE handling.

Information to include in a support request

• Time of the failure and time zone.
• Endpoint path and model name.
• HTTP status code and redacted response body.
• Client name, version, and operating system.
• Whether streaming was enabled.
• A minimal reproduction with the API key, personal information, and business data removed.

Never share

A complete API key, password, payment information, or unredacted private content.