Using BeatAPI in ChatBox
Using BeatAPI in ChatBox
ChatBox is a cross-platform desktop chat client. BeatAPI serves the OpenAI, Anthropic, and Gemini request formats, so ChatBox works through whichever of its three provider types matches the model you want.
Prerequisites
- ChatBox installed — Windows, macOS, Linux, or the web build.
- A BeatAPI API key — create one in Dashboard → API Keys.
Step 1: Open the configuration
On first launch a setup wizard appears — click Use your own API Key or local model.
If ChatBox is already configured, open settings with the gear icon at the bottom left, or Ctrl+, (Cmd+, on macOS).
Step 2: Choose a provider type and fill in the host
The API Host differs per provider type, because each client appends a different path. Getting this wrong is the most common failure.
The API Key is the same BeatAPI key in all three cases.
Every model on the account answers on every format, so the provider type is a matter of which shape ChatBox sends, not of which models you can reach. The three hosts differ only because the OpenAI type appends /v1/chat/completions, the Claude type appends /messages, and the Gemini type appends v1beta/models/.... Each combination above resolves to a real BeatAPI endpoint.
Step 3: Pick a model
Select the model from the dropdown, or type its ID if the list has not refreshed.
The full catalogue is on the Text API pages and the pricing page.
Optional parameters
Setting Max Tokens is the simplest cost control there is: output is the expensive half of most conversations.
FAQ
ChatBox cannot connect
- Re-check the API Host against the table above — the
/v1differs per provider type. - Confirm the key is active in Dashboard → API Keys.
BeatAPI models do not appear in the list
Type the model ID directly into the model field. IDs are case-sensitive and are listed on the pricing page.
Errors during a conversation
Checking usage and spend
The dashboard shows calls, tokens, and cost per API key; the same figures come from GET /v1/usage.
Support
Open a support ticket from the dashboard and include the request_id from the failing response.

