Agent integration guide
Use Continue CLI with WaveSpeed LLM API
This guide shows how to connect Continue CLI to WaveSpeed AI with ~/.continue/config.yaml, OpenAI-compatible chat completions, /v1/chat/completions, base URL https://llm.wavespeed.ai/v1, and default model deepseek/deepseek-v4.1-flash-1017. Copy the configuration above, export your API key, run the agent, then verify requests in Logs.
Create a WaveSpeed access key
Export the required key locally
Paste config into
~/.continue/config.yamlRun cn and check Logs
What this Continue CLI setup configures
Protocol
OpenAI-compatible chat completions
Endpoint
/v1/chat/completions
Model
deepseek/deepseek-v4.1-flash-1017
The copy-ready configuration above is the only Continue CLI file you need to edit for the recommended setup: ~/.continue/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 Continue CLI. If you use a shell profile, reload the terminal before starting the agent.
Requests fail with a protocol or endpoint error
Check that Continue CLI 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 ~/.continue/config.yaml. You can start with the default model shown on this page.
No requests appear in Logs
Make sure Continue CLI 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 Continue CLI guide show up in search?
Yes. This page is built as an indexable setup guide for users searching for Continue CLI custom provider, OpenAI-compatible endpoint, base URL, and local agent configuration workflows.