Using Ace Data Cloud in LobeChat
LobeChat is an open-source AI client that features "modern UI + plugin ecosystem + knowledge base + one-click self-deployment." You can use the official online version (PWA) or run a private version on your own server using Docker. It natively supports custom OpenAI-compatible endpoints, allowing access to Ace Data Cloud, with one API Token accessing over 60 large models including Claude, GPT, Gemini, Grok, DeepSeek, Kimi, GLM, etc. This article describes the configuration process.
¶ Application Process
To integrate Ace Data Cloud into LobeChat, first go to the Ace Data Cloud Console to obtain your API Token for backup.

If you are not logged in or registered, you will be automatically redirected to the login page to invite you to register and log in. After logging in or registering, you will be automatically returned to the current page.
When applying for the first time, there will be a free quota provided to experience the model services of Ace Data Cloud for free.
¶ Configuring Ace Data Cloud
Go to LobeChat's Application Settings → Language Model, find the OpenAI card and enable it, then fill in:
| Field | Value | Description |
|---|---|---|
| API Key | Your Ace Data Cloud Token | Token copied from the console |
| API Proxy Address | https://api.acedata.cloud/v1 |
Must end with /v1 |
| Client Request Mode | Enabled | Direct browser connection, Key does not go through LobeChat server |
LobeChat will not automatically append /v1 to the Base URL, the request path is directly {API Proxy Address}/chat/completions:
| API Proxy Address | Actual Request | Result |
|---|---|---|
https://api.acedata.cloud/v1 |
https://api.acedata.cloud/v1/chat/completions |
Correct |
https://api.acedata.cloud/openai |
https://api.acedata.cloud/openai/chat/completions |
Also available |
https://api.acedata.cloud/openai/v1 |
https://api.acedata.cloud/openai/v1/chat/completions |
404 (/openai does not have /v1) |
https://api.acedata.cloud |
https://api.acedata.cloud/chat/completions |
404 (missing /v1) |
LobeChat will automatically call /v1/models to fetch models, and if Ace Data Cloud returns many models, the interface will be long. It is recommended to manually fill in an allow list in "Model List → Custom Model Name," separated by commas. If you need to customize the display name, you can use =, for example, gpt-5=GPT-5 Flagship Version.
¶ Recommended Models
The following model IDs have been verified as available through Ace Data Cloud GET /v1/models and POST /v1/chat/completions:
| Family | Model ID | Notes |
|---|---|---|
| GPT | gpt-5, gpt-5-mini, gpt-4o |
OpenAI flagship / Cost-effective / Classic multimodal |
| Claude | claude-opus-4-8, claude-sonnet-4-6 |
Anthropic flagship / Balanced |
| Gemini | gemini-3.1-pro, gemini-3-flash-preview |
Google multimodal / Fast |
| Grok | grok-4 |
xAI, natively connected |
| DeepSeek | deepseek-v3 |
High cost-performance, Chinese-friendly |
| Kimi | kimi-k2.5 |
Long text |
For the complete model list, please refer to the Ace Data Cloud Service Documentation.
¶ Verification of Integration
If you are unsure whether the issue lies with LobeChat or the network, you can first verify the endpoint directly using curl (replace {token} with your Token):
curl -X POST 'https://api.acedata.cloud/v1/chat/completions' \
-H 'Authorization: Bearer {token}' \
-H 'Content-Type: application/json' \
-d '{
"model": "gpt-5",
"messages": [{"role": "user", "content": "ping"}]
}'
If you receive an OpenAI-compatible chat.completion object, it indicates that both the Token and endpoint are ready; if you receive HTTP 403 used_up, it means the Token is valid but the balance is insufficient, and you can recharge at the console.
¶ Advanced: Docker Self-Deployment
If you want to deploy a private version for team use, you can start it with a single Docker command (replace {token} with your Token):
docker run -d \
--name lobe-chat \
-p 3210:3210 \
-e OPENAI_API_KEY={token} \
-e OPENAI_PROXY_URL=https://api.acedata.cloud/v1 \
-e ACCESS_CODE=your-secret-password \
-e OPENAI_MODEL_LIST="gpt-5,claude-opus-4-8,gemini-3.1-pro,grok-4,deepseek-v3" \
lobehub/lobe-chat:latest
Open http://your-server-IP:3210, enter ACCESS_CODE to use it, and team members do not need to fill in their own Key. For a complete explanation of the environment variables used above, such as OPENAI_API_KEY, OPENAI_PROXY_URL, OPENAI_MODEL_LIST, see the LobeChat Model Service Provider Environment Variable Documentation. If using nginx for reverse proxy with HTTPS, be sure to add proxy_buffering off;, otherwise, streaming responses will be buffered. For more deployment forms, please refer to LobeChat Self-Deployment Guide and Docker Compose Deployment.
¶ Frequently Asked Questions
¶ Prompt 404 Not Found
This is usually because the API proxy address is written as .../openai/v1 or is missing /v1. Change it to https://api.acedata.cloud/v1.
¶ Model List is Empty
Turn on the "Client Request Mode" switch; or manually fill in the model allow list in "Custom Model Name."
¶ Prompt 401 Unauthorized
Please confirm that the API Key pasted is the Ace Data Cloud Token (without the Bearer prefix and no extra spaces), and that the application balance is sufficient.
¶ Learn More
- LobeChat Official Website | LobeChat GitHub | Self-Hosting Documentation
- LobeChat Configuration OpenAI Provider Official Documentation
- LobeChat Model Provider Environment Variables Documentation
- Ace Data Cloud OpenAI Chat Completions API Documentation
- Ace Data Cloud Service List
- Ace Data Cloud Console
