Skip to content
繁體中文
Agent Quick Start

Connect OpenCode to Tokatlas ​

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

Before You Start ​

Install OpenCode from its official documentation. This example follows the v1 provider configuration; v2 uses a different providers schema.

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. Run /connect, choose Other, enter provider ID tokatlas, and save your Tokatlas key.
  2. Merge the example into project opencode.json. Replace the model placeholder in both locations.
  3. Run /models and select the Tokatlas model. Create a new session and test a small project task.

Configuration Example ​

json
{
  "$schema": "https://opencode.ai/config.json",
  "provider": {
    "tokatlas": {
      "npm": "@ai-sdk/openai-compatible",
      "name": "Tokatlas",
      "options": {
        "baseURL": "https://api.tokatlas.ai/v1"
      },
      "models": {
        "YOUR_TOKATLAS_MODEL_ID": {
          "name": "Tokatlas Model"
        }
      }
    }
  },
  "model": "tokatlas/YOUR_TOKATLAS_MODEL_ID"
}

Compatibility Notes ​

The credential ID must match provider.tokatlas. @ai-sdk/openai-compatible selects Chat Completions; models requiring Responses need the corresponding OpenAI adapter. For v2, use the v2 provider guide rather than pasting this v1 schema.

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 ​