Agent Quick Start
Connect Cherry Studio to Tokatlas
Configure Cherry Studio with a Tokatlas key, endpoint, and enabled model.
Before You Start
Install Cherry Studio from its official project releases.
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
| Setting | Value |
|---|---|
| Provider name | Tokatlas |
| Protocol | Chat Completions |
| Endpoint / Base URL | https://api.tokatlas.ai |
| API Key | YOUR_TOKATLAS_API_KEY |
| Model ID | YOUR_TOKATLAS_MODEL_ID |
Setup
- Open Settings → Model Provider and add a custom provider named Tokatlas with type OpenAI.
- Enter the root API address from the Connection Settings table above and your Tokatlas key. Cherry Studio appends the standard API path.
- Use Manage to fetch models or add an enabled model ID manually. Enable the provider switch.
- Select Tokatlas and the model in a new chat, then test a short message.
Compatibility Notes
For this standard Chat route, the resulting request URL should be https://api.tokatlas.ai/v1/chat/completions. If you explicitly use a versioned base, the documented form is https://api.tokatlas.ai/v1/; check the final path when diagnosing 404 errors.
Verify and Troubleshoot
- Open a new conversation and send “Reply with OK only”; check that text returns.
- Check Tokatlas usage for a successful request at the same time with the configured model.
- If you need tools, ask the client to list files in a test directory and check that the tool result returns to the conversation.
- If step 1 fails, test the key and model directly using API Basics. If that succeeds, troubleshoot client settings below.
| Problem | Check |
|---|---|
401 / 403 | Re-enter the Tokatlas key without quotes or spaces; check the auth mode and model access. |
404 | Compare the full request URL with the table above; remove a duplicated /v1 or endpoint suffix. |
| Unknown model | Copy an enabled ID from the model list, save it, and select that model in a new chat. |
| Tool failure | Model capabilities and client protocol support. |
| Changes ignored | Select the Tokatlas provider/profile, fully quit the client, and reopen it. |