Skip to content
Codex Pooler

OpenAI-Compatible Codex Gateway

Codex Pooler can act as a narrow OpenAI-compatible Codex gateway for selected SDK clients. Clients call /v1 with a Pool API key, and Codex Pooler translates supported requests into Codex-compatible work before applying the same Pool routing, limits, account selection, and accounting path.

It does not provide full OpenAI API parity.

Supported Shape At A Glance

Section titled “Supported Shape At A Glance”
Client needUse this routeBoundary
List models visible to the PoolGET /v1/modelsOpenAI-shaped model list from Pool and catalog state
Send Responses workPOST /v1/responsesTranslated to Codex-compatible work and routed through Pool policy
Use chat-completions-style clientsPOST /v1/chat/completionsCoerced to Codex Responses work and normalized back to chat shape
Use narrow Responses websocket compatibilityGET /v1/responsesNot OpenAI Realtime SDK support
Read operator metadata/mcpSeparate endpoint with operator MCP tokens, not Pool API keys

Base URL

Section titled “Base URL”

Use https://codex-pooler.example.com/v1 for deployed examples, or http://localhost:4000/v1 for local setup. The credential is a Pool API key.

Base URL: https://codex-pooler.example.com/v1
Authorization: Bearer <pool-api-key>

Unsupported Boundaries

Section titled “Unsupported Boundaries”

Codex Pooler does not support /v1/realtime or OpenAI Realtime SDK websocket or session routes. GET /v1/responses is narrow Responses websocket compatibility only.

Unsupported /v1 routes may return deterministic OpenAI-shaped unsupported endpoint errors when explicitly routed. Examples include embeddings, batches, moderations, fine-tuning jobs, image variations, response retrieve, response cancel, response delete, and /v1/responses/compact.

Canonical Setup Pages

Section titled “Canonical Setup Pages”
Section titled “Related Discovery Pages”