songquanpeng/one-api

LLM API 管理 & 分发系统,支持 OpenAI、Azure、Anthropic Claude、Google Gemini、DeepSeek、字节豆包、ChatGLM、文心一言、讯飞星火、通义千问、360 智脑、腾讯混元等主流模型,统一 API 适配,可用于 key 管理与二次分发。单可执行文件,提供...

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 16 minutes ago
Added to GitGenius on August 31st, 2026
Created on April 22nd, 2023
Open Issues & Pull Requests: 1,033 (+0)
GitHub issues: Enabled
Number of forks: 6,853
Total Stargazers: 36,769 (+0)
Total Subscribers: 188 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 35.3 hours
Mean response time: 23.9 days
90th percentile: 58.0 days
Tracked items: 477

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 38% of tracked open issues have had no activity in three months. Only 2% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 452
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 588 days
Stale 30+ days: 445
Stale 90+ days: 400

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (392)
  • enhancement (223)
  • waiting for pr (3)
  • priority (2)
  • question (2)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

One API is an LLM API management and redistribution system that unifies access to multiple large language model providers through a single standardized OpenAI-compatible API interface.

The tool solves the problem of managing credentials and routing requests across fragmented LLM providers. It accepts API keys from services including OpenAI, Azure, Anthropic Claude, Google Gemini, DeepSeek, and numerous others, then exposes them through a unified OpenAI API format. This allows applications built against the OpenAI standard to seamlessly switch between or load-balance across different model providers without code changes. The system handles key management, request routing, and credential isolation in a single deployment.

Teams should adopt this tool if they need to consolidate access to multiple LLM providers, manage API keys across different services, or offer their users flexibility in which models they consume. It suits organizations building LLM applications that want to avoid vendor lock-in, reduce operational overhead from managing separate integrations, or implement cost optimization through provider selection. The project positions itself as a ready-to-deploy alternative to building custom API gateway logic, offering a single executable binary or Docker image that requires minimal setup.

The project maintains active development with regular updates addressing new model providers and features. The codebase shows ongoing refinement of the core routing and adaptation logic. Documentation is comprehensive and available in multiple languages, reflecting attention to accessibility for different user communities. The tool receives consistent attention to operational concerns like deployment flexibility and configuration management.