Skip to main content

Integration overview

Put your TokenRoute API Key into the client, IDE or command-line tool you already use.

Windows users: skip manual config editing

Use GSS Deploy (Windows one-click setup) for ChatGPT, Claude Code, Hermes, or WorkBuddy. Install it, select a tool locally, enter your API Key, and it writes the configuration for you.

Which tool​

What you wantUse thisDifficulty
Everyday chat, quick model trialsChatboxLow
Desktop client managing several modelsCherry StudioLow
Writing code in an IDEVS Code / ClineMedium
Letting AI edit code from the terminalCodex CLIMedium
A Claude-style CLIClaude CodeMedium
Adding custom models in WorkBuddyWorkBuddyMedium
Agent workflows with multiple profiles and toolsetsHermesHigh

If you have no preference, start with Chatbox — install, fill three fields, done. It's the fastest way to confirm your key works.

Before you start​

Four prerequisites, all required:

RequirementNotes
API KeyCreated in the console — see Get an API Key
Available quotaYour account or department must have balance, or calls fail immediately
Model nameCopy from Models — case-sensitive
Network reachabilityYour machine can reach api.smartwan.com

Common configuration fields​

Tools name these fields differently, but they all want the same few things:

FieldWhat to enter
API KeyThe sk- key created in the console
Base URLhttps://api.smartwan.com or https://api.smartwan.com/v1 — follow the tool's page
Modele.g. deepseek-v4-flash, claude-sonnet-5, gpt-5.5
API typeOpenAI Compatible or Anthropic, depending on what the tool supports
Does Base URL need /v1?

This is the most common trap. Some tools append /v1 automatically; add it yourself as well and you get /v1/v1/chat/completions and a 404. Every tool page states the recommended value — follow it.

Verifying your setup​

First click "fetch models" / "refresh model list" in the tool — if the list loads, both key and network are working.

Then start a new conversation and send:

Hello, please reply with: setup successful

A normal reply means you're connected.

If it fails, check in this order:

  1. Was the API Key copied in full (no characters lost at either end)?
  2. Is /v1 in the Base URL duplicated or missing?
  3. Does the model name match the model list exactly?
  4. Does the account still have quota?
  5. Protocol and client authentication — Messages accepts x-api-key or Bearer; follow Authentication

Still stuck? See the FAQ.

Verification scope​

ScopeWhat was confirmed
Python SDKsMinimal live calls with OpenAI 3.17.0, Anthropic 1.7.0 and Google GenAI 2.24.0
CLIsMinimal live calls with Codex CLI 0.155.1 + gpt-5.5, and Claude Code 2.1.278 + claude-haiku-4-5
HermesProvider matching, configuration parsing and stable tool-management commands; the complete Agent / IM flow needs separate validation
GUI clients, IDEs and installerConfiguration instructions do not establish complete flow verification for your version, OS and account

The live calls above were run on 2026-09-22. After upgrading a client or changing models, repeat a minimal call before restoring tools and advanced parameters.

Platform notes​

OSNotes
WindowsPrefer the tool's own GUI configuration. For CLI tools, note that PowerShell and CMD set environment variables differently
macOSHomebrew works well for installing Node.js and similar dependencies; config files usually live in ~/.config, ~/.claude, ~/.codex
LinuxShell-based configuration mostly; mind environment variable scope and file permissions