Using BeatAPI in Cherry Studio
Using BeatAPI in Cherry Studio
Cherry Studio is a desktop chat client that talks to several providers side by side. BeatAPI is added as an OpenAI-type provider, after which every text model on the account appears in its model picker.
Prerequisites
- Cherry Studio installed — from the official site.
- A BeatAPI API key — create one in Dashboard → API Keys.
Step 1: Open provider settings
Click the settings icon at the top right, or press Ctrl+, (Cmd+, on macOS), then choose Model Service in the left menu.
Step 2: Add BeatAPI as a provider
At the bottom of the model service page, click + Add, then fill in:
Click Confirm. In the configuration panel on the right, fill in:
Enter https://api.beatapi.io with no /v1 suffix and no trailing path. Cherry Studio appends /v1/chat/completions itself; adding /v1 yourself produces /v1/v1/chat/completions, which 404s on every message.
Make sure the BeatAPI provider toggle at the top right is on (green), then use the Test button to confirm the connection before adding models.
Step 3: Add models
With the provider configured, find the Models section and click Manage to open the model picker. Search for the ID you want and click + to add it.
The full catalogue is on the Text API pages and the pricing page. Add as many as you like; switching between them is a dropdown in the chat header.
Step 4: Chat
Return to the main window, start a new chat with +, click the model selector at the top, and pick a model under the BeatAPI provider.
FAQ
Cherry Studio cannot connect
- API URL must be
https://api.beatapi.io— no/v1. - The key must be active — check Dashboard → API Keys.
- The provider toggle must be on.
The model list is empty or will not refresh
Add models by ID manually in the model manager. The IDs are on the pricing page and are case-sensitive.
Errors during a conversation
Checking usage and spend
The dashboard shows calls, tokens, and cost, broken down per API key. The same figures are available from GET /v1/usage.
Support
Open a support ticket from the dashboard and include the request_id from the failing response.

