OpenClaw (Clawdbot) — Configuration & API integration

What is OpenClaw?

An agent gateway that runs on common operating systems and can connect to channels such as WhatsApp, Telegram, Discord, iMessage, and more. You send a message and get answers from your agents from many surfaces; extra channels can be added via plugins.

See the official project for the latest features and docs: OpenClaw.

1. Install OpenClaw

Pick the flow that matches your OS.

Script install (recommended)

macOS / Linux

Install

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

Check

openclaw --version

Windows (PowerShell)

Note: OpenClaw’s installer is often run from WSL2. In PowerShell, start WSL and run the install inside WSL.

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

Verify:

openclaw --version

2. Initialize OpenClaw

Start the interactive wizard:

openclaw onboard

Typical flow (wording may change by version):

Choose QuickStart
Choose Skip for now where you don’t need vendor keys yet
Choose All providers (or the option that matches your plan)
Choose Keep current when unsure
You can Skip optional chat-tool or skills steps and finish onboarding
Enable recommended privacy / gateway options if the wizard suggests them

When onboarding completes, OpenClaw may open the gateway UI in your browser.

If the gateway is not running:

openclaw gateway

2. Connect OpenClaw to mixgateway.io

1. Get a gateway API key

Open mixgateway.io and sign in.
In the [console](/dashboard), open API Keys (or equivalent).
Create a key and copy it — use it as Authorization: Bearer … against the gateway.

2. Edit `openclaw.json`

After installation, OpenClaw keeps config under its config directory (often ~/.openclaw).

Open the folder

open ~/.openclaw

On Windows + WSL, from that directory you can open Explorer with:

explorer.exe .

Edit openclaw.json. Merge the following idea with your existing file: set a provider that points at the OpenAI-compatible base URL https://api.mixgateway.io/v1, and wire agents.defaults.model.primary to a model id that uses that provider.

Example (adjust names to match your OpenClaw version — structure inspired by third-party gateway guides such as ApiSet’s OpenClaw doc):

{
  "agents": {
    "defaults": {
      "model": {
        "primary": "mixgateway/deepseek:deepseek-chat"
      },
      "models": {
        "mixgateway/deepseek:deepseek-chat": {}
      }
    }
  },
  "models": {
    "mode": "merge",
    "providers": {
      "mixgateway": {
        "baseUrl": "https://api.mixgateway.io/v1",
        "apiKey": "PASTE_YOUR_GATEWAY_API_KEY_HERE",
        "api": "openai-completions",
        "models": [
          {
            "id": "deepseek:deepseek-chat",
            "name": "deepseek-chat",
            "reasoning": false,
            "input": ["text"],
            "cost": {
              "input": 0,
              "output": 0,
              "cacheRead": 0,
              "cacheWrite": 0
            },
            "contextWindow": 128000,
            "maxTokens": 8192
          }
        ]
      }
    }
  }
}

Notes:

Replace PASTE_YOUR_GATEWAY_API_KEY_HERE with your real key from the dashboard.
Change deepseek:deepseek-chat to any model your gateway supports (see Models & Routing).
mixgateway is the provider key in this example only — you can rename it, but keep agents.defaults.model.primary in sync (providerKey/modelId).

3. Restart the gateway

openclaw gateway restart

You should see the gateway UI reflect the new provider and model.