CLIProxyAPI vs ShareQuota
The closest sibling on this site: both are Go, both are MIT, both turn the logins of the coding tools you already have into an API. The differences are in scope and in shape.
CLIProxyAPI is a free, MIT-licensed Go service that wraps the OAuth logins of Claude Code, Codex, Gemini CLI, Antigravity and Grok Build into OpenAI-, Gemini-, Claude- and Codex-compatible endpoints, rotates across several accounts per provider, and is deployed as a binary or a Docker image with a management API. ShareQuota is a free, MIT-licensed Go binary with the same core idea — sign in to the plans you own, pool them behind one endpoint, fail over between them — applied to five providers including DeepSeek and OpenRouter API keys, with a dashboard that switches Claude Code, Codex and Gemini CLI over reversibly and a management API that only listens on localhost. CLIProxyAPI leans toward a shared service; ShareQuota leans toward one person’s machine.
Side by side
Eleven facts, read from each project’s own repository and site on 2026-09-13. Where a row favours the other tool, the row says so.
| Fact | ShareQuota | CLIProxyAPI |
|---|---|---|
| GitHub stars | — | 51,600+ |
| Written in | Go | Go |
| Licence | MIT | MIT |
| What you run | One static binary | Go binary · Docker |
| Providers reached | 5 | Claude, Codex, Gemini, Antigravity, Grok logins |
| Signs in to a subscription plan | Yes | Yes |
| Client dialects served | Anthropic, OpenAI, Responses, Gemini | Anthropic, OpenAI, Gemini, Responses |
| Coding tools named as supported | Claude Code, Codex, Gemini CLI, Cursor, Cline, Copilot | Any Anthropic, OpenAI or Gemini client |
| Built as a shared team gateway | No | Yes |
| Token compression built in | No | No |
| Runs on your machine, no service between | Yes | Yes |
Star counts are rounded down to the hundred. ShareQuota’s repository is public but new, and its count is not yet a fact worth printing.
Which one, for what
Pick CLIProxyAPI when
- You need Antigravity or Grok logins pooled, which ShareQuota does not carry.
- The proxy serves several people, and account rotation across many logins is the job.
- You want Docker and a remote management API as the deployment story.
Pick ShareQuota when
- You want DeepSeek and OpenRouter keys pooled beside the OAuth plans, with one failover order across all five.
- The tool configs should be changed for you and restored on disable — backed up first, every time.
- A management API that answers only on loopback is the security posture you want by default.
Questions about the pair
Yes, more than any other pair on this site: both wrap subscription logins as an API, both are Go, both are MIT. CLIProxyAPI goes further on account rotation and on providers such as Antigravity and Grok; ShareQuota goes further on the pooled API keys, the reversible CLI setup and the loopback-only surface.
They are level: Anthropic, OpenAI, OpenAI Responses and Gemini on both, so the same coding tools can point at either. Where they differ is upstream — which logins and keys each can pool — not downstream.
Nothing is locked in on either side: both hold credentials on your disk and both are reached at a base URL your tools already know how to change. Sign in again on the new one, point the tools at its port, and disable the old one’s CLI integration so the original config is restored.