Claude Desktop Third-Party Inference Gateway Configuration Guide

This guide configures the Third-Party Inference Gateway for Claude Desktop, not Claude Code, and not the MCP Connector for Claude Desktop.

1. Obtain API Key

Open the Ace Data Cloud application list, go to the available applications, and copy the API Key.

Obtain Ace Data Cloud API Key

2. Enable Developer Mode

In the Claude Desktop menu, open Help → Troubleshooting → Enable Developer Mode.

Claude Desktop Enable Developer Mode

Public tutorial screenshot, used only for locating the menu; the interface may vary slightly between different versions.

3. Open Third-Party Inference Configuration

After enabling, open Developer → Configure Third-Party Inference….

Claude Desktop Open Third-Party Inference

Public tutorial screenshot, used only for locating the menu; the interface may vary slightly between different versions.

4. Configure Gateway

Select Gateway, then fill in:

Field Value
Gateway base URL https://api.acedata.cloud
Gateway API key The API Key just copied
Gateway auth scheme bearer
Credential kind Static API key

Claude Desktop Gateway Configuration Interface Example

Interface example (not a real-time screenshot): Based on public tutorial images, only the gateway address is replaced through GPT Image 2, with the Key masked. It is used to illustrate the field positions and does not serve as proof of successful connection.

Click Test connection; after the test passes, click Apply Changes. If prompted to restart the application, please restart as instructed, then select the desired Claude model from the available models.

5. Verification

Create a new conversation and send Reply only OK. Then perform a simple tool task; call records can be viewed in the Usage History.

The actual check on the Ace Data Cloud Anthropic interface on September 8, 2026, covered /v1/models, Bearer authenticated streaming /v1/messages, tool calls, and tool_result continuation. The response also retains the prompt cache usage field; both the cache write and read values in this check are 0, thus not indicating a cache hit.

401 usually indicates an incorrect Key; if the model cannot be found, first retest the connection and restart Claude Desktop. When reporting issues, provide the trace ID from the call records, do not provide the API Key.

References

Return to the Coding Plan Configuration Center.