Codex Pooler Vs Direct Credentials
Codex Pooler changes the client credential model. Instead of putting account-specific material in each client, operators connect upstream Codex accounts to Pools and give clients stable Pool API keys. Codex Pooler then routes supported work to eligible upstream accounts.
Comparison
Section titled “Comparison”| Question | Direct account credentials | Codex Pooler |
|---|---|---|
| What does the client hold? | Account-specific credential material or client-specific account setup | A Pool API key that represents a Pool |
| How do capacity changes work? | Each client may need reconfiguration | Operators adjust Pool assignments, upstream lifecycle, and routing policy centrally |
| How is an account selected? | Selection is usually fixed by client setup | Eligibility checks and Pool strategy choose from assigned upstream accounts |
| How are requests investigated? | Evidence may be spread across clients and local logs | Admin UI and MCP expose sanitized metadata for visible Pools |
| What stays out of logs? | Depends on each client and process | Docs describe metadata-only request, routing, audit, and MCP evidence |
When Codex Pooler Fits
Section titled “When Codex Pooler Fits”Codex Pooler fits teams that already operate trusted Codex accounts and want centralized Pool policy, stable client credentials, shared capacity, account readiness checks, continuity-aware routing, and metadata-only request evidence.
It is not a way to bypass account terms or limits. Operate only accounts you are allowed to use, and give Pool API keys only to trusted clients.
Credential Boundaries
Section titled “Credential Boundaries”Use Pool API keys for /backend-api and /v1 runtime requests. Use operator-owned MCP tokens for /mcp. Do not reuse Pool API keys for MCP, and do not use MCP tokens for runtime work.
Raw Pool API keys and raw MCP tokens are one-time secrets in the product surfaces. Public docs should use placeholders such as <pool-api-key> and <operator-mcp-token>.
Canonical Docs
Section titled “Canonical Docs”- Codex Pooler overview covers the product scope and FAQ
- Pools explains the Pool boundary and routing settings
- Upstreams explains account lifecycle and readiness
- Routing Strategies explains eligibility, continuity, quota evidence, and fallback