Skip to main content
ChatBox is a widely used cross-platform AI client with Windows, macOS, Linux, and web availability. When you connect ChatBox to Crazyrouter, the safest approach is to use ChatBox’s OpenAI API Compatible or OpenAI API provider flow instead of searching for a provider-specific preset. This setup is useful because it:
  • is simple for non-technical users
  • lets you switch between Crazyrouter-approved models inside one desktop client
  • works well for desktop chat, knowledge-base Q&A, file reading, and everyday writing tasks

​
Start Here

Use this configuration first:
  • Provider / API Mode: OpenAI API Compatible or OpenAI API
  • API Host: https://crazyrouter.com
  • API Path: leave it blank or keep the default
  • API Key: sk-xxx
  • First validation model: gpt-5.4
According to ChatBox’s current official provider documentation, the API Path usually does not need to be filled manually because ChatBox already has a default OpenAI-compatible chat path. For Crazyrouter docs, the safest starting point is to enter the root host https://crazyrouter.com and avoid manually forcing /v1/chat/completions at the beginning.

​
Who This Guide Is For

  • users who want a fast desktop setup for Crazyrouter
  • users who want multi-model daily chat, translation, summarization, or writing assistance
  • users who want to combine ChatBox knowledge-base or file-Q&A features with Crazyrouter
  • users who want a full GUI setup without writing code

​
Prerequisites

ItemNotes
Crazyrouter accountRegister at crazyrouter.com first
Crazyrouter tokenCreate a dedicated token for ChatBox
ChatBox clientDesktop is recommended because knowledge-base features are stronger there
Allowed modelsStart by allowing at least one chat model
Suggested first-pass allowlist:
  • gpt-5.4
  • claude-sonnet-4-6
  • gemini-3-pro-preview

​
Install ChatBox

​
Windows

  1. Open the ChatBox website
  2. Download the Windows installer
  3. Run the installer
  4. Launch ChatBox after setup

​
macOS

  1. Open the ChatBox website
  2. Download the macOS build
  3. Move it into Applications
  4. If macOS shows a security prompt on first launch, complete the usual allow flow

​
Linux

  1. Open the ChatBox website
  2. Download the package or desktop build for your distribution
  3. Install it and launch ChatBox
If your only goal is to verify that Crazyrouter works in ChatBox, start with the desktop app and postpone multi-device sync, knowledge-base imports, and large model lists until the basic chat path is stable.
The exact labels may vary slightly by ChatBox version. Common entry points include:
  • Settings
  • Model Provider
  • AI Provider
  • Add
If your current version already includes OpenAI API, select it directly. If not, add a new OpenAI API Compatible provider.

​
Configuration Steps

1

Step 1: Create a dedicated Crazyrouter token for ChatBox

On the first pass, only allow one or two models such as:
  • gpt-5.4
  • claude-sonnet-4-6
A small model scope makes troubleshooting much easier.
2

Step 2: Open ChatBox settings

Launch ChatBox, then open the settings entry in the lower-left area and go to:
  • Model Provider
  • or AI Provider
3

Step 3: Select or add an OpenAI-compatible provider

Use one of these routes:
  • if OpenAI API already exists, select it
  • if not, click Add and create an OpenAI API Compatible provider
4

Step 4: Enter the Crazyrouter connection values

Recommended values:
  • API Host: https://crazyrouter.com
  • API Path: leave blank or keep the default
  • API Key: sk-xxx
If ChatBox asks for a provider name, Crazyrouter is a clear choice.
5

Step 5: Add the first model

For the first test, add only:
  • gpt-5.4
After the minimal path works, you can add:
  • claude-sonnet-4-6
  • gemini-3-pro-preview
6

Step 6: Use Check or Save for the first connectivity test

If your ChatBox version includes a Check button, use it first.If it only has Save, save the provider and then return to the main chat screen for validation.
7

Step 7: Run the smallest possible chat validation

