Importing Desktop Client Config with CC Switch

Manual configuration is not hard — it is just easy to mistype. One extra /v1, one dropped character, an Anthropic-group key pasted into an OpenAI field: each one sends you back and forth between 401 and 404 with no clear signal which is which.

The CC Switch import removes that transcription step.

What it does

On the API Keys page in the console, select a key and click Import to CC Switch. The platform generates configuration matching that key's own protocol group — an Anthropic-compatible key produces Anthropic-shaped config, an OpenAI-compatible key produces OpenAI-shaped config.

In other words, the two things most likely to go wrong — whether the group matches the endpoint, and whether the base URL should carry /v1 — are filled in from the key's real properties instead of from memory.

How to use it

1. Sign in to the console and open API Keys
2. Select the key you want to use (create one first if needed, minding the protocol group)
3. Click Import to CC Switch
4. Confirm the import in CC Switch

Once imported, switch to that profile in CC Switch and you are done.

About key safety

The import link is generated in your current browser, and the real key never appears on any public page. In practice that means:

• You must be signed in to see the entry point — there is no key material on the page when signed out
• The generated link carries credentials. Do not forward it, and do not paste it into a group chat or a ticket
• To set up a colleague, have them sign in and generate their own key rather than sharing your link. That also keeps usage and quotas separate per person

When you still configure by hand

The import covers desktop clients managed by CC Switch. These cases still need manual setup:

• Running on a server or in CI, with no desktop client
• Calling the API from your own code with an SDK
• Clients that CC Switch does not manage

For those, see the Claude Code, Codex and SDK guides on this blog.

After configuring

Whichever route you take, do the same last step: send one request, then check the usage records in the console.

If the record is there, the request genuinely went through ROIBest AI. If there is no record but the client works fine, the configuration did not take effect and the client is still using its previous credentials — a state that is invisible from the client side.