Tokatlas

Appearance

繁體中文
Agent Quick Start

Connect OpenClaw to Tokatlas ​

Configure OpenClaw with a Tokatlas key, endpoint, and enabled model.

Before You Start ​

Install and initialize OpenClaw using its official documentation. Back up your existing configuration.

Prepare a Tokatlas API key and a model enabled for your account. Replace all YOUR_... placeholders. Back up existing settings before merging changes.

Connection Settings ​

SettingValue
Provider nameTokatlas
ProtocolChat Completions
Endpoint / Base URLhttps://api.tokatlas.ai/v1
API KeyYOUR_TOKATLAS_API_KEY
Model IDYOUR_TOKATLAS_MODEL_ID

Setup ​

  1. Merge the following settings into ~/.openclaw/openclaw.json, preserving existing agents and providers. Replace both model placeholders with the same enabled ID.
  2. Provide TOKATLAS_API_KEY to the OpenClaw process. A background service must receive it in its own environment, not only your terminal.
  3. Validate the configuration with the installed version’s diagnostics, restart its gateway if required, and select the Tokatlas model.

Configuration Example ​

json
{
  "models": {
    "mode": "merge",
    "providers": {
      "tokatlas": {
        "baseUrl": "https://api.tokatlas.ai/v1",
        "apiKey": "${TOKATLAS_API_KEY}",
        "api": "openai-completions",
        "models": [
          {
            "id": "YOUR_TOKATLAS_MODEL_ID",
            "name": "Tokatlas Model"
          }
        ]
      }
    }
  },
  "agents": {
    "defaults": {
      "model": {
        "primary": "tokatlas/YOUR_TOKATLAS_MODEL_ID"
      }
    }
  }
}

Compatibility Notes ​

models.mode: merge retains other providers. If your agent has a model allowlist or a per-agent override, update it too. Declare context size and optional capabilities only from confirmed model specifications.

Verify and Troubleshoot ​

  1. Open a new conversation and send “Reply with OK only”; check that text returns.
  2. Check Tokatlas usage for a successful request at the same time with the configured model.
  3. If you need tools, ask the client to list files in a test directory and check that the tool result returns to the conversation.
  4. If step 1 fails, test the key and model directly using API Basics. If that succeeds, troubleshoot client settings below.
ProblemCheck
401 / 403Re-enter the Tokatlas key without quotes or spaces; check the auth mode and model access.
404Compare the full request URL with the table above; remove a duplicated /v1 or endpoint suffix.
Unknown modelCopy an enabled ID from the model list, save it, and select that model in a new chat.
Tool failureModel capabilities and client protocol support.
Changes ignoredSelect the Tokatlas provider/profile, fully quit the client, and reopen it.

References ​