Request is unauthorized

Symptoms

A client receives an authorization error, an API key is rejected, or a request fails before model processing.

Check

1. Confirm the request is sent to the intended Desktop or Server instance.
2. Check that the client is using a current Stravia API key, not a setup claim token or upstream provider key.
3. Verify the key is enabled and its allowed-model scope includes the requested model.
4. If the key is for MCP, distinguish /mcp API-key authentication from the separate MCP tool-access gate.
5. If the request is accepted but the upstream service rejects it, investigate provider credentials instead.

Resolution

Use an enabled key with the required model scope, or issue a replacement key and update the client securely. Do not widen a key to all models unless that access is intended. Rotate any key that has been exposed.

Escalate if still stuck

Record the endpoint, protocol, requested model, and response status without including any key or credential. See API keys , MCP , or Diagnostics .