// the find
router-for-me/CLIProxyAPI
Wrap Gemini CLI, Antigravity, ChatGPT Codex, Claude Code, Grok Build as an OpenAI/Gemini/Claude/Codex compatible API service, allowing you to enjoy the free Gemini 3.1 Pro, GPT 5.5, Grok 4.3, Claude model through API
A Go proxy server that intercepts the OAuth sessions of AI coding CLIs (Claude Code, Codex, Gemini CLI, Grok Build) and re-exposes them as standard OpenAI/Anthropic/Gemini-compatible API endpoints. Lets you point any API client at your paid CLI subscriptions without using per-token API keys. 37k stars puts it in genuine 'community has voted' territory.
The core mechanism is clever: it handles full PKCE OAuth flows per provider and manages multi-account pools with round-robin balancing, so you can spread load across several subscriptions transparently. The plugin system is unusually well-designed — plugins are native shared libraries (Go, C, Rust) loaded at runtime, not just HTTP middleware hooks, which gives you low-overhead interception at the auth, request, and response layers. The Go SDK is extractable and documented, so the proxy logic can be embedded rather than deployed standalone. The downstream ecosystem (20+ projects) is a real signal — it means the Management API and OAuth abstractions are stable enough for others to build on.
The whole thing is load-bearing on reverse-engineered, undocumented OAuth flows — the presence of `utls_transport.go` in the Claude auth package means they're TLS-fingerprint-spoofing to evade detection, which tells you exactly how fragile the Anthropic integration is and that it likely violates ToS outright. The README description lists model versions that don't exist ('GPT 5.5', 'Grok 4.3', 'Gemini 3.1 Pro') — either aspirational placeholders or inflated marketing, neither is confidence-inspiring. More than half the README is sponsor advertisements for third-party paid relay services, some offering 90% discounts on subscriptions that shouldn't be resellable, which creates an uncomfortable ToS laundering dynamic. Usage statistics were yanked in v6.10.0 and fragmented across four separate third-party tools with no official replacement — if you need cost tracking for a team deployment, you're assembling it yourself.