Codex setup

Use a compatible API in Codex-style developer tools

Point a client that supports a custom OpenAI-compatible endpoint at router.cheap, then validate the model, responses format, streaming, and tool permissions used by your version.

Start with router.cheap Read the API docs

Core settings

Base URL: https://router.cheap/v1.
Authentication: a router.cheap API key stored outside source code.
Model: an identifier currently returned by /v1/models.
Timeout and retry policy: explicit values appropriate for coding tasks and CI.

Test before automation

Start with read-only or sandboxed tasks. Check diff quality, tool-call behavior, token usage, and failure recovery before allowing writes, shell commands, or unattended CI actions.

Frequently asked questions

Is Codex the same as the OpenAI API?

Codex-style clients and the OpenAI API are related but client capabilities differ. Follow the client version's endpoint and responses requirements.

Can I use the chat completions endpoint?

Use the endpoint supported by your client. router.cheap documents both compatible request families where enabled; verify the current model catalog.

How should CI keys be handled?

Use a dedicated least-privilege key in the CI secret store, never in repository files or logs.