Use QCode with 9router

Add QCode.cc as a custom provider in 9router, a local multi-provider router, for cross-provider fallback and unified management

Need an API key? Sign up →·Endpoints & base URLs →

9router is a local multi-provider AI routing proxy: it runs an OpenAI-compatible service on your own machine (default http://localhost:20128/v1), takes over requests from tools like Claude Code, Cursor, Cline, and Codex, and forwards them to multiple model providers according to your rules (including automatic fallback / switching when a quota is exhausted / output compression to save tokens, etc.). Conceptually it's similar to QCode's own CCR — the difference is that 9router runs on your own machine and is managed by you.

For exact features, ports, and UI, refer to the 9router official repo; this article only covers "how to add QCode to it".

When you need it¶

• Connecting to QCode directly is simpler: if you only use QCode, just point your tool's BASE_URL at api.qcode.cc — you don't need 9router.
• When 9router makes sense: when you want to mix QCode with other providers (subscription plans, promotional credits, self-hosted, etc.) and need a unified entry point, automatic fallback, cross-provider switching, or token compression, you can register QCode as one of 9router's providers (as the primary or as a fallback layer).

Add QCode as a provider¶

1. Start 9router per its docs and open the local console (default http://localhost:20128).

2. Under Providers, add a custom / OpenAI-compatible (Compatible Node) provider:

3. Endpoint / Base URL:

   • Chat (GPT family): https://api.qcode.cc/openai/v1
   • Chat (Claude family, if 9router supports Anthropic-protocol nodes): https://api.qcode.cc/api
   • Image (optional): https://api.qcode.cc/qcode-img/v1 (see the note below)
   • In mainland China, swap the domain for asia.qcode.cc (the nearby Asia access point).
4. API Key: your QCode API Key (starts with cr_).
5. Models / aliases: register claude-opus-5, claude-sonnet-5, gpt-6-sol, gpt-5.6-terra, etc. as needed (4.x such as claude-sonnet-4-6 remains on sale).
6. Put this QCode provider into your tier / fallback chain (e.g. as the primary, or as a fallback layer once other providers run out of quota).
7. Point your tools (Claude Code / Cursor / Cline, etc.) at 9router's local entry point http://localhost:20128/v1 — from then on 9router decides when to route to QCode.

Direct QCode vs via 9router¶

Notes¶

• Local only: 9router runs locally, and its config is not shared between team members.
• Image routing needs your own testing: 9router exposes /v1/images/generations, but "calling QCode's gpt-image-2 via 9router" is untested and may need extra configuration; if you need reliability, route images via direct image-2.
• Quotas follow the QCode dashboard: 9router's stats are not the same as your actual QCode account quota (per-Key daily limits, etc. follow the QCode dashboard / probe.qcode.cc).
• Protocol-to-path mapping: /openai/v1 uses the OpenAI protocol, /api uses the Anthropic protocol, and /qcode-img/v1 is for images — see Endpoints and API formats.

Install and the local endpoint (per the official 9router README)¶

As of 2026-10-15, the quick start in the official 9router README is: install with npm install -g 9router, start it with 9router, and open the dashboard at http://localhost:20128 by default. In the tool you want to connect, set the Endpoint to http://localhost:20128/v1 and copy the API Key from the 9router dashboard. The README also states that custom OpenAI / Anthropic compatible endpoints are supported, and that is how QCode is added.

Key settings explained¶

Common errors and how to troubleshoot¶

Hit QCode directly with curl first (section 5 of Endpoints and API formats) to confirm the key and path, then debug the 9router layer. It saves a lot of back and forth.

FAQ¶

Do I need 9router if I only use QCode?¶

No. If you only use QCode, point the tool's BASE_URL straight at api.qcode.cc (or asia.qcode.cc in mainland China). It is simpler: one fewer local proxy and one fewer place for things to go wrong.

Why does the cost shown in 9router differ from my QCode bill?¶

The figures in 9router are its own estimates based on its routing choices. QCode bills per token, with per-model rates listed at qcode.cc/models, and the QCode dashboard is what actually counts.

Can Claude Code use Claude models through 9router?¶

Only if 9router supports an Anthropic-protocol node and you have configured QCode's /api address as such a node. With only an OpenAI-compatible node, Claude models are rejected. The exact UI is described in the official 9router repository.

How do I confirm that requests passing through 9router really reach QCode?¶

Enter your cr_ key at probe.qcode.cc; if you can see the model and tokens of the request, it arrived. If not, check whether the QCode provider is in 9router's tier / fallback chain and whether it is placed early enough.

One API Key works across two protocols (Anthropic / OpenAI), whether you connect directly or through a router like 9router. Learn about QCode.cc pricing.

Enterprise →