API key is invalid

[Shiroyasha101]

openrouter api key shows invalid

[vishalhabib99]

OmniRoute's key test for OpenRouter calls OpenRouter's authenticated key-info endpoint, GET https://openrouter.ai/api/v1/auth/key (testKeyModelsUrl in open-sse/config/providers/registry/openrouter/index.ts). 200 means valid, 401 means invalid. It deliberately doesn't use /models any more, because that endpoint is public and used to accept any key (#11226). So "invalid" means OpenRouter itself rejected the key from the machine OmniRoute runs on.

Run the same check yourself on that machine:

curl -s -o /dev/null -w "%{http_code}\n" \
  -H "Authorization: Bearer sk-or-v1-YOUR_KEY" \
  https://openrouter.ai/api/v1/auth/key

• 401 from curl too: the key itself is the problem. The usual causes are a space or newline copied along with the key (paste it into a plain text editor first, since it should be one line starting with sk-or-v1-), a key that was deleted or disabled under openrouter.ai/settings/keys, or pasting something other than an API key. Creating a fresh key and pasting it again usually fixes it.
• 200 from curl, but OmniRoute still says invalid: then it's on the OmniRoute side, for example a proxy setting, the request not reaching openrouter.ai from the container, or the key being saved with extra characters. In that case, reply with your OmniRoute version, how you run it (Docker or npm), and the server log line from when you click test, so the maintainers can follow up.

[Shiroyasha101]

3.8.51
windows
Failed to load external module playwright-core: Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'playwright-core' imported from C:\Program Files\OmniRoute\resources\app\.build\next\server\chunks\[turbopack]_runtime.js\nError

[vishalhabib99]

Thanks for the details. That playwright-core line isn't what's rejecting your key. The desktop build ships without the browser-automation packages (playwright / playwright-core are an optional "browser-runtime" pack, see open-sse/utils/optionalPacks.ts). They're only used by the browser-based web providers, and the OpenRouter key test doesn't touch them. So you can ignore that log line for this problem.

On the key itself: the test shows "Invalid API key" only when OpenRouter answers the check with 401 or 403 (src/lib/providers/validation/openaiFormat.ts). If the request couldn't reach OpenRouter at all, you'd see a different error. So OpenRouter is actively refusing the key that OmniRoute sends.

To tell whether it's the key or OmniRoute, run this in PowerShell on the same Windows machine (use curl.exe, not curl, which is a PowerShell alias):

curl.exe -s -o NUL -w "%{http_code}`n" -H "Authorization: Bearer sk-or-v1-YOUR_KEY" https://openrouter.ai/api/v1/auth/key

• 401 or 403: OpenRouter rejects the key itself. Create a new key at openrouter.ai/settings/keys and paste it into OmniRoute straight from the copy button. It should be one line starting with sk-or-v1-, with no spaces before or after it.
• 200: the key is fine, and OmniRoute is sending something different. Delete the OpenRouter connection, add it again with the same key, and test again. Also check whether you set a custom base URL or a proxy for that connection. If it still fails, post the 200 result here together with the log lines from the moment you click Test (not the playwright one), so the maintainers can see what OmniRoute is actually sending.

[diegosouzapw]

@Shiroyasha101 Did the curl check from @vishalhabib99's reply settle it? If OpenRouter returns 401 to that request too, a new key fixes it; if it returns 200 and OmniRoute still says invalid, post the result here. Otherwise I'll close this in 7 days for inactivity.