For AI agents: step-by-step setup guide — /docs/agents.md, documentation index — /llms.txt.

Errors and limits

Rate limits, timeouts, and gateway error codes. For each response, we explain when it occurs and what to do: retry the request or fix it.

The numbers come from the limits field of the GET /v1/capabilities response: values there are always current.

Output length by model#

Without max_tokens, the gateway applies a default: without streaming — shorter, so the response fits within the timeouts; in a stream — the model's cap. max_completion_tokens is the same field.

The error body is an error object with message, type, code, param; not every error has all fields. Rely on the status and type, and check code for details: the message text may change. The Anthropic format is in the Anthropic error format section.

{
  "error": {
    "message": "Model is currently overloaded in the Gonka network",
    "type": "rate_limit_exceeded",
    "code": "upstream_rate_limited"
  }
}

Until the stream is open, a rejection comes as a regular response code — just like without streaming. Once it's open, the status is already 200, and the error arrives like this:

• Chat Completions — a joingonka-error with a error, then a disconnect without [DONE].
• Without streaming after an early response — status 200 and a body with a error.
• Anthropic Messages — an event: error, then the stream closes.
• OpenAI Responses — an response.failed, with the reason in response.error.code.
• Legacy Completions — data: {"error": …}, then [DONE].

data: {"id":"joingonka-error","object":"chat.completion.chunk","model":"MiniMaxAI/MiniMax-M2.7","choices":[],"error":{"message":"Gonka network error","type":"api_error"}}

• POST /v1/messages responds with the Anthropic envelope: {"type": "error", "error": {"type", "message"}}.
• Gateway rejections preserve the type from the table above (insufficient_funds, model_unavailable, and others); there's no code field in this envelope — the reason is in the text.
• Request shape errors — invalid_request_error: no messages or max_tokens, a tool call without a name, unknown model.
• Unknown path — not_found_error, body too large — request_too_large.

event: error
data: {"type":"error","error":{"type":"timeout","message":"Upstream timeout"}}

• After the pause from Retry-After: 429
• With increasing pause — 1, 2, 4 s, and so on: 500, 502, 503 service_unavailable, 504
• With another model: 503 model_unavailable
• Don't retry without changes — fix the request, key, or balance: 400, 401, 402, 403, 404, 413, 415, 501

Every retry after 504 is a new input estimate charge; for long responses, enable stream: true.

If the error keeps happening, contact support and include the x-request-id from the response headers.