# OpenClaw

Configure an explicit OpenAI Completions provider for Laminarity without enabling native-provider request shaping.

> Verification: contract-tested; checked 2026-09-01; OpenClaw 2026.7.1-2 custom model provider — The real CLI schema validator and local-agent Chat Completions flow pass with isolated state and a fake key. Production-key certification is tracked separately.

## Configure the provider

Set `api` explicitly to `openai-completions`. This keeps OpenClaw on the Chat Completions transport and avoids native OpenAI-only request shaping.

```json
{
  models: {
    mode: "merge",
    providers: {
      laminarity: {
        baseUrl: "https://api.laminarity.ai/v1",
        apiKey: "${LAMINARITY_API_KEY}",
        api: "openai-completions",
        timeoutSeconds: 300,
        models: [
          {
            id: "auto",
            name: "Laminarity Auto",
            reasoning: false,
            input: ["text", "image"],
            contextWindow: 64000,
            maxTokens: 16000
          }
        ]
      }
    }
  },
  agents: {
    defaults: { model: { primary: "laminarity/auto" } }
  }
}
```

## Model metadata

OpenClaw custom providers do not discover every capability automatically. Add concrete models from `/v1/models` and declare reasoning, image input, context, and output limits accurately when you pin them.

Keep `auto` non-reasoning in the client configuration. Laminarity applies the selected model's execution profile during automatic routing.

## Verify

Use OpenClaw's model list and connection test, then run one short response and one tool call. Connection tests make a real provider request and may consume tokens.

## Upstream documentation

- [OpenClaw model providers](https://docs.openclaw.ai/concepts/model-providers)
- [OpenClaw custom providers](https://docs.openclaw.ai/gateway/config-tools)