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

# Connect Claude Desktop to APIONE

> Configure the APIONE inference gateway, apply changes, and verify access.

Claude Desktop versions supporting third-party inference can connect to APIONE through a gateway. Availability depends on the client version, deployment, and account policies.

## Open the configuration

1. Open **Help → Troubleshooting → Enable Developer Mode** and follow the client's instructions.

![Claude Desktop Enable Developer Mode menu](https://mintcdn.com/apione/YJqu1mI7oWawp6EB/images/integrations/screenshots/claude-desktop-enable-developer-v2.png?fit=max\&auto=format\&n=YJqu1mI7oWawp6EB\&q=85\&s=558b74998ff69b19b581c72d1b98f12d)

Enable developer mode from the Help menu.

2. Open **Developer → Configure Third-Party Inference**.

![Claude Desktop third-party inference menu](https://mintcdn.com/apione/YJqu1mI7oWawp6EB/images/integrations/screenshots/claude-desktop-inference-menu-v2.png?fit=max\&auto=format\&n=YJqu1mI7oWawp6EB\&q=85\&s=b39c7c8474d06a91fe4b9a041aacc3d0)

Open third-party inference settings from the Developer menu.

## Enter APIONE settings

Select **Gateway** under **Connection**.

| Field | Value |
| - | - |
| Credential kind | `Static API key` |
| Gateway base URL | `https://api.apione.ai` |
| Gateway API key | Your APIONE API Key |
| Gateway auth scheme | `bearer` (Authorization header) |

![APIONE gateway URL and concealed static key](https://mintcdn.com/apione/YJqu1mI7oWawp6EB/images/integrations/screenshots/claude-desktop-apione-gateway-v2.png?fit=max\&auto=format\&n=YJqu1mI7oWawp6EB\&q=85\&s=3073b08fbda40404842ae2e1781e0cce)

APIONE gateway configuration

Use the root URL `https://api.apione.ai`. The client appends `/v1/models` and `/v1/messages`; adding `/v1` here duplicates the version path and can cause 404 errors.

Select **bearer** explicitly; the screenshot shows the field location, not a selected value. APIONE accepts `Authorization: Bearer YOUR_APIONE_KEY` for this gateway. Do not add a second key in custom headers. Click **Test connection**. If you see `API token has expired` or another authentication error, check the key's enabled state, expiry, group permissions, and balance in APIONE. Inspect the actual HTTP status, error body, and request identifiers. The client message alone does not prove expiry. Replace the key only if the backend confirms it is expired, disabled, or revoked. Never include the full key in logs or support messages.

Add an actual APIONE model ID supporting Anthropic Messages in the model configuration.

## Save, apply, and verify

1. Click **Save Changes**.
2. Click **Apply Changes** and follow the client instructions, including restarting if requested.
3. Select the model and send a short text message.
4. Check the APIONE request details for the model, final status, and usage.
5. Test the file operations and tools required by Code or Cowork separately.

If automatic discovery returns no models, check the actual `/v1/models` response and use a manual Model List where supported. Use a single authentication method and avoid duplicate credentials in extra headers.

***

[Integration directory](https://apione.ai/docs/en/guides/clients.md) · [Choose a model](https://apione.ai/docs/en/models/catalog.md) · [Troubleshooting](https://apione.ai/docs/en/support/errors.md)


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