OpenClaw Setup

Why this setup

OpenClaw lets you register additional model providers via the models.providers block in its config file. For Claude models served by ClaudeStore, the cleanest integration is to add ClaudeStore as a custom anthropic-messages provider.

• OpenClaw treats it as a first-class Anthropic-compatible provider.
• System blocks, tool use, content blocks, and reasoning are preserved end-to-end.
• You keep using normal OpenClaw model refs (claudestore/claude-sonnet-4-6).

Config path

OpenClaw reads its config from a single JSON file in your home directory:

~/.openclaw/openclaw.json

The CLI exposes openclaw config and openclaw configure helpers, but for a provider this specific it's faster and clearer to edit the JSON directly. The snippet below is drop-in.

Environment variable

Export your ClaudeStore key so the config can reference it via placeholder:

export CLAUDESTORE_API_KEY="YOUR_SK_CS4_KEY"

Storing the key in an env var keeps it out of openclaw.json and out of any backups or git history of dotfiles.

Minimal working config

Drop this into ~/.openclaw/openclaw.json (the file is parsed as JSON5, so trailing commas and comments are allowed):

{
  env: {
    CLAUDESTORE_API_KEY: "YOUR_SK_CS4_KEY",
  },
  agents: {
    defaults: {
      model: { primary: "claudestore/claude-sonnet-4-6" },
    },
  },
  models: {
    mode: "merge",
    providers: {
      claudestore: {
        baseUrl: "https://api3.claudestore.store",
        apiKey: "${CLAUDESTORE_API_KEY}",
        api: "anthropic-messages",
        models: [
          {
            id: "claude-sonnet-4-6",
            name: "Claude Sonnet 4.6",
            reasoning: true,
            input: ["text", "image"],
            contextWindow: 1000000,
            maxTokens: 64000,
          },
          {
            id: "claude-opus-4-7",
            name: "Claude Opus 4.7",
            reasoning: true,
            input: ["text", "image"],
            contextWindow: 1000000,
            maxTokens: 128000,
          },
          {
            id: "claude-haiku-4-5",
            name: "Claude Haiku 4.5",
            reasoning: true,
            input: ["text", "image"],
            contextWindow: 200000,
            maxTokens: 64000,
          },
        ],
      },
    },
  },
}

Why no /v1 in baseUrl

In OpenClaw's Anthropic-compatible provider flow, baseUrl is the provider root. OpenClaw appends the Anthropic Messages path itself.

• ✅ Correct: https://api3.claudestore.store
• ❌ Wrong: https://api3.claudestore.store/v1

Adding /v1 here will double up the path and you'll see 404s on every request.

Verification

After saving the config, run these checks in order:

openclaw gateway status

Confirms OpenClaw can reach the configured providers.

openclaw models list

You should see claudestore/claude-sonnet-4-6, claudestore/claude-opus-4-7, and claudestore/claude-haiku-4-5 in the output.

openclaw models set claudestore/claude-sonnet-4-6

openclaw dashboard

Send a small request from the dashboard and confirm the call shows up under the claudestore provider.

Advanced: 1M context

For long-context work on Sonnet 4.6 or Opus 4.7, enable the 1M context flag per model:

{
  agents: {
    defaults: {
      models: {
        "claudestore/claude-sonnet-4-6": { params: { context1m: true } },
        "claudestore/claude-opus-4-7":   { params: { context1m: true } },
      },
    },
  },
}

Important limitation: /fast

Troubleshooting

echo $CLAUDESTORE_API_KEY

Related

• SDK & client overview — OpenClaw is an advanced client; it uses custom provider config rather than a simple base_url setting.
• API key configuration
• Models — current Claude model IDs.

Windows setup

1. Install OpenClaw

OpenClaw ships as a npm package and as standalone Windows binaries:

npm install -g openclaw
openclaw --version

Or grab openclaw-windows-x64.exe from GitHub Releases and put it on your PATH.

2. Config path on Windows

OpenClaw reads %USERPROFILE%\.openclaw\openclaw.json (e.g. C:\Users\<you>\.openclaw\openclaw.json):

mkdir $env:USERPROFILE\.openclaw -ErrorAction SilentlyContinue
notepad $env:USERPROFILE\.openclaw\openclaw.json

Paste the minimal config from the section above. Save as UTF-8 (no BOM).

3. Persist CLAUDESTORE_API_KEY

setx CLAUDESTORE_API_KEY "YOUR_SK_CS4_KEY"

GUI alternative: Win+R → sysdm.cpl → Environment Variables → User variables → New.

4. Verify

openclaw gateway status
openclaw models list
openclaw models set claudestore/claude-sonnet-4-6

5. WSL

If you launch OpenClaw from inside WSL, use the Linux config path ~/.openclaw/openclaw.json and re-export the env var in ~/.bashrc:

export CLAUDESTORE_API_KEY="YOUR_SK_CS4_KEY"

6. Troubleshooting

• "openclaw is not recognized" — open a fresh PowerShell, or add %APPDATA%\npm to PATH.
• Placeholder ${CLAUDESTORE_API_KEY} not resolved — env var not set in the shell that launched openclaw. Use setx and reopen.
• JSON parse error — Notepad saved with BOM. Save the file as UTF-8 without BOM (use VS Code or Notepad++).
• PowerShell quoting — wrap all values in double quotes; cmd.exe rules differ.
• Antivirus blocks node.exe / openclaw.exe — whitelist the binary and the host api3.claudestore.store.