Kling 4.0 is LIVE — Unbelievably Real Video | Try Now →
Agent Setup

Connect DeepSeek Harness to WaveSpeed LLM API

Copy the recommended ~/.dsh/cordis.patch.yml setup for DeepSeek Harness, route requests to /v1/chat/completions, and verify local agent calls in WaveSpeed Logs.

DeepSeek's agent harness; add WaveSpeed as a provider route.

Config file

~/.dsh/cordis.patch.yml

Protocol

OpenAI-compatible chat completions

Endpoint

/v1/chat/completions

Manual setup

1

Create a WaveSpeed access key

2

Export the required key locally

3

Paste config into~/.dsh/cordis.patch.yml

4

Run dsh --profile headless and check Logs

OpenAI-compatible chat completions

Usage appears in Dashboard and Logs

Switch models without rewriting agent code

One-command setup

Configures DeepSeek Harness, checks that it works, and backs up your previous settings. Add --undo to restore them.

  1. 1

    Install the WaveSpeed CLI

    npm install -g @wavespeed/cli
  2. 2

    Sign in

    wavespeed login
  3. 3

    Configure DeepSeek Harness

    wavespeed setup dsh

No Node.js? See other install options

Manual setup

Edit ~/.dsh/cordis.patch.yml
# File: ~/.dsh/cordis.patch.yml
- id: llm-pi-ai
  config:
    providers:
      wavespeed:
        apiKeyEnv: WAVESPEED_API_KEY
        api: openai-completions
        baseURL: https://llm.wavespeed.ai/v1
        models:
          - id: deepseek/deepseek-v4.1-flash-1017
- id: agent-default-model
  config:
    provider: wavespeed
    model: deepseek/deepseek-v4.1-flash-1017

Do not replace the variable name

WAVESPEED_API_KEY is the environment variable name that the agent reads. Keep this name in the config file, and put your real API key in your shell instead.

1

Temporary for this terminal

Works until you close this terminal window.

export WAVESPEED_API_KEY="wsk_live_..."
2

Keep it after restart

Writes the key into your shell profile so new terminals can read it.

echo 'export WAVESPEED_API_KEY="wsk_live_..."' >> ~/.zshrc
source ~/.zshrc

Agent integration guide

Use DeepSeek Harness with WaveSpeed LLM API

This guide shows how to connect DeepSeek Harness to WaveSpeed AI with ~/.dsh/cordis.patch.yml, 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.

1

Create a WaveSpeed access key

2

Export the required key locally

3

Paste config into

~/.dsh/cordis.patch.yml
4

Run dsh --profile headless and check Logs

What this DeepSeek Harness 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 DeepSeek Harness file you need to edit for the recommended setup: ~/.dsh/cordis.patch.yml. 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 DeepSeek Harness. If you use a shell profile, reload the terminal before starting the agent.

Requests fail with a protocol or endpoint error

Check that DeepSeek Harness 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 ~/.dsh/cordis.patch.yml. You can start with the default model shown on this page.

No requests appear in Logs

Make sure DeepSeek Harness 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 DeepSeek Harness guide show up in search?

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