Troubleshooting

Fix the most common FluxRouter problems fast: an agent that won't connect, error codes including 402, latency, truncated output, and each ability from speech to apps.

Something not working? Most problems fall into a handful of buckets, and almost all of them clear after four quick checks.

What to check first

  1. The base URL matches the protocol. OpenAI-compatible tools use https://api.fluxrouter.ai/v1. Anthropic-compatible tools, such as Claude Code, use https://api.fluxrouter.ai/anthropic with no /v1. There is no bare /chat path.
  2. The key is your Flux key. It starts with sk-. Send it as Authorization: Bearer sk-... (the Anthropic path also accepts x-api-key: sk-...). A leftover OpenAI or Anthropic key returns 401.
  3. The model is real. Use flux-auto or another flux-* id. See Models.
  4. Keep the X-Flux-Request-Id. Every response carries one. Include it when you ask for help so support can find your exact request.

Pages in this section

Abilities

Every ability error code is in the error reference for every endpoint and tool.

To see which model answered a request and what it cost, read Receipts.

Still stuck?

Grab the X-Flux-Request-Id from the failing response, note the base URL and model id you used, and email support at fluxrouter dot ai. Those three details resolve most questions on the first reply.