Generic Client Setup
Any OpenAI-compatible client works out of the box. Below are the exact settings for popular tools.
Common settings (same for every client)
https://token.bitbeam.cn/v1sk-tr-••••••Create one under API KeysUse the model ID from the Model Market. Some clients require adding models manually instead of fetching the list.
Cherry Studio
OpenAICross-platform desktop client with multi-provider and knowledge base support.
| Setting | Value |
|---|---|
| Provider type | OpenAI |
| API Host | https://token.bitbeam.cn/v1 |
| API Key | sk-tr-xxxxxx |
Add a provider of type "OpenAI", then click Manage to fetch the model list automatically.
ChatBox
OpenAILightweight desktop / mobile client.
| Setting | Value |
|---|---|
| Provider type | OpenAI API Compatible |
| API Host / Endpoint | https://token.bitbeam.cn/v1 |
| API Key | sk-tr-xxxxxx |
LobeChat
OpenAIModern open-source AI chat framework, self-hostable.
| Setting | Value |
|---|---|
| OPENAI_PROXY_URL | https://token.bitbeam.cn/v1 |
| OPENAI_API_KEY | sk-tr-xxxxxx |
Set as environment variables when self-hosting, or fill them under Settings → Language Model on the hosted version.
NextChat
OpenAIOne-click deployable lightweight web client.
| Setting | Value |
|---|---|
| BASE_URL | https://token.bitbeam.cn |
| OPENAI_API_KEY | sk-tr-xxxxxx |
NextChat appends /v1 itself, so BASE_URL must be the domain only — do not include /v1.
Open WebUI
OpenAISelf-hosted web UI, often used alongside local models.
| Setting | Value |
|---|---|
| OPENAI_API_BASE_URL | https://token.bitbeam.cn/v1 |
| OPENAI_API_KEY | sk-tr-xxxxxx |
Dify
OpenAILLM app orchestration platform — bring these models into workflows and agents.
| Setting | Value |
|---|---|
| Provider type | OpenAI-API-compatible |
| API endpoint URL | https://token.bitbeam.cn/v1 |
| API Key | sk-tr-xxxxxx |
| Model name | A model ID from the Model Market, e.g. glm-5.2 |
Add under Settings → Model Provider → OpenAI-API-compatible. Each model must be added individually.
Don't see your tool?