Create

Sign in to ReadmeX

or

How we handle your data: Privacy Policy

ReadmeX

Your AI reading companion

What would you like to catch up on?

Pick a briefing, or ask your own question.

Your community and people briefings stay personal to you.

CLIProxyAPI

CLIProxyAPI: A proxy server that provides OpenAI/Gemini/Claude/Codex/Grok compatible API interfaces for CLI.

What problem it solves

CLI users may need to access several model providers through one compatible API interface while using multiple accounts. The project addresses this by exposing provider-compatible endpoints and supporting account authentication, round-robin load balancing, streaming, tools, and multimodal inputs.

Key features

  • Provider-compatible API interfaces — Expose OpenAI, Gemini, Claude, Codex, and Grok compatible endpoints for CLI models. Clients can use these interfaces through compatible clients or SDKs.

    Source: README

  • OAuth and CLI authentication — Connect supported providers through OAuth login flows and simple command-line authentication for Gemini, OpenAI, Claude, and Grok.

    Source: README

  • Response and tool capabilities — Support streaming, non-streaming, and WebSocket responses where available, along with function calling, tools, and text and image inputs.

    Source: README

  • Multi-account load balancing — Distribute requests across multiple Gemini, OpenAI, Claude, and Grok accounts using round-robin load balancing. Dedicated multi-account balancing is also listed for AI Studio Build, Claude Code, OpenAI Codex, and Grok Build.

    Source: README

  • Embeddable Go SDK — Provide a reusable Go SDK for embedding the proxy. Documentation covers usage, advanced executors and translators, access, watchers, and custom providers.

    Source: README, docs, examples/custom-provider

Who it may suit

Inference: This may suit developers who want to route CLI model accounts through a local compatible API and need OAuth authentication, multi-account balancing, or an embeddable proxy server.

Topics to discuss

  • How should multi-account scheduling handle account-specific quotas and cooldowns?

  • Which provider and protocol combinations should receive priority for compatibility testing?

  • What configuration and observability features would be most useful for proxy operators?


Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.

Read the original README https://github.com/router-for-me/CLIProxyAPI#readme

ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.

github.comhttps://github.com/router-for-me/CLIProxyAPI

Comments

…