CC Switch API setup guide

Use the one-click import in the qionggeme console to send the provider, endpoint, model, and API key to CC Switch. If import fails, configure the official provider fields manually.

Quick configuration

Recommended starting point
https://qionggeme.com/console/token
Open the action menu for an API key and choose “CC Switch”.
Import protocol
ccswitch://v1/import
The link may contain an API key. Never paste it into public chats, tickets, logs, or screenshots.
Codex endpoint
https://qionggeme.com/v1
Native Responses protocol; no local route mapping is required.
Claude / Gemini endpoint
https://qionggeme.com
Imported state
enabled=true
After importing, still confirm that the target provider is enabled.

Before you begin:

Setup steps

  1. Open the qionggeme API key page

    Visit https://qionggeme.com/console/token, find the API key you want to import, and choose CC Switch from that row’s action menu. Do not copy the secret-bearing URL from the browser address bar afterward.

  2. Choose the target app, provider name, and primary model

    In the dialog, choose Claude, Codex, or Gemini, enter a recognizable provider name, and select the primary model. The model ID must exactly match a currently available ID on the pricing page.

  3. Click “Open CC Switch”

    The console generates a ccswitch://v1/import Deep Link and asks the operating system to open CC Switch. The generated data includes apiKey, model, homepage, and enabled=true. The Codex endpoint is https://qionggeme.com/v1; the Claude and Gemini endpoint is https://qionggeme.com.

  4. Review and confirm the import in CC Switch

    CC Switch displays an import confirmation screen. Check the app type, provider name, endpoint, and model before approving it. The official protocol requires a preview and explicit user confirmation. Cancel if the source is untrusted or any field looks wrong.

  5. Confirm the provider is enabled and restart the target CLI

    Return to the provider list for the selected app and confirm that the imported provider is enabled. If Claude Code, Codex, or Gemini CLI was already running, close and relaunch it so the process reads the new configuration. Codex’s official switching guide specifically requires reopening the terminal after a switch.

  6. Add the provider manually if one-click import fails

    Add a custom provider in the corresponding CC Switch app tab:

    • Codex tab: set the endpoint to https://qionggeme.com/v1, enter the API key and model, and use native responses. Local route mapping is not required.
    • Claude tab: set the endpoint to https://qionggeme.com, enter the API key and model, save, and enable the provider.

    Manual endpoints must never use the content-site URL or include /docs.

Configuration example

# Security checklist (does not expose a real API key or full Deep Link)
Protocol: ccswitch://v1/import
resource: provider
Codex endpoint: https://qionggeme.com/v1
Claude/Gemini endpoint: https://qionggeme.com
Fields: apiKey, model, homepage, enabled=true

# Manual Codex fallback
Base URL: https://qionggeme.com/v1
Wire API: responses
Local route mapping: not required

Troubleshooting

Clicking “Open CC Switch” does not launch the app

Confirm that CC Switch is installed and has been launched at least once. Its installer registers the ccswitch:// protocol. If the protocol is not registered correctly, reinstall or repair it using the official Deep Link guide, then start the import again from the API key page.

CC Switch reports an import failure or missing field

Do not manually edit a link containing the key. Return to the console, select the app, provider name, and primary model again, and reopen it. If it still fails, use the manual fallback above. The endpoint must be https://qionggeme.com/v1 or https://qionggeme.com as appropriate and must not contain /docs.

Import succeeds, but the target CLI still uses the old provider

Confirm the new provider is enabled in CC Switch, then completely exit and restart the target CLI. For Codex, close the current terminal window and open a new one.

Codex requests fail, or I think local routing must be enabled

Verify that the Codex endpoint is https://qionggeme.com/v1 and the protocol is native responses. qionggeme does not require CC Switch local route mapping. Translation is only needed when an upstream does not natively support Responses, such as a Chat Completions-only or Anthropic Messages-only endpoint.

I get 401, insufficient balance, or model-not-found errors

Check that the API key is active, the token has the required permissions and balance, and the model ID matches the model pricing page. Never post the key or a key-bearing Deep Link in a public support channel.

Ready to get started?

Create a qionggeme account, generate an API key, and access every currently available model.

Create an account

Frequently asked questions

Which fields does the CC Switch one-click import write?

The qionggeme provider import includes apiKey, model, homepage, and enabled=true. It sets the endpoint by app: https://qionggeme.com/v1 for Codex and https://qionggeme.com for Claude or Gemini.

Can I send a ccswitch:// import link to someone else?

Do not share a Deep Link that contains an API key. Query parameters may expose the secret through public chats, tickets, screenshots, browser-history synchronization, or logs. Remove sensitive fields and have collaborators use their own keys.

Why does Codex not need local route mapping?

The qionggeme Codex endpoint https://qionggeme.com/v1 natively supports the Responses protocol. Enter the Base URL, API key, and model directly. Only non-Responses upstreams require local protocol conversion.

Why does the imported provider not take effect immediately?

First confirm that it is enabled. A running CLI may still hold the old configuration and must be restarted. Codex’s official switching instructions require closing and reopening the terminal.

Can the endpoint use the content-site /docs URL?

No. Codex uses https://qionggeme.com/v1; Claude and Gemini use https://qionggeme.com. An API endpoint must never include /docs.

Related guides

Codex CLI custom API setup guide

Use Codex’s official custom model provider configuration to connect to 穷哥么. The provider uses the Responses API, while the secret remains in an environment variable.

Read guide →

Claude Code custom API setup guide

Set environment variables so Claude Code uses the qionggeme gateway and Claude models billed through your qionggeme API balance.

Read guide →

Cockpit Tools custom API setup guide

Cockpit Tools manages Codex profiles. Follow the full sequence—add provider, bind it to an instance, then enable and start—to make Codex actually use the qionggeme API.

Read guide →