Skip to main content

Overview

CLI Proxy API supports multiple AI providers, each with unique authentication methods, model catalogs, and capabilities.

Supported Providers

Gemini

Google’s Gemini models via OAuth, API keys, or Vertex AI

Claude

Anthropic Claude models via OAuth or API keys

Codex

OpenAI GPT models via OAuth

Qwen

Alibaba Qwen Code models via OAuth

iFlow

Z.ai GLM models via OAuth

Antigravity

Google’s code assistance platform

Kimi

Moonshot AI models via OAuth

AI Studio

Google AI Studio API keys

Vertex AI

Google Cloud Vertex AI endpoints

Provider Details

Gemini CLI

Authentication: OAuth 2.0 Models:
  • gemini-2.5-pro - Latest Pro model
  • gemini-2.5-flash - Fast Flash model
  • gemini-3-pro-preview - Preview models
  • gemini-3-pro-high - High performance variant
Configuration:
Features:
  • Multi-account load balancing
  • Automatic token refresh
  • Virtual parent grouping for project-based accounts
  • Support for thinking models with budget configuration
File Format:

AI Studio (Gemini API Keys)

Authentication: API Key Configuration:
config.yaml
Features:
  • Direct API key access
  • Custom base URLs for relay services
  • Per-key proxy configuration
  • Model aliasing and exclusion

Vertex AI

Authentication: API Key (Vertex-compatible endpoints) Configuration:
config.yaml
Use Case: Third-party Vertex AI endpoints that use API keys instead of service accounts.

Claude Code

Authentication: OAuth 2.0 Models:
  • claude-sonnet-4 - Claude Sonnet 4
  • claude-opus-4-5-20251101 - Claude Opus 4.5
  • claude-3-5-sonnet-20241022 - Claude 3.5 Sonnet
  • claude-3-5-haiku-20241022 - Claude 3.5 Haiku
Configuration:
Features:
  • Multi-organization support
  • Custom TLS fingerprinting (bypasses Cloudflare)
  • Request cloaking for non-Claude-Code clients
  • Automatic session management
File Format:
Request Cloaking: Clause Code has detection mechanisms to identify non-official clients. CLI Proxy API supports request cloaking:
config.yaml
Cloaking features:
  • auto: Cloak only for non-Claude-Code clients
  • always: Always apply cloaking
  • never: Disable cloaking
  • strict-mode: Strip all user system messages
  • sensitive-words: Obfuscate specific words

Claude API (API Keys)

Authentication: API Key Configuration:
config.yaml
Use Case: Official Anthropic API keys or relay services.

OpenAI Codex

Authentication: OAuth 2.0 Models:
  • gpt-5-codex - GPT-5 for coding
  • gpt-5 - GPT-5 base model
  • o3-mini - O3 mini model
  • o1-preview - O1 preview model
Configuration:
Features:
  • JWT-based session tokens
  • Organization membership tracking
  • Refresh token rotation
  • Support for reasoning models
File Format:

Codex API (API Keys)

Authentication: API Key Configuration:
config.yaml
Use Case: OpenAI API keys or OpenAI-compatible relay services.

Qwen Code

Authentication: OAuth 2.0 Models:
  • qwen3-coder-plus - Qwen 3 Coder Plus
  • qwen3.5-plus - Qwen 3.5 Plus
  • qwen-max - Qwen Max model
Configuration:
Features:
  • Alibaba Cloud integration
  • Multi-account support
  • Cookie-based authentication
File Format:

iFlow (Z.ai GLM)

Authentication: OAuth 2.0 Models:
  • glm-4.7 - GLM 4.7
  • glm-5 - GLM 5 (Pro users)
  • tstars2.0 - TStar models
Configuration:
Sponsor: This project is sponsored by Z.ai’s GLM CODING PLAN starting at $10/month. Features:
  • GLM CODING PLAN integration
  • Multi-model support
  • Cookie-based session management
File Format:

Antigravity

Authentication: OAuth 2.0 (Google OAuth) Models:
  • gemini-3-pro-high - High performance model
  • gemini-3-pro-preview - Preview models
  • Other Gemini variants
Configuration:
Features:
  • Google’s code assistance platform
  • Project ID management
  • Onboarding flow for new users
  • Tier-based access
File Format:

Kimi

Authentication: OAuth 2.0 Models:
  • kimi-k2.5 - Kimi K2.5
  • kimi-k2 - Kimi K2
  • kimi-k2-thinking - Thinking variant
Configuration:
Features:
  • Moonshot AI integration
  • Cookie-based authentication
  • Multi-account support
File Format:

OpenAI Compatibility

Authentication: API Key Use Case: Any OpenAI-compatible endpoint (OpenRouter, local models, custom APIs) Configuration:
config.yaml
Model Pools: You can map multiple upstream models to the same alias for automatic failover:
Requests to best-model will round-robin across qwen3.5-plus, glm-5, and claude-3.5-sonnet. If one fails before producing output, the next model in the pool is tried.

Provider Comparison

Provider Selection

When a request specifies a model, CLI Proxy API:
  1. Resolves aliases - Converts client model names to upstream names
  2. Finds providers - Identifies which providers offer the model
  3. Filters credentials - Excludes disabled/cooldown/quota-exceeded credentials
  4. Applies routing - Uses round-robin or fill-first strategy
  5. Executes request - Sends to selected provider

Model Prefix Routing

Force a specific provider using prefixes:
See Routing for details.

Provider-Specific Features

Thinking Models

Providers that support thinking/reasoning:

Multimodal Input

Providers supporting image input:

WebSocket API

Some providers support WebSocket connections for lower latency:
config.yaml
Auth File
Connect via:

Adding Custom Providers

See the Custom Provider Example for implementing custom provider integrations using the SDK.

Next Steps

OAuth Setup

Authenticate with OAuth providers

API Keys

Configure API key providers

Routing

Learn about provider selection

Model Mappings

Configure model aliases and mappings