> ## Documentation Index
> Fetch the complete documentation index at: https://docs.acedata.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Claude Desktop Third-Party Inference Gateway Configuration Guide

> Claude AI integration guide - Ace Data Cloud

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

## 1. Obtain an API Key

Open the [Ace Data Cloud application list](https://platform.acedata.cloud/console/applications), enter an available application, and copy the API Key.

![Obtain Ace Data Cloud API Key](https://cdn.acedata.cloud/dvc3cg.jpg)

## 2. Open Third-Party Inference Configuration

On the Claude Desktop login page, open **Help → Troubleshooting → Enable Developer Mode** in sequence, then select **Developer → Configure Third-Party Inference…**.

![Open Third-Party Inference in Claude Desktop](https://cdn.acedata.cloud/713ffd7104a3.png)

> The image is from the Bifrost Apache-2.0 repository and is only used to locate the Claude Desktop menu; the interface may vary slightly between versions.

## 3. Configure the 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](https://cdn.acedata.cloud/68d41fe682cb.png)

Click **Apply Changes**, then click **Save & Restart**.

## 4. Verify

After restarting, select an available model, create a new conversation, and send `Reply only OK`, then perform a simple tool task. Invocation records can be viewed in [Usage History](https://platform.acedata.cloud/console/usages).

Ace Data Cloud Gateway supports `/v1/models`, Bearer-authenticated streaming `/v1/messages`, tool calling, and `tool_result` continuation used by Claude Desktop. Prompt caching fields are retained; cache write and read values both being 0 does not mean that a cache hit occurred.

A 401 usually means that the Key is incorrect; when a model cannot be found, recheck the configuration and fully restart Claude Desktop. When reporting an issue, provide the trace ID in the invocation records, and do not provide the API Key.

## Official References

* [Claude Desktop Third-Party Inference Installation and Single-Machine Configuration](https://claude.com/docs/third-party/claude-desktop/installation)
* [Claude Desktop Third-Party Inference Configuration Reference](https://claude.com/docs/third-party/claude-desktop/configuration)

Return to the [Claude App Integration Guide](https://platform.acedata.cloud/documents/mcp-tutorials-claude-desktop).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.