Before you start
- Get an application API key from the Ace Data Cloud console. Check the selected model’s access, current price, and balance. A restricted key needs both
/v1/modelsand/v1/chat/completions. - Use an Open WebUI administrator account to add the server-side connection and grant model access. Authorized users share this connection’s key and can consume its Credits. Do not paste a key into chat messages or screenshots.
Add the connection
- Open Open WebUI. In the user menu, choose Admin Panel → Settings → Connections.
- Under OpenAI API → Manage OpenAI API Connections, click Add Connection (
+). - Leave Connection Type at External. Set URL to
https://api.acedata.cloud/v1(no trailing slash), Auth to Bearer, and API Key to your application key. Leave API Type at Chat Completions. - Click Verify Connection. It checks the
/v1/modelsendpoint; the button is optional when you save. Click Save in the connection dialog, then Save in the main Connections settings if prompted. - In Admin Panel → Settings → Models, grant the intended users or group Read access to each model. Then, as an authorized user, start a new chat and select a current Chat Completions model. Send
Reply with the single word OK.Check the completed reply and the corresponding usage record.
+) and save. This allowlist controls discovery; it does not replace each model’s Read permission. Seeing an ID does not prove support for images, tools, or other protocols.
Check the request and solve problems
The URL already contains/v1; Open WebUI appends /models or /chat/completions. Do not enter the full chat endpoint or /openai/v1 as the connection URL. Verify Connection checks discovery; only a completed chat proves the chat route. If an ordinary user sees no models, check Read grants separately from application access, key validity, and balance.
Disable any unused default connection to avoid selecting or probing it. The Ace key stays in the server-side connection settings; restrict server and model access. A personal-key model Pipe or service Tool has its own user settings and permissions; the shared connection does not populate those keys.
Each model request can consume Credits. Title, tag, and follow-up generation can send additional requests; disable these features for a controlled first check. Match charges in usage history by key and time window. An accepted media task is not a finished result; this text-chat quickstart does not validate media, files, Community tool publication, or every model.
For connection rules, see Open WebUI’s official compatibility guide. Continue with the full setup guide or Chat Completions schema.

