ccflare

ccflare 🛡️

A multi-provider native proxy for Anthropic and OpenAI.

ccflare routes each provider by URL prefix, load-balances across multiple accounts, and keeps full request history, rate-limit state, and usage analytics without translating provider payloads.

Why ccflare?

- Native passthrough — Anthropic stays Anthropic, OpenAI stays OpenAI
- Multi-provider routing — route by /v1/{provider}/*
- Compatibility routes — route by /v1/ccflare/* with family-prefixed models
- Account failover — retry another account when one provider account is rate limited
- Built-in observability — dashboard, request history, analytics, logs, and health endpoints
- Flexible auth — API key and OAuth account support

Quick start

Verify the server is up:

How routing works

ccflare proxies requests by provider prefix:

- http://localhost:8080/v1/anthropic/*
- http://localhost:8080/v1/openai/*
- http://localhost:8080/v1/ccflare/*

Examples:

- /v1/anthropic/v1/messages → https://api.anthropic.com/v1/messages
- /v1/openai/chat/completions → https://api.openai.com/v1/chat/completions
- /v1/openai/responses → https://api.openai.com/v1/responses

The /v1/{provider} prefix is stripped exactly once before forwarding upstream.

Compatibility routes keep the client-facing schema but select a provider family from
the model prefix:

- openai/ → prefers codex, then openai
- anthropic/ → prefers claude-code, then anthropic

Examples:

- /v1/ccflare/openai/chat/completions with "model":"openai/gpt-5.4"
- /v1/ccflare/openai/responses with "model":"anthropic/claude-sonnet-4"
- /v1/ccflare/anthropic/messages with "model":"openai/gpt-4o-mini"

Account setup

API key accounts

Add accounts through the management API:

OAuth accounts

Use the CLI/TUI for interactive OAuth setup:

The management API also…