WorkBuddy Custom Model Configuration Guide

1. Obtain an API Key

Open the Ace Data Cloud application list, enter an available application, and copy the API Key.

Obtain Ace Data Cloud API Key

2. Add a Model

In WorkBuddy, go to Settings → Models → Custom Models → Add Model, then fill in:

Field Value
Provider Custom
API Endpoint https://api.acedata.cloud/v1
API Key The API Key you just copied
Model Name Go to the model catalog to view it, and fill in the exact name of the model to call, for example, claude-opus-5, gpt-6-sol
Custom Protocol Off

WorkBuddy Custom Provider Configuration Screen

The id here is the model name used by the model parameter in API requests, not the UUID of the service, API, or Application, nor a custom display name. You can only enter ds-4.0 when the real-time catalog returns {"id":"ds-4.0"}; if it is not in the catalog, it means it is currently unavailable. Do not guess or abbreviate it.

You can first view the available models in the model catalog; if you need to confirm the exact names that the current Coding credentials can call, use the API Key you just copied to query the API catalog:

curl https://api.acedata.cloud/v1/models \
  -H "Authorization: Bearer YOUR_API_KEY"

Find the target model in the response data array, and copy its id value exactly. Configure capability switches according to the actual support of that model.

When keeping “Custom Protocol” off, WorkBuddy will complete the path according to OpenAI Chat Completions rules. Enable advanced capability switches (tools, images, reasoning) only according to the actual capabilities of the selected model; when uncertain, keep the defaults first.

3. Verify

After saving, select the newly added model in the chat model selector and send Reply only OK. Then perform a read-only file or tool task to confirm that the required capabilities are available; call records can be viewed in usage history.

If the model does not appear, confirm that the configuration has been saved and enabled; check the Key for 401; check whether the entered model name exactly matches the id in the catalog and whether the API endpoint is correct for 404. WorkBuddy’s official documentation states that the Key is stored in the local configuration, but request content will still be sent to the configured model service.

Official References