Users run the public Codex CLI locally.
Documentation and prospectus
How the CodexAPI.pro service works.
This document explains the system behind the customer dashboard: official OpenAI Codex CLI setup, wallet-backed API access, usage billing, Stripe top-ups, admin operations, and marketplace delivery.
Codex reaches a hosted Responses-compatible gateway.
Displayed 1M input/output token rate.
Projects resume through Codex's normal session state.
Overview
The service gives customers a practical way to use the official OpenAI Codex CLI with hosted account management. The CLI remains local. The hosted system supplies the provider endpoint, wallet credentials, usage tracking, top-up workflow, generated startup commands, and support tooling.
System components
Customer flow
- Create or receive a dashboard login.
- Open the dashboard and confirm wallet credit.
- Install the official Codex CLI with npm.
- Copy the generated Linux, Windows, or VS Code setup command.
- Run `codex --search` for a new project or `codex resume --last --search` for prior work.
- Return to the dashboard to inspect token usage and top up through Stripe.
Command model
Commands generated in the dashboard set `CODEXAPI_CODEX_API_KEY`, select `model_provider="codexapi"`, point Codex at `https://codexapi.pro/v1`, and use `wire_api="responses"`. When a buyer already has OpenAI Codex login state, the dashboard also provides isolated `CODEX_HOME` commands so this provider overrides the existing local profile for that run.
npm install -g @openai/codex@latest
CODEXAPI_CODEX_API_KEY="your_username" codex --search -m gpt-5.5
Wallet billing
Token usage is measured after completed Codex requests. The wallet displays the remaining dollar credit, daily usage, and transaction records. Stripe payments add credit to the existing token, so the customer does not need to reload Codex settings after a top-up.
G2G marketplace orders
Admins can create ready-to-deliver accounts for marketplace buyers. Delivery details include `Dashboard Login: https://codexapi.pro/dashboard.html`, dashboard username/password, API username/token, install commands, new-session commands, resume commands, and smoke tests. A single G2G order should use one wallet-linked token.
Admin operations
Admins manage users, pending signups, manual credit changes with notes, G2G order creation, token visibility, service provider selection, SMTP tests, API keys, and customer simulation. Provider changes apply to new requests and should not interrupt active work.
API routes
| Route | Purpose |
|---|---|
/v1/models | Model list for official Codex CLI. |
/v1/responses | Responses-compatible Codex execution and billing. |
/api/v1/cli/public-codex | Generated public Codex provider config. |
/api/v1/me | Dashboard account and wallet state. |
/api-docs | Verbose API reference. |
Support checklist
When a customer reports a problem, confirm their dashboard username, wallet balance, installed Codex version, operating system, exact command, current project directory, and whether they are starting fresh or resuming. Most failures come from missing environment variables, using the wrong Codex home, or copying only part of the generated command.