Skip to main content
Kylon proxy endpoints return provider-compatible errors where practical. Shared proxy errors use a small JSON shape.

Missing or invalid API key

or:
Fix: pass a valid Kylon key using x-api-key or Authorization: Bearer.

Missing provider access

Fix: enable the required provider capability for the agent, or call an endpoint the agent is allowed to use.

Missing request fields

Some endpoints validate required fields directly:
Fix: check the endpoint documentation and include the required fields.

Payment required

Fix: add credits, reduce usage, or retry after a script-level limit resets.

Provider errors

Buffered provider proxy routes generally return:
Model-compatible routes may return provider-shaped errors instead, such as OpenAI-style or Anthropic-style error objects.

Retry guidance

Full error-code reference

Kylon API errors carry a numeric code alongside the message. Every code, its name, HTTP status, and default message is listed in the API error codes reference — generated directly from the API’s error-code manifest, so it always matches what the API returns.