james-6-23/codex2api
Codex2API 是一个基于 Go + Gin + React/Vite 的 Codex 反向代理与管理后台项目 observed · 2026-08-28
Health v2 · maintenance only
77/100
- Activity 99
- Release rhythm 87
- Longevity 11
Flags: young no_license
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: 0
- age_days: 163
- days_rel: 7
- days_push: 7
- n_releases_24m: 128
Adoption not part of the score
1983 stars · 350 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
Codex2API is a self-hosted Go/Gin reverse proxy with an embedded React admin dashboard that turns a pool of Codex accounts into an OpenAI- and Anthropic-compatible API gateway. It exposes chat completions, responses, messages, images, and models endpoints while handling account scheduling, health scoring, dynamic concurrency, rate-limit recovery, and usage tracking.
Use cases
- expose an OpenAI-compatible API from a Codex account pool
- point Codex CLI or Claude Code at one self-hosted base URL
- rotate multiple Codex accounts with quota-aware load balancing
- add usage tracking and health monitoring to a Codex-to-API bridge
- self-host an Anthropic Messages-compatible gateway backed by Codex
- manage API keys, proxies, and prompt filtering from an admin console
- run a lightweight SQLite single-container gateway for Codex access
When to choose
- you have multiple Codex accounts and need one observable, schedulable OpenAI/Anthropic-compatible endpoint
- you want built-in account health tiers, cooldown recovery, round-robin or remaining-quota scheduling
- you need an embedded admin dashboard for accounts, keys, proxies, and usage analytics
- you want flexible deployment from a single SQLite container up to a PostgreSQL + Redis stack
When to avoid
- you need a thin, minimal proxy with no account-pool management or dashboard
- you require a permissively licensed dependency since the repository has no license
- you depend on officially supported OpenAI API access rather than unofficial Codex account forwarding
- you need actual model inference or fine-tuning, since this only forwards requests to Codex
Facets
service · maturity active
api-gateway proxy http-server auth rate-limiting monitoring self-hosted large-language-models artificial-intelligence apis developer-tools self-hosted backend go self-hosted cross-platform openai-compatible anthropic-compatible codex reverse-proxy account-pool llm-gateway admin-dashboard api-key-management token-refresh usage-tracking health-scoring gin react-dashboard sqlite postgresql redis docker linux web-server
2 sources
- readme: https://github.com/james-6-23/codex2api · fetched 2026-08-28 · 7185da98e1d6
- homepage: https://codex2api-latest-vu8j.onrender.com · fetched 2026-08-29 · c9aed7800a61
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| james-6-23/codex2api | main | 77 |
For agents
markdown · JSON · MCP: product_card(name="james-6-23/codex2api")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem