<!-- Generated from public website sources; do not edit this file. -->

> DSSUB design reference. Account, payments and API are not connected; prices, policies and setup examples require independent launch verification.

# OpenClaw
Prepare a custom provider for the Gateway, TUI and Control UI.

## Current availability
DSSUB is a design preview. These are complete configuration references, not a live connection: `api.dssub.invalid` is intentionally non-routable. No real account, key, payment or inference service is connected. Replace the endpoint and use an authorized key only after DSSUB publishes verified connection details. Client versions and live tool compatibility remain unverified.

## Install and onboard
Use the [official installation guide](https://docs.openclaw.ai/start/getting-started). Run `openclaw onboard` to configure an installed Gateway. Record `openclaw --version`. The credential must be available on the machine running the Gateway.

## Save the provider
Merge the downloaded file into `~/.openclaw/openclaw.json`. Preserve other agents, providers and security settings. Set `DSSUB_API_KEY` in the Gateway’s supported environment; exporting it in a TUI terminal does not necessarily update an existing background service.

```json
{
  "models": {
    "mode": "merge",
    "providers": {
      "dssub": {
        "baseUrl": "https://api.dssub.invalid/v1",
        "apiKey": "${DSSUB_API_KEY}",
        "api": "openai-completions",
        "models": [
          {
            "id": "deepseek-flash",
            "name": "DeepSeek V4.1 Flash",
            "input": [
              "text"
            ]
          },
          {
            "id": "deepseek-v4-pro",
            "name": "DeepSeek V4 Pro",
            "input": [
              "text"
            ]
          }
        ]
      }
    }
  },
  "agents": {
    "defaults": {
      "model": {
        "primary": "dssub/deepseek-flash"
      },
      "models": {
        "dssub/deepseek-flash": {},
        "dssub/deepseek-v4-pro": {}
      }
    }
  }
}
```

## Start and inspect the Gateway
For an already installed Gateway, restart after editing its configuration, then inspect its model setup.

```sh
openclaw gateway restart
openclaw models status
openclaw tui
```

## Switch models
Use `/model dssub/deepseek-v4-pro` or `/model dssub/deepseek-flash` in a new session. In the Control UI, choose the corresponding DSSUB entry from its model picker. Model selection and service authentication are separate checks.

## Choose reasoning effort
OpenClaw offers `/think` for supported routes. DSSUB has not verified any reasoning levels, so leave defaults unchanged. Text is the only input declared in this example; do not enable image input because a related upstream model supports it.

## Verify your first request
After a live connection is published, start a new session in a small test project. First ask for a short text reply. Then ask the tool to read README.md and summarize it without modifying files. Confirm the selected provider and model, then match the request in [Usage](/account/usage). Check tool results, streaming completion and billed tokens separately. The current sample dashboard cannot verify a real request.

## Troubleshoot and restore
A DNS failure for `api.dssub.invalid` is expected in this preview. For a real connection, check the exact endpoint, API format, model ID and credential. A 401 concerns authentication; a 404 may concern a path or model; a 429 may concern a quota or rate limit. See [troubleshooting](/docs/error-codes/index.md).

Back up configuration before editing, merge only DSSUB fields, and retain your existing providers and permissions. To revert, select your previous provider and restore only the fields you changed. Stop and restart the tool after changing its startup environment.

## Reference
[Custom providers](https://docs.openclaw.ai/concepts/model-providers/custom-providers), reviewed November 16, 2026.

---

HTML source: [OpenClaw — dssub Tutorials](/docs/openclaw/)
