Seedance 2.0 15% OFF | Create in Video Generator →
Sign In
DashboardExploreAI GeneratorHOTDesktop AppAPI KeysBilling
Agent setup

Connect OpenClaw to WaveSpeed LLM API

Copy the recommended ~/.openclaw/config.yaml setup for OpenClaw, route requests to /v1/chat/completions, and verify local agent calls in WaveSpeed Logs.

API keyTest model
Config file

~/.openclaw/config.yaml

Protocol

OpenAI-compatible chat completions

Endpoint

/v1/chat/completions

Quick start

1

Create a WaveSpeed access key

2

Export the required key locally

3

Paste config into~/.openclaw/config.yaml

4

Run openclaw and check Logs

OpenAI-compatible chat completions

Usage appears in Dashboard and Logs

Switch models without rewriting agent code

Edit ~/.openclaw/config.yaml
# File: ~/.openclaw/config.yaml
providers:
  wavespeed:
    type: openai-compatible
    base_url: https://llm.wavespeed.ai/v1
    api_key_env: WAVESPEED_API_KEY
    endpoint: /chat/completions
    default_model: anthropic/claude-opus-4.8

Agent integration guide

Use OpenClaw with WaveSpeed LLM API

This guide shows how to connect OpenClaw to WaveSpeed AI with ~/.openclaw/config.yaml, OpenAI-compatible chat completions, /v1/chat/completions, base URL https://llm.wavespeed.ai/v1, and default model anthropic/claude-opus-4.8. Copy the configuration above, export your API key, run the agent, then verify requests in Logs.

1

Create a WaveSpeed access key

2

Export the required key locally

3

Paste config into

~/.openclaw/config.yaml
4

Run openclaw and check Logs

What this OpenClaw setup configures

Protocol

OpenAI-compatible chat completions

Endpoint

/v1/chat/completions

Model

anthropic/claude-opus-4.8

The copy-ready configuration above is the only OpenClaw file you need to edit for the recommended setup: ~/.openclaw/config.yaml. Keep the API key in your shell environment so it is not committed to a repository.

Troubleshooting

The API key is not being picked up

Export WAVESPEED_API_KEY in the same shell where you run OpenClaw. If you use a shell profile, reload the terminal before starting the agent.

Requests fail with a protocol or endpoint error

Check that OpenClaw is using OpenAI-compatible chat completions and endpoint /v1/chat/completions. Protocol mismatches are the most common cause of 404 or payload errors.

The selected model does not work

Confirm the model id exists in WaveSpeed Models, then paste the exact id into ~/.openclaw/config.yaml. You can start with the default model shown on this page.

No requests appear in Logs

Make sure OpenClaw is using the WaveSpeed base URL and your current API key. Then send a new prompt from the local agent and refresh Logs.

Can this OpenClaw guide show up in search?

Yes. This page is built as an indexable setup guide for users searching for OpenClaw custom provider, OpenAI-compatible endpoint, base URL, and local agent configuration workflows.

View all agent setup guidesBrowse models