CLIProxyAPI vs magpie
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. — versus — Pick any model for any coding agent from one menu-bar app: a local gateway translating OpenAI, Anthropic and Gemini APIs, with subscription sign-ins and quota failover across accounts.
Both turn coding-CLI subscriptions into a local multi-protocol API with account rotation; CLIProxyAPI is the headless Go proxy, magpie adds per-agent config editing and a UI.
| CLIProxyAPI | magpie | |
|---|---|---|
| Stars | 54k | 8.6k |
| Forks | 8.3k | 565 |
| Language | Go | Go |
| License | MIT | MIT |
| Last activity | 3 days ago | yesterday |
| Topics | gateway | gateway, coding |
| Curated connections | 5 | 4 |
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.
magpie — the curator's take
Worth it the moment you run more than one agent, provider or account — Claude Code on Kimi, Codex on DeepSeek, failover when a plan runs dry, 50+ agents configured in place. Not needed for one agent on its vendor's own plan (the README says so itself). It reads your agents' stored sign-ins by default; turn account discovery off if that's a policy problem.