Using Lingxi AI Plaza in ChatBox

ChatBox is an open-source AI client that supports Windows, macOS, Linux, iOS, Android, and Web. It supports custom service providers of the "OpenAI API" type, allowing direct access to Lingxi AI Plaza. This article describes the configuration process.

Application Process

To access Lingxi AI Plaza in ChatBox, first go to the Lingxi AI Plaza Console to obtain your API Token for backup.

Get Lingxi AI Plaza API Key

If you are not logged in or registered, you will be automatically redirected to the login page inviting you to register and log in. After logging in or registering, you will be automatically returned to the current page.

There is a free quota available for first-time applicants, allowing you to experience Lingxi AI Plaza's model services for free.

Download ChatBox

Go to the ChatBox official website to download by platform, or use the portable Web version directly:

  • Desktop: Windows .exe, macOS .dmg (distinguishing Intel / Apple Silicon), Linux AppImage
  • Mobile: App Store, Google Play, direct link for Android on the official website

Configure Lingxi AI Plaza

Start ChatBox and go to Settings → Model, select OpenAI API for "Model Provider" (do not select Azure or Custom), then fill in:

Field Value Description
API Key Your Lingxi AI Plaza Token Token copied from the console
API Host https://api.acedata.cloud Only fill in the root domain, do not include /openai or /v1
API Path /v1/chat/completions ChatBox defaults to /chat/completions, must be manually changed to this

The request path for ChatBox is {API Host} + {API Path}, so the Host should only include the root domain:

API Host Final Request Result
https://api.acedata.cloud https://api.acedata.cloud/v1/chat/completions Correct
https://api.acedata.cloud/openai https://api.acedata.cloud/openai/v1/chat/completions 404 (/openai does not have /v1)
https://api.acedata.cloud/openai/v1 https://api.acedata.cloud/openai/v1/v1/chat/completions 404

ChatBox will not automatically call /v1/models, you need to manually enter the model ID in the "Custom Model" input box at the bottom of the model settings page (one per line), and save it to select from the model dropdown in the chat interface.

Select Model

The model directory will continue to be updated. Prefer using the model list automatically loaded by the client; if manual entry is needed, first request GET https://api.acedata.cloud/v1/models to get the current model ID, then choose based on the context, image, and tool invocation capabilities supported by the client.

Verify Integration

If you are unsure whether the issue lies with ChatBox 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": "MODEL_ID",
    "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.

Frequently Asked Questions

Prompt 404 Not Found

This is usually due to the API Host having an extra /openai or /v1. The Host should only be https://api.acedata.cloud, and the path should default to /v1/chat/completions.

Prompt 401 / token_mismatched

Please confirm that the "API Key" pasted is the Lingxi AI Plaza Token (without the Bearer prefix and no extra spaces), and that the balance of the associated application is sufficient.

ChatBox does not automatically pull the model list; you must manually enter the model ID in the "Custom Model" box and save it.

Want to generate images in ChatBox

Lingxi AI Plaza's image generation is a separate Images API (/openai/images/generations), with a different path from the chat interface, and the image entry in ChatBox cannot be directly connected. For drawing, please refer to the Image Generation API documentation for curl / SDK calls.

Learn More