OpenClaw

Setup

One command, no config files:

npx @opperai/cli launch openclaw

This adds an opper provider entry to ~/.openclaw/agents/main/agent/models.json and defaults to running gateway start as a background daemon.

To wire it by hand, add Opper as a custom provider in ~/.openclaw/config.json. This is the top-level config; the CLI writes the equivalent entry into the per-agent models.json above. Either location works — use the manual one when you want the provider available to every agent, or want the model list under version control:

{
  "env": { "OPPER_API_KEY": "your-api-key" },
  "agents": {
    "defaults": {
      "model": { "primary": "opper/anthropic/claude-opus-4-7" }
    }
  },
  "models": {
    "providers": {
      "opper": {
        "baseUrl": "https://api.opper.ai/v3/compat",
        "apiKey": "${OPPER_API_KEY}",
        "api": "openai-completions",
        "models": [
          { "id": "anthropic/claude-opus-4-7", "name": "Claude Opus 4.7 (Opper)" },
          { "id": "anthropic/claude-sonnet-4-6", "name": "Claude Sonnet 4.6 (Opper)" },
          { "id": "mistral/mistral-large-2512", "name": "Mistral Large 3 (Opper)" },
          { "id": "gemini/gemini-3.5-flash", "name": "Gemini 3.5 Flash EU (Opper)" }
        ]
      }
    }
  }
}

Choosing a model

Switch at any time:

openclaw models set opper/anthropic/claude-sonnet-4-6

The opper/ prefix names the provider; everything after it is the Opper model ID.

The custom-provider route gives you full model access with a single API key, but no session span tracing. OpenClaw is built on pi, so if you want traces grouped per session it’s worth looking at the native pi provider package — check its docs for whether your OpenClaw version can load pi extensions.

Get started

Platform

Build

Observe & Control

Integrations

Tutorials

Tooling

Setup

Choosing a model

pi

All integrations

​Setup

​Choosing a model

​Related

pi

All integrations

Setup

Choosing a model

Related