StackMap
Subscribe

9router vs CLIProxyAPI

Self-hosted gateway pointing any AI coding CLI (Claude Code, Codex, Cursor, Cline) at 40+ providers, with subscription→cheap→free auto-fallback and tool_result compression for 20-40% token savings. — versus — Turns your coding-CLI subscriptions (Claude Code, Codex, Antigravity, Kimi, Grok) into a local OpenAI/Gemini/Claude-compatible API — multi-account rotation in one Go proxy.

The curated verdict

Two directions of the same arbitrage: 9router points coding CLIs at 40+ providers; CLIProxyAPI exposes your CLI subscriptions as an OpenAI/Claude/Gemini-compatible endpoint for any client.

9routerCLIProxyAPI
Stars22k43k
Forks3.8k6.8k
LanguageJavaScriptGo
LicenseMITMIT
Last activity7 days agotoday
Topicsgateway, codinggateway
Curated connections62

9router — the curator's take

The 'never hit a rate limit again' gateway: run it on localhost, point Claude Code / Codex / Cursor / Cline / Copilot at its OpenAI-compatible endpoint, and it round-robins your accounts and cascades Subscription → cheap ($0.2-0.6/1M) → free (Kiro, OpenCode) providers so a job never dies mid-flight, while RTK compresses tool_result payloads (git diff, grep, ls) to shave 20-40% of tokens. Best when you juggle several provider subscriptions/keys and keep exhausting quota. NOT for you if you want one stable premium model (free-tier fallbacks vary in quality/availability), if routing traffic through third-party free providers raises data-privacy concerns, or if you want savings from smarter code retrieval rather than payload compression. Overlaps heavily with lynkr — pick 9router for free/multi-account fallback breadth, lynkr for tool-stripping, semantic caching and local-model routing.

CLIProxyAPI — the curator's take

The inverse of a router: 9router points CLIs at providers, CLIProxyAPI exposes your subscription OAuth accounts AS a provider — any SDK can spend your Claude Code/Codex/Kimi quota. Multi-account balancing built in. ToS gray zone: unofficial client re-use; firewall it, don't resell it.