#Is it possible that my agent can't access OpenRouter API?

1 messages · Page 1 of 1 (latest)

tropic ridge
#

I keep getting this message:

⚠️ Agent couldn't generate a response. Please try again.

I do have credits on my account and pasted a valid API key during onboard though.

worthy martenBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

frail sandalBOT
elder sandBOT
#

Let me check the exact docs sections that cover missing provider auth and OpenRouter setup, then I’ll give them a concrete checklist.

#

I found the relevant docs. This error string is unfortunately generic, so the next step is to get the real provider error out of the gateway logs.

#

Yep, possible, but that banner by itself is too generic to prove it’s OpenRouter.

OpenClaw uses that exact message as a catch-all when the run fails, so the real clue is in the gateway logs.

Please run these on the machine running openclaw gateway and paste the output here, minus secrets:

openclaw --version
openclaw models status
openclaw models status --probe
openclaw logs --follow

Then, while logs --follow is running, send the agent one more message and copy the error lines.

The most common causes here are:

#

  1. The gateway can’t actually see your OpenRouter key

    • especially if you onboarded on one machine, but the gateway runs on another
    • for daemon setups, put it on the gateway host, usually in ~/.openclaw/.env

  2. You created a new agent

    • auth is per-agent
    • docs call out that a new agent can have an empty auth store:
      ~/.openclaw/agents/<agentId>/agent/auth-profiles.json

  3. Fallback switched to another provider

    • for example Google or Anthropic, and that provider is missing auth
    • openclaw models status --probe usually reveals this fast

Relevant docs: