qoder2api-hub is a self-hosted, MIT-licensed Python gateway that turns Qoder's domestic (qoder.com.cn) and international (qoder.com) accounts into OpenAI- and Anthropic-compatible API endpoints, built for developers who want to reach Qoder-hosted models from Codex CLI, Claude Code, or any standard OpenAI client.

What it is

The project is a multi-account reverse proxy for Qoder, the coding platform whose user base is served by two separate regional sites. It lives squarely in the OpenAI-compatible API ecosystem and exposes each account pool across three protocol surfaces at once: OpenAI Chat Completions, the Responses API used by Codex, and Anthropic Messages for Claude Code. It is written in Python and uses only the standard library, with COSY signing and AES/RSA implemented in pure Python, and it is also published as amd64 and arm64 Docker images.

The concrete thing it replaces is the official Qoder client as the access path. Qoder credentials and tokens normally live on one logged-in device, and each account's credits, model list, pricing and thinking tiers are managed from there, one account at a time. The gateway imports those credentials instead — through OAuth device authorization, a PAT, or by taking the credentials of a locally logged-in official client — refreshes tokens on a schedule, and pools several accounts per region. It then publishes the official model catalogue at /v1/models, so what a caller sees is a single base URL backed by a pool of accounts rather than a client somebody has to keep open.

Key capabilities

• Three protocol surfaces on one port: OpenAI Chat Completions, the Responses API used by Codex, and Anthropic Messages for Claude Code, which connects to http://127.0.0.1:8790 without the /v1 suffix.
• Dual-region account pools with separate egress for the domestic and international sites, automatic region selection by model, account rotation, session affinity, and failover to a cooled-down spare.
• Client-free credential onboarding through OAuth device authorization, PAT import, or import from a logged-in official client, plus scheduled token refresh and automatic daily Credits check-in.
• A model catalogue pulled dynamically from the official list, carrying peak and off-peak pricing, context window, thinking tiers and the reason a model is disabled.
• Anti-risk-control shaping: outbound identity aligned with the official client, an optional per-account concurrency gate and request pacing, and /health telemetry for queueing, throttling and rejection signals.
• A web dashboard on the same port covering accounts, usage and performance metrics, request logs, quota guards, and one-click agent configuration for Claude Code, Codex CLI, OpenCode, DSH and Crush that backs up existing config first.

Who uses it and how

• Individual developers on a workstation, starting it with start-qoder-proxy.bat on Windows (logs to qoder-proxy.log) or start-qoder-proxy.sh on Linux and macOS (writes qoder-proxy.pid) and calling 127.0.0.1:8790.
• Small groups sharing one gateway across a LAN, where docker compose up -d starts in LAN mode, enforces an API key generated on first start, and exposes it through docker compose logs qoder-proxy | grep -i "api key".
• Agent-driven coding setups, since Claude Code, Codex CLI, OpenCode, DSH and Crush each get a documented base URL and protocol pairing and can be written from the dashboard.
• Hosts that sit behind an egress proxy or in a datacenter, which the deployment and risk-control documents address directly.

Getting started

Python 3.9+ or Docker is required: clone the repository, then run start-qoder-proxy.bat, chmod +x *.sh && ./start-qoder-proxy.sh, or docker compose up -d. The API then answers at http://127.0.0.1:8790/v1 and the dashboard at http://127.0.0.1:8790/ with the default password admin.

How it compares

The facts supply no list of paid products, so the nearest reference points are the tools named in the README: the related WorkBuddy2API Panel governs a wider spread of platforms, including WorkBuddy, CodeBuddy, Trae, MiniMax, Doubao and Huawei Cloud CodeArts alongside Qoder behind one OpenAI-compatible gateway, whereas this project concentrates on Qoder's two regions alone. The credited projects mmqz/cpa-multi-plugins, Liki4/qodercli2api and Sliverkiss/workbuddy2api supplied the dual-region constants, OAuth and COSY signing work and protocol reverse-engineering that this gateway assembles into a dashboard-driven product.

When to use it — and when not to

Self-hosting means running a Python or Docker host, moving the dashboard off the default admin password, and accepting that upstream risk controls still bite: the project's own documentation notes that multiple accounts can still queue, and its internals rest on conclusions reverse-engineered from the official client, which can change without notice. It ships no accounts or credits, and its disclaimer rules out commercial resale and malicious concurrency, so anyone needing a vendor-supported or officially sanctioned integration should look elsewhere.

git clone https://github.com/shuishuipingan/qoder2api-hub.git
cd qoder2api-hub

curl http://127.0.0.1:8790/v1/chat/completions \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model": "Qwen3.8-Flash", "messages": [{"role": "user", "content": "你好"}]}'