Free LLM API errors · OpenRouter · checked 2026-11-13
OpenRouter 401 "User not found": fix
HTTP 401 · User not foundOpenRouter does not recognise the account behind your API key: the key was deleted or disabled, or the account or workspace it belonged to no longer exists.
Our own router has received this error from OpenRouter in production.
Why it happens
- The key was deleted or disabled in the OpenRouter dashboard.
- The key belonged to an account or workspace that was removed or reorganised. We saw every key of one account fail this way at once; a new key fixed it.
How to fix it
- Open openrouter.ai/settings/keys and check the key is still listed and enabled.
- Create a new key and replace it wherever it is set (environment variables, then redeploy).
- Do not retry: this error does not clear by itself.
- If you run a fallback chain, treat it as a key problem, not a model problem: otherwise every model gets marked as broken.
Questions
- My OpenRouter key worked yesterday. Why "User not found" today?
- The key or the account behind it changed. Check the key in your dashboard and create a new one if it is gone or disabled.
Sources
Read on 2026-11-13. Providers change limits and messages often; the linked pages are what applies.
Limits and fine print of OpenRouter's free tier: OpenRouter free API. Tired of handling these by hand? ZeroLimitAI is one OpenAI-compatible endpoint that moves to the next free model when one of these comes back, and can run on your own Groq or OpenRouter key.