A shared pool of subscription accounts with CLIProxyAPI

Why you need this

A proxy service on top of the subscriptions solves two problems.

Problem 1 — one account for several people without a ban. The vendor blocks an account that works from several devices and IPs. Through the proxy, all requests come from one server under one authorization: to the vendor it is one client, while any number of people sit behind it, each with their own API key.

Problem 2 — several accounts as one. Subscription limits burn fast. The pool is exposed to clients as one entry point, and the service itself moves requests to a fresh account when the current one runs out of quota.

The service accumulates OAuth authorizations of subscriptions (Claude, OpenAI, Gemini, Kimi, Grok) and API keys of providers such as OpenRouter, accepts requests over an OpenAI-compatible API and the native Anthropic and Gemini protocols, and serves one model list. Installation is in the README, details at help.router-for.me.

What to know before you start

You cannot use Anthropic models from Codex, or OpenAI models from Claude Code, because the OpenAI and Anthropic protocols differ: the proxy translates formats, but tool calling, thinking and caching work differently, and cross-use is unstable. The working combination: Claude Code — Claude models, Codex — OpenAI models, the rest of the pool — from harnesses with an open provider choice.

Clients have to be switched. Claude Code and Codex go to the vendor under your login by default. To route requests through the pool, the client is pointed at the proxy address — the three folds below.

Some account features are lost. Anything bound to the vendor account is unavailable through the pool: artifact sharing, cloud sessions and tasks, history sync across devices. Authorization lives on the proxy server; the client needs only the address and a key.

Where to run it

The Management Center panel opens at https://<domain>/management.html. In it:

• Auth Files — adding accounts, OAuth login right from the browser;
• AI Providers — API-key providers (OpenRouter and others);
• Config → api-keys — keys for members, one per person or machine, so access is easy to revoke.

The service has no built-in usage statistics — for that, run a separate dashboard such as cpa-usage-keeper.

Switch the clients

Three kinds of setup: Claude Code, Codex, and anything that speaks an OpenAI-compatible API.

{
  "env": {
    "ANTHROPIC_BASE_URL": "https://<domain>",
    "ANTHROPIC_AUTH_TOKEN": "<your-key>",
    "CLAUDE_CODE_ENABLE_GATEWAY_MODEL_DISCOVERY": "1",
    "API_TIMEOUT_MS": "600000"
  }
}

model = "gpt-5.6-sol"
model_provider = "cliproxyapi"

[model_providers.cliproxyapi]
name = "OpenAI"
base_url = "https://<domain>/v1"
wire_api = "responses"
requires_openai_auth = true
experimental_bearer_token = "<your-key>"

export OPENAI_BASE_URL="https://<domain>/v1"
export OPENAI_API_KEY="<your-key>"

{
  "$schema": "https://opencode.ai/config.json",
  "provider": {
    "pool": {
      "npm": "@ai-sdk/openai-compatible",
      "name": "Team pool",
      "options": {
        "baseURL": "https://<domain>/v1",
        "apiKey": "{env:POOL_API_KEY}"
      },
      "models": {
        "claude-opus-5": { "name": "Claude Opus 5" },
        "gpt-5.6-sol": { "name": "GPT 5.6" }
      }
    }
  }
}