◉ TOKNADO

Integrations / OpenClaw

OpenClaw + TOKNADO

How to use OpenClaw with TOKNADO's OpenAI-compatible endpoint

OpenClaw lets you plug in any endpoint that speaks the OpenAI chat completions format as a custom provider. TOKNADO is exactly that: one OpenAI-compatible endpoint in front of a managed model pool, so OpenClaw gets a single base URL and key instead of several provider accounts.

This guide covers both ways to add it: the interactive wizard (fastest) and the manual config for people who keep their setup in version control. It also covers the one step people miss: allowing the model after you define the provider.

Start free trial Jump to setup

What you need

Setup: OpenClaw with TOKNADO

  1. Run the configuration wizard

    On an existing install this adds a provider without disturbing what you already have.

    openclaw configure
  2. Choose the custom provider path

    When asked where the Gateway will run, choose Local. For the section, choose Model. For Model / Auth Provider, choose Custom provider.

  3. Enter the TOKNADO details

    Use these values at the prompts. For compatibility, pick OpenAI-compatible. The base URL must include the API path (normally ending in /v1).

    API Base URL  : https://toknado.up.railway.app/v1
    API key       : YOUR_TOKNADO_API_KEY
    Compatibility : OpenAI-compatible
    Model ID      : toknado/auto
  4. Or edit the config directly

    If you prefer manual config, add a provider entry. api must be openai-completions for OpenAI-compatible endpoints.

    {
      "models": {
        "mode": "merge",
        "providers": {
          "toknado": {
            "baseUrl": "https://toknado.up.railway.app/v1",
            "apiKey": "YOUR_TOKNADO_API_KEY",
            "api": "openai-completions",
            "models": [
              { "id": "toknado/auto", "name": "TOKNADO" }
            ]
          }
        }
      }
    }
  5. Select the model and test

    Model references use the form provider/model-id. Set it as default, then open the dashboard and send a message.

    openclaw models set toknado/toknado/auto
    openclaw dashboard

Notes for real-world use

Troubleshooting OpenClaw + TOKNADO

SymptomWhat to check
404 or “not found”The base URL is missing its API path. It should end where /chat/completions would be appended, usually /v1.
“Model not allowed”The provider exists but the model is not in the allowlist. Add toknado/toknado/auto and apply the config.
Unknown model or 400The model ID must match your dashboard exactly, including any prefix or version tag.
401 / invalid keyRe-copy the key from the dashboard, no trailing space, and confirm your plan or trial is active.
429 or slowdownsYou hit the rolling hourly limit or upstream availability dipped. Check usage in the Storm Console and consider a larger plan.

FAQ

Does OpenClaw support custom OpenAI-compatible providers?

Yes. Choose Custom provider in openclaw configure and select OpenAI-compatible, or define the provider in the models section of the config with api set to openai-completions.

What goes in the base URL field?

The TOKNADO endpoint from your dashboard, including its API path. Do not append /chat/completions; the client adds that.

Can I keep my other OpenClaw providers?

Yes. With mode set to merge the TOKNADO provider is added alongside existing ones, and you switch with openclaw models set.

Can I try this before paying?

The TOKNADO setup guide offers a three-day trial with up to 250 requests per rolling hour, which is enough to confirm OpenClaw connects.

Point OpenClaw at TOKNADO

One OpenAI-compatible endpoint, a managed model pool behind it, and usage you can see in the Storm Console. 3-day trial, up to 250 requests per rolling hour.

Start free trial See pricing Setup guide

Hourly limits apply over the previous 60 minutes. Service is best effort; upstream availability can reduce throughput.

More tools that work with TOKNADO