Skip to main content
Cherry Studio is a cross-platform desktop client (Windows, macOS, Linux) that brings many model providers together in one app. Add Tokios as a custom OpenAI provider — point it at https://api.tokios.com/v1, paste an sk-tok-… key, and add your Tokios deployment name as a model — and Cherry Studio chats with a model running on your own hardware instead of a hosted provider.

​
Prerequisites

Connector paired

Install and pair tokios-connector next to the model you want Cherry Studio to reach.

Model registered

Register a deployment (public name) for that model.

API key created

Create an sk-tok-… key, optionally scoped to that deployment.

Supported backends

Confirm your local backend (Ollama, llama.cpp, vLLM, LM Studio) is running.

​
Add Tokios as a provider in Cherry Studio

1

Open model provider settings

Open Settings (the gear icon) and go to the Model Services tab. Some builds label this Model Provider — Cherry Studio’s docs are translated from Chinese, so the exact wording can vary by version.
2

Add a provider

Click + Add. In the Add Provider dialog, enter a Provider name (for example, Tokios) and set Provider type to OpenAI — that’s the setting for any generic OpenAI-compatible endpoint.
3

Set the API address and key

Fill in the provider fields:
Include /v1 in the API address yourself. Cherry Studio does not reliably append the path for a custom provider, so give it the full /v1 base.
4

Add your deployment as a model

Cherry Studio doesn’t auto-list models for a custom provider — add one manually using the public deployment name you registered in the Models tab, for example gemma-tunnel. This is the value Cherry Studio sends in the model field; it is not Ollama’s, llama.cpp’s, vLLM’s, or LM Studio’s local model id.
Replace gemma-tunnel with the deployment name you registered, and sk-tok-YOUR_KEY with your own key. Never commit either into a shared config file.

​
Desktop app, model elsewhere

The common shape this solves: Cherry Studio runs on your laptop or desktop, but the model you want — bigger than that machine can run — lives on a workstation or server somewhere else. The connector next to that model dials out to Tokios, and Cherry Studio calls https://api.tokios.com/v1 with your sk-tok-… key. You keep Cherry Studio’s UI with a model that isn’t local to the machine you’re typing on — no inbound ports, no VPN.

​
Troubleshooting

The API key Cherry Studio sent is missing, malformed, or has been revoked. Confirm you pasted the full sk-tok-… key with no extra whitespace, and check its status on the Keys tab.
The model value Cherry Studio sent doesn’t match a registered deployment, or the API address is missing /v1. Confirm the model name matches the public name on the Models tab, and that the address is https://api.tokios.com/v1.
The connector for that deployment is offline or at its concurrency cap. Check the Connectors tab — the connector needs to show as Online, and the machine running it needs to still be up and reachable.

​
Next steps

Compatible clients

See base URL and key setup for other OpenAI- and Anthropic-compatible clients.

API keys

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