Chatbox
Chatbox is a cross-platform desktop and mobile chat client. Add MirAPI as a custom OpenAI-compatible provider and one base URL plus one key gives you the whole catalogue — chat, vision, and reasoning models.
What you need
Section titled “What you need”| Element | Value |
|---|---|
| Base URL | https://api.mirapi.ai/v1 |
| API key | Your MirAPI key (sk-...) |
| Model | deepseek-chat |
Chatbox speaks the OpenAI-compatible protocol, so the only endpoint you configure is the base URL. Because Chatbox appends /chat/completions itself, the base URL must end in /v1.
Configure
Section titled “Configure”- Open Settings → Add custom provider (Add Provider).
- Choose OpenAI API compatible.
- Fill in:
API domain / Base URL: https://api.mirapi.ai/v1API key: sk-...Default model: deepseek-chat- Save the provider.
- Add
deepseek-chat— or any other id fromGET /v1/models— to the provider’s model list if it isn’t populated, then start a new chat with the MirAPI provider.
Verify with a message
Section titled “Verify with a message”Send:
Reply with exactly: connected to MirAPIThe reply should contain the exact phrase. If you get an error instead, it almost always comes down to the base URL or the key — check both against the table above.
Tool-specific pitfalls
Section titled “Tool-specific pitfalls”- Keep
/v1in the base URL.https://api.mirapi.ai/v1is correct;https://api.mirapi.aialone breaks the chat path. - Pick models your key can call. A model outside your whitelist returns 403 even with a valid key.
- 403 also means an empty balance. Top up and retry — the same key works again immediately.
429means rate limited. Retry with jittered exponential backoff; MirAPI sends noRetry-Afterheader and does not retry for you.- Errors carry a request ID. Chatbox shows the raw HTTP error text, including MirAPI’s request-id suffix — keep it for support tickets.