OpenClaw

Set up OpenClaw on this machine to use RouterPlex, an OpenAI- and Anthropic-compatible AI gateway. Keep working until a real request from OpenClaw succeeds through RouterPlex.
 
My RouterPlex API key: YOUR_ROUTERPLEX_API_KEY
 
Key handling:
- If the key line above is a placeholder rather than a real key (real keys start with sk-), use my ROUTERPLEX_API_KEY environment variable. If that is empty too, ask me for the key once, then continue.
- Store the key only in user-level config or my user environment. Never put it in a project file, never commit it, and do not repeat the full key in your replies.
 
Full guide: https://docs.routerplex.com/openclaw
 
Step 1. Prove the key and the RouterPlex gateway work before changing anything else. Run:
   curl -sS https://api.routerplex.com/v1/chat/completions -H "Authorization: Bearer YOUR_ROUTERPLEX_API_KEY" -H "Content-Type: application/json" -d '{"model":"claude-sonnet-4-6","max_tokens":32,"messages":[{"role":"user","content":"Reply with exactly: RouterPlex connected."}]}'
   On Windows PowerShell, use curl.exe with the body in a file, or Invoke-RestMethod.
   - A reply containing "RouterPlex connected.": go on.
   - 401: the key is wrong or revoked. Stop and ask me for a correct key.
   - 402: my balance or trial credit is used up. 403: this key reached its own spending limit. Stop and tell me; retrying cannot fix these.
   - Network, DNS, TLS, or proxy errors: find and fix the cause (proxy variables, VPN, firewall, system clock, outdated CA certificates), then run it again.
 
Step 2. Configure OpenClaw:
   - Run openclaw --version. If OpenClaw is missing, install it with the official installer and run openclaw onboard --install-daemon. It needs Node 24.16+ or 26.1+.
   - Merge this into ~/.openclaw/openclaw.json (Windows: %USERPROFILE%\.openclaw\openclaw.json). Keep my existing Gateway authentication, channels, agents, and providers:
 
{
  "gateway": {
    "mode": "local",
    "bind": "loopback"
  },
  "models": {
    "providers": {
      "routerplex": {
        "baseUrl": "https://api.routerplex.com/v1",
        "apiKey": "${ROUTERPLEX_API_KEY}",
        "api": "openai-completions",
        "models": [
          {
            "id": "claude-sonnet-4-6",
            "name": "claude-sonnet-4-6"
          }
        ]
      }
    }
  },
  "agents": {
    "defaults": {
      "model": {
        "primary": "routerplex/claude-sonnet-4-6"
      },
      "models": {
        "routerplex/claude-sonnet-4-6": {}
      }
    }
  }
}
 
   - A background Gateway does not inherit terminal variables. Save ROUTERPLEX_API_KEY=<key> in OpenClaw's private ~/.openclaw/.env (Windows: %USERPROFILE%\.openclaw\.env) and restrict it to my user (chmod 600 on macOS/Linux).
 
Step 3. Test OpenClaw itself from a new terminal or a restarted app, so you test the saved setup rather than the shell you changed:
   Stop the Gateway first (openclaw gateway stop; skip if no service is installed), then run:
   openclaw models status --probe --probe-provider routerplex --probe-concurrency 1 --probe-timeout 60000 --probe-max-tokens 256
   The probe result must say ok. Start the Gateway again afterwards with openclaw gateway start.
   Expected reply: "RouterPlex connected."
 
Step 4. If step 1 works but step 3 fails, the problem is OpenClaw's configuration or environment, not RouterPlex. Check these, fix what is wrong, and repeat step 3:
   - The key or base URL is set in one place but not where OpenClaw starts: zsh vs bash startup files, login vs non-login shells, a desktop launcher, a background service, Windows vs WSL, or a remote SSH or container environment.
   - Another setting wins: OPENAI_API_KEY, OPENAI_BASE_URL, OPENAI_API_BASE, ANTHROPIC_API_KEY, ANTHROPIC_BASE_URL, or a project-level config that overrides the user-level one.
   - OpenClaw is outdated, or still needs a full restart to read the new settings.
   - If an environment variable cannot be made to reach OpenClaw reliably and OpenClaw accepts a key in its user-level config, put the key there instead.
 
Keep repeating steps 3 and 4 until the test reply comes back. Stop early only for a 401, 402, or 403, or for a step only I can do, such as a click in a settings window or a login. Then tell me exactly what to do, wait for me, and continue testing afterwards.
 
When it works, tell me which files you changed, where the key is stored, and the final test output.

curl -fsSL https://openclaw.ai/install.sh | bash
openclaw onboard --install-daemon

iwr -useb https://openclaw.ai/install.ps1 | iex
openclaw onboard --install-daemon

{
  "gateway": {
    "mode": "local",
    "bind": "loopback"
  },
  "models": {
    "providers": {
      "routerplex": {
        "baseUrl": "https://api.routerplex.com/v1",
        "apiKey": "${ROUTERPLEX_API_KEY}",
        "api": "openai-completions",
        "models": [
          {
            "id": "claude-sonnet-4-6",
            "name": "claude-sonnet-4-6"
          }
        ]
      }
    }
  },
  "agents": {
    "defaults": {
      "model": {
        "primary": "routerplex/claude-sonnet-4-6"
      },
      "models": {
        "routerplex/claude-sonnet-4-6": {}
      }
    }
  }
}

export ROUTERPLEX_API_KEY='YOUR_ROUTERPLEX_API_KEY'

$env:ROUTERPLEX_API_KEY = 'YOUR_ROUTERPLEX_API_KEY'

openclaw gateway stop
openclaw models status --probe --probe-provider routerplex --probe-concurrency 1 --probe-timeout 60000 --probe-max-tokens 256