Credits, errors and request tracking
Each account receives ten free successful chat requests in total, with up to 500 output tokens per request. API and playground share this allowance across all keys; creating another key does not reset it. Failed generation restores the allowance. Accounts begin with $0.00 credit; after the free allowance is exhausted, requests without sufficient credit return HTTP 402. Payments and automatic billing are not enabled. View remaining free requests in Credits and usage in Usage.
{
"error": {
"type": "insufficient_credit",
"code": "insufficient_credit",
"message": "Your account has insufficient credits."
},
"request_id": "REQUEST_ID"
}
At most two requests may run concurrently per account. The request rate limit is 120 per hour per client address, including API and playground attempts. HTTP 400 means invalid parameters, 429 means a rate or concurrency limit, and 502 means generation failed. Do not automatically retry a generation without checking its outcome.
The actual request_id is also returned in the x-request-id response header. Keep it when contacting support; never share your API key. Handle 401 by checking your key, and 402 by checking your account credit. Do not repeatedly retry either error unchanged.