client/claude-desktop

Claude Desktop

Mac and Windows. Steps are identical except where the menus live — macOS uses the system menu bar, Windows uses the top-left dropdown inside the window.

§00

Before you start

mode/hosted

Hosted users — you already have everything you need. Your short code does auth; mappings are pre-configured.

mode/your-key

Your-key users — configure at least one model mapping in the dashboard first. The Gateway URL is only useful once mappings exist.

What you'll paste
Gateway URL — your Hosted base URLhttps://hosted.reapi.net
API key — your short code (the 8-character one)
Gateway URL — your BYOK base URL (includes your short code in the path)https://byok.reapi.net/{code}/anthropic
API key — your own provider API key (e.g. the DeepSeek or Qwen key you configured your mappings against)
§01

Enable developer mode

Open Claude Desktop. From the menu bar, go to Help → Troubleshooting → Enable developer mode. The app relaunches automatically and the Developer menu appears.

Windows: the menu bar lives under the top-left dropdown inside the Claude window.

fig.01 · screenshot

Enable developer mode

coming soon
§02

Open Configure Third-Party Inference

From the Developer menu, pick Configure Third-Party Inference. A full-window settings panel opens with Connection as the first tab.

fig.02 · screenshot

Open Configure Third-Party Inference

coming soon
§03

Pick Gateway (Anthropic-compatible)

Under Connection, choose Gateway — Anthropic-compatible. Leave Bedrock, Vertex, and Foundry alone; those are other cloud providers, not reAPI.

fig.03 · screenshot

Pick Gateway (Anthropic-compatible)

coming soon
§04

Fill in Gateway credentials

Paste your Gateway base URL and your API key. Leave Gateway auth scheme on the default, Bearer — x-api-key is the Anthropic-direct path, not the gateway path.

Gateway base URL (Hosted)
https://hosted.reapi.net
Gateway base URL (your-key)
https://byok.reapi.net/{code}/anthropic
Replace the curly-brace placeholder with your 8-character short code.
§05

Add the models you want to send

Scroll to Identity & Models and add one entry per model name you want the picker to show. Each entry must match the from-name side of a mapping in your dashboard — whatever claude-* name your client will send. Claude Desktop filters entries through a claude-* pattern, so the name has to start with claude-.

If the upstream model behind a mapping supports a 1M-token context window, toggle Offer 1M-context variant on for that entry.

The first entry becomes the picker default, so put your most-used model at the top.

fig.04 · screenshot

Add the models you want to send

coming soon
§06

Optional — hide the Anthropic sign-in

At the bottom of Identity & Models there's a Hide Anthropic sign-in toggle. Flip it on if you want the login screen to show only your gateway; leave it off if you also sign in to Claude directly sometimes. Reversible from this same screen later.

§07

Apply locally

The bottom bar reads Connection needs N fields while anything is missing; once everything's filled it turns into the Apply locally button. Click it.

A Relaunch Claude? prompt appears — hit Relaunch now. Once Claude reopens, the model picker in the bottom bar shows the entries you added.

fig.05 · screenshot

Apply locally

coming soon
§99

If something's wrong

  • 01Connection test fails — double-check the base URL for typos. For BYOK, the URL must end with /YOUR-CODE/anthropic, with your 8-character short code filled in.
  • 02Model picker is empty — the Model list section wasn't saved. Every entry has to start with claude- and has to exist as a from-name in your dashboard mappings.
  • 03Requests fail with "no mapping" — the from-name you added to Claude Desktop doesn't match any mapping row in your dashboard. Fix the mapping or rename the entry.

You're done

Your client is now routing through reAPI. Head to your dashboard for mapping edits, activity, and wallet.