CLIProxyAPI exposes OpenAI/Gemini/Claude/Codex/Grok compatible endpoints via a proxy, supporting multiple accounts, load balancing, streaming options, function calls, and multimodal input. It includes OAuth logins for several providers and a Go SDK for embedding the proxy.
Collecting history — the radar snapshots this repo daily. The trend line appears after 3 days of data (1 so far).
What it is
CLIProxyAPI is a proxy server that provides OpenAI/Gemini/Claude/Codex/Grok compatible API interfaces for CLI models. It supports multiple providers and accounts, with features such as streaming, non-streaming, WebSocket responses, function calling/tools, multimodal input, and multi-account load balancing. It also offers an OpenAI Codex/Claude Code/Grok Build workflow via OAuth logins and a reusable Go SDK for embedding the proxy.
How it works
The project acts as a middleware layer that translates between clients using OpenAI/Gemini/Claude/Codex/Grok compatible requests and the underlying provider models. It supports multiple accounts with round-robin load balancing across Gemini, OpenAI, Claude, and Grok, and provides both streaming and non-streaming response modes where supported. It includes OAuth-based login flows for Codex, Claude Code, and Grok Build, and supports tool usage and function calling. Multimodal input (text and images) is supported, and there are upstream provider configurations (OpenRouter-compatible) via config.
Getting started
Getting started guidance is provided via CLIProxyAPI Guides: https://help.router-for.me/.
Recent releases
The latest releases include v7.2.119 (2026-08-04) with Linux release assets such as CLIProxyAPI_<version>linux<arch>.tar.gz. Prior releases v7.2.118, v7.2.117, v7.2.116, and v7.2.115 share the same Linux release asset naming pattern in the visible release notes.
Traction
Stars: 46140 Forks: 7179 Open issues: 380
Behind the repo
No company or startup link is provided in the visible facts.
Caveats
License: MIT Created: 2025-07-01 Last push: 2026-08-04 Languages: Go The README mentions a management API and usage statistics sections, noting that built-in usage statistics were removed since v6.10.0 and suggesting external options such as CPA Usage Keeper and CPA-Manager-Plus for statistics.