Troubleshooting

Diagnose in thirty seconds

Before digging into your tool, check that the key and the API respond, with nothing in between:

Is the key valid?
Fenêtre de terminal
```
curl -sS -o /dev/null -w "%{http_code}\n" https://api.kloria.dev/v1/models \
  -H "Authorization: Bearer $KLORIA_API_KEY"
```
200: the key is fine, the problem is in the tool’s configuration. 401: the problem is the key.

Does the model respond?

curl -sS https://api.kloria.dev/v1/chat/completions \
  -H "Authorization: Bearer $KLORIA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model": "claude-sonnet-5", "max_tokens": 5, "messages": [{"role": "user", "content": "."}]}'

A response with choices: everything works on Kloria’s side. An error: its message tells you why (see below).

Does the request show up in the console?

Open Usage Logs. If your tool’s requests aren’t there, they’re not reaching Kloria: check the configured address.

Common error messages

“Invalid token” or “Token not provided” (401)

The key is missing from the request, mistyped, disabled or expired.

Check that it starts with sk- and has no space or line break around it.
Check the header: Authorization: Bearer sk-… (with the word Bearer and a space), or x-api-key: sk-… in Anthropic format.
In the console, under API Keys, check that the key is enabled and not expired.
Is it really a Kloria key, created in your console? A key from another service won’t work.

“Insufficient user quota” or a message about quota (403)

Your balance is used up, or the key reached its own quota. Check Wallet for the balance, and the key’s quota under API Keys. See Credits and billing.

“This token has no access to model…” (403)

The key has model limits that don’t include the one requested. Edit the key, or use another one.

“No available channel for model X under group Y”

The requested model doesn’t exist under that name, or it’s temporarily unavailable.

Check the exact ID on Models and pricing: claude-sonnet-5, not Claude Sonnet 5 or claude-sonnet-5-0.
With Claude Code, this message for a Haiku model means ANTHROPIC_DEFAULT_HAIKU_MODEL isn’t set (see Claude Code).
If the ID is correct and the error persists, the model may be unavailable: retry in a few minutes, then report it.

“Model … has not been priced” or “price not configured”

The model isn’t open on Kloria yet. Use a model from the list and tell us which one you’d like.

400 error mentioning `anthropic-beta`, `context_management` or “Extra inputs are not permitted”

Your tool sends experimental features the model doesn’t accept. For Claude Code, add CLAUDE_CODE_DISABLE_EXPERIMENTAL_BETAS = 1 to the env block of the settings.

429, 500, 502 or 503 error

Overload or temporary incident on the model’s side. Retry with increasing delays. If it lasts more than a few minutes, report it.

Configuration issues

Symptom	Likely cause
404 on every request	Malformed address: `/v1` twice (`…/v1/v1/…`) or missing. OpenAI format: `https://api.kloria.dev/v1`. Anthropic format: `https://api.kloria.dev`.
HTML response instead of JSON	The tool calls `app.kloria.dev` (the console) instead of `api.kloria.dev`.
The tool asks you to sign in to its own account	The gateway configuration isn’t read. See the tool’s page.
Works in one terminal, not another	The environment variable only exists in the first one. Make it permanent (see Quickstart).
Streaming arrives all at once at the end	A corporate proxy or antivirus buffers the response. Test from another network.

Reporting an issue

Write to contact@kloria.dev with:

the approximate time of the request and the model used;
the HTTP status and error message;
the tool and its version, if the error comes from a tool.