#Error

1 messages · Page 1 of 1 (latest)

uncut laurel
#

HTTP 401: authentication_error: login fail: Please carry the API secret key in the 'Authorization' field of the request header (request_id: 05e19b8c1fe16a5ad80e02aa2f46c7fe)

This happend after i asked my bot to update the agent IDs

burnt cometBOT
#

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

desert mossBOT
#

That 401 isn’t really about “agent IDs” — it means the model provider request went out without an API key in the Authorization header (or the key isn’t being loaded by the Gateway daemon).

Most common causes after changing agents/IDs:

  • You switched to a different agent/profile that doesn’t have auth set up yet
  • Your API key is only in your interactive shell (export ...) but the Gateway runs as a service and can’t see it anymore

What I’d do next (and paste outputs here — redact keys):

  1. Version first:
openclaw --version
  1. Check what provider/model OpenClaw is trying to use + whether it sees creds:
# 
openclaw models status
openclaw doctor
  1. If you’re running the gateway as a daemon/service, put the key where the daemon can read it (example for Anthropic):
cat >> ~/.openclaw/.env <<'EOF'
ANTHROPIC_API_KEY=...
EOF

openclaw gateway restart
openclaw models status

Docs: https://docs.openclaw.ai/gateway/authentication

#

If you paste openclaw models status + the relevant lines from openclaw logs --follow around the error, I can tell you exactly which provider is missing the key and the cleanest fix.

uncut laurel
#

🦞 OpenClaw 2026.2.14 (c1feda1) — If you can describe it, I can probably automate it—or at least make it funnier.

Config : ~/.openclaw/openclaw.json
Agent dir : ~/.openclaw/agents/main/agent
Default : minimax-portal/MiniMax-M2.5
Fallbacks (0) : -
Image model : -
Image fallbacks (0): -
Aliases (3) : GLM -> zai/glm-5, minimax-m2.1 -> minimax-portal/MiniMax-M2.1, minimax-m2.5 -> minimax-portal/MiniMax-M2.5
Configured models (3): zai/glm-5, minimax-portal/MiniMax-M2.1, minimax-portal/MiniMax-M2.5

Auth overview
Auth store : ~/.openclaw/agents/main/agent/auth-profiles.json
Shell env : off
Providers w/ OAuth/tokens (0): -

  • minimax-portal effective=models.json:minimax-oauth | models.json=minimax-oauth | source=models.json: ~/.openclaw/agents/main/agent/models.json

OAuth/token status

  • none
desert mossBOT
#

Your openclaw --version output basically explains the 401:

  • Your default model is minimax-portal/MiniMax-M2.5
  • Auth says “OAuth/token status: none”
  • Yet minimax-portal is trying to use models.json:minimax-oauth

So OpenClaw is calling MiniMax without any token/API key loaded, and MiniMax returns HTTP 401 … carry the API secret key in Authorization header.

Fix (MiniMax OAuth / Coding Plan route)

Run this on the machine hosting openclaw gateway:

openclaw plugins enable minimax-portal-auth
openclaw gateway restart
openclaw onboard --auth-choice minimax-portal
openclaw models status
#

After onboarding, openclaw models status should no longer show OAuth/token status - none.

Docs: https://docs.openclaw.ai/providers/minimax

Alternative (API key route instead of OAuth)

If you want API key auth (not the portal OAuth), run:

openclaw configure

Then choose Model/auth → MiniMax and enter MINIMAX_API_KEY (it’ll write it for daemon use).

If it still errors

Paste (redacting secrets):