Create a new chat, make sure the selected model is gpt-5.4, and send:
Reply only OK
If you get OK or an equivalent short answer consistently, the main ChatBox-to-Crazyrouter path is working.
Follow this order instead of enabling everything at once:
  1. Start with one token
  2. Start with one model: gpt-5.4
  3. Validate plain text chat first
  4. Add a second model later
  5. Enable knowledge base, file Q&A, or more advanced settings only after chat is stable
ScenarioRecommended modelWhy
First connectivity testgpt-5.4Verified successfully in production on March 23, 2026, and best suited for the OpenAI-compatible baseline
Higher-quality writing and explanationclaude-sonnet-4-6Better for detailed explanation, rewriting, and summaries
Gemini fallback pathgemini-3-pro-previewUseful as a second vendor-compatible validation path inside the same client

​
How To Use ChatBox Features With Crazyrouter

​
Basic chat

This is the best first test and should always come before advanced features.

​
Knowledge base / file Q&A

Turn this on only after basic chat already works. For the first pass:
  • keep files small
  • keep content simple
  • test with one file first
Do not start with a large knowledge-base import before confirming the API configuration itself.

​
Multi-model switching

Useful when you want different models for different tasks, for example:
  • default baseline chat: gpt-5.4
  • important summaries and writing: claude-sonnet-4-6
  • secondary vendor validation: gemini-3-pro-preview

​
Parameter Suggestions

If your ChatBox version exposes common generation settings, keep the first run conservative:
ParameterSuggested valueNotes
Temperature0.2 to 0.7Keep it moderate during validation
Max Tokensdefault or moderateAvoid very large outputs during troubleshooting
Context MessagesdefaultBasic chat validation is enough at first

​
Token Best Practices

SettingRecommendationWhy
Dedicated tokenRequiredDo not share it with IDEs or automation tools
Model allowlistStrongly recommendedStart with only one or two models
Spending limitStrongly recommendedKnowledge-base or repeated Q&A flows can amplify cost
Environment separationRecommendedSeparate personal desktop usage from team-shared usage
Leak responseRotate immediatelyReplace the key if it appears in screenshots, recordings, or screen sharing

​
Validation Checklist

  • ChatBox is installed and launches normally
  • A dedicated Crazyrouter token was created for ChatBox
  • OpenAI API or OpenAI API Compatible is selected
  • API Host is set to https://crazyrouter.com
  • API Path is left blank or kept at the default
  • sk-xxx was entered successfully
  • Only gpt-5.4 was added for the first pass
  • Validation succeeded through Check or a minimal chat
  • The request appears in Crazyrouter logs

​
Common Errors And Fixes

SymptomCommon causeFix
401 unauthorizedToken is wrong, incomplete, or expiredGenerate a new token and paste it again
404Host or path is wrongReset Host to https://crazyrouter.com and keep the path default
403 / model not allowedThe token does not allow the selected modelAllow that model in Crazyrouter token settings
model not foundThe model name is wrongSwitch back to gpt-5.4 and revalidate
Save succeeds but chat failsWrong provider type or the model was not actually addedRecheck the provider mode and model list
Knowledge-base Q&A is slow or failsFiles are too large or the task is too complexFall back to smaller files and plain text chat
Not sure whether /v1 is requiredCurrent ChatBox versions usually do not need a manually forced full pathStart with the root host and leave API Path blank or default

​
FAQ

​
Which provider should I select in ChatBox?

Prefer OpenAI API or OpenAI API Compatible.

​
What should I enter as the API Host?

Use https://crazyrouter.com.

​
Do I need to manually enter /v1/chat/completions?

Usually no. Based on ChatBox’s official provider documentation, API Path typically already has a default value, so leave it blank or unchanged first.

​
What should the first model be?

Start with gpt-5.4.

​
When should I add more models or knowledge-base features?

Only after the minimal chat path is already working.
If your goal is “make ChatBox work first”, the best approach is not to configure many models and features at once. Start with gpt-5.4 and validate the smallest possible chat path.