Discover and explore top open-source AI tools and projects—updated daily.
CaddyGlowUnified local API access for multiple AI providers
Top 98.1% on SourcePulse
<2-3 sentences summarising what the project addresses and solves, the target audience, and the benefit.> CCProxy API addresses the complexity of integrating with multiple AI providers like Anthropic Claude, OpenAI Codex, and GitHub Copilot. It offers a local, plugin-based reverse proxy that unifies access through a single, consistent API, enabling users to leverage existing subscriptions without managing individual API keys or billing. This simplifies development and allows for seamless switching between models and providers.
How It Works
<2-4 sentences on core approach / design (key algorithms, models, data flow, or architectural choices) and why this approach is advantageous or novel.> The core of CCProxy API is a plugin-based reverse proxy architecture. It supports providers like Anthropic Claude (API/SDK), OpenAI Codex, and GitHub Copilot, exposing a unified interface that mimics OpenAI Chat Completions and Anthropic Messages. A key design choice is the shared model-mapping layer, allowing clients to use the same model identifiers across different backends without code modification. Authentication can leverage existing provider credential files or utilize CLI-driven OAuth flows, with secrets automatically picked up by the proxy.
Quick Start & Requirements
uvx --with "ccproxy-api[all]" ccproxy serve --port 8000pipx install "ccproxy-api[all]" followed by ccproxy serve.docs/index.mddocs/getting-started/quickstart.mddocs/getting-started/configuration.mddocs/examples.mdHighlighted Details
access_log), analytics (analytics with DuckDB), request tracing (request_tracer), metrics (metrics with Prometheus compatibility), and more, allowing customization of instrumentation and storage.Maintenance & Community
The provided README does not contain specific details regarding maintainers, community channels (e.g., Discord, Slack), sponsorships, or a public roadmap.
Licensing & Compatibility
The project's license is indicated as "See LICENSE" within the repository. Specific details regarding the license type, commercial use permissions, or compatibility with closed-source projects are not elaborated upon in the README.
Limitations & Caveats
The README does not explicitly list any limitations, alpha status, or known bugs. The mention of "Migration (0.2)" suggests that version updates may involve breaking changes, requiring attention during upgrades.
1 month ago
Inactive