Skip to main content
Tokios exposes standard OpenAI and Anthropic API surfaces, so any client that lets you set a custom base URL works. You change 2 things: the base URL and your API key (sk-tok-…). The "model" value is the public deployment name you registered (for example, gemma-tunnel).

Quick verdict: 39 clients confirmed

All 39 clients connect by pointing at https://api.tokios.com/v1 (OpenAI) or https://api.tokios.com (Anthropic).

Which base URL?

Coding agents and IDEs (15 clients)

These connect from inside your editor or terminal for code generation, editing, and tool-calling workflows.
Claude Code uses ANTHROPIC_BASE_URL (no /v1). Zed, Pi, and omp can speak either surface — they default to OpenAI, and switching them to Anthropic also means dropping the /v1. Everything else above uses OPENAI_BASE_URL or equivalent with the /v1 suffix. See the Coding agent compatibility page for per-agent setup details.

Chat applications (10 clients)

General-purpose chat UIs for conversational interaction with your local models.
“Depends on model” means the chat app sends the tools field in the request, but the local model must support tool calling for it to work. Qwen3-Coder-30B and Mistral-7B-Instruct handle tool calls reliably on most engines.

Per-client setup for chat apps

SDKs and frameworks (8 clients)

Programmatic libraries for building applications on top of your Tokios endpoint.

Code examples

Clients that read OPENAI_BASE_URL or ANTHROPIC_BASE_URL pick Tokios up automatically once you export those variables in your shell:

Observability and gateway tools (4 clients)

Tools for tracing, proxying, or evaluating your Tokios endpoint.

Langfuse

Langfuse traces LLM calls by proxying requests through its SDK. Configure it as an OpenAI provider with your Tokios base URL:
  • LLM Connection base URL: https://api.tokios.com/v1
  • API Key: your sk-tok-… key
See the Langfuse guide.

LiteLLM

LiteLLM can proxy Tokios as an upstream provider. Add it to your litellm_config.yaml:

Promptfoo

Promptfoo evaluates LLM outputs. Add Tokios as an OpenAI-compatible provider in your promptfooconfig.yaml:

RAG and agent platforms (2 clients)

AnythingLLM wraps any OpenAI-compatible endpoint as a “Generic OpenAI” provider and adds document retrieval on top. OpenClaw connects as an OpenAI-compatible gateway client.

Feature support matrix

A consolidated view of feature support across all 39 clients.

The universal setup pattern

Every client above follows the same 3 steps:
  1. Set the base URL to https://api.tokios.com/v1 (OpenAI) or https://api.tokios.com (Anthropic).
  2. Set the API key to your sk-tok-… key.
  3. Set the model to your registered deployment name.
If a client isn’t listed here but supports a custom OpenAI-compatible base URL, it almost certainly works. Test it with:

One API key works with all compatible clients

Create a single sk-tok-… key in the Tokios dashboard, and it works across every client on this page. Scope it to specific deployments with model-name patterns, or use * for full access. Rotate keys anytime — revoking cuts access immediately.

Quickstart

Pair a connector and register your first model end to end.

API keys

Create, scope, and rotate sk-tok-… keys for teammates and agents.

Coding agents

Detailed setup for 15 coding agents that connect through Tokios.

Remote access comparison

How Tokios compares to Tailscale, Cloudflare Tunnel, and SSH tunnels.