Customer dashboard

Wallet credit for Codex CLI.

Create a CodexAPI.pro wallet account, then run the official OpenAI Codex CLI with the startup command generated below. New clients get $5 free credit, and signed-in clients can claim $10 once after sharing CodexAPI.pro.

Wallet balance $0.00 Top up wallet
Billing rate $5 / $30 per 1M input / output tokens
CLI username -
Account status Signed out

Client dashboard setup


Client dashboard

Start here

Install the official Codex CLI first.

Most clients trust the public OpenAI package, so start there. Install the official Codex CLI once, then use one of the generated CodexAPI.pro startup commands below to connect that trusted CLI to your wallet-backed API key.

Visible model for your next session GPT-5.5
npm install -g @openai/codex@latest
What this official install does

This installs the public OpenAI Codex CLI from npm. Run it once on the client computer after Node.js and npm are available. It does not spend CodexAPI.pro wallet credit by itself; it only installs the trusted CLI binary.

After install, copy the one-time setup-and-start command for your operating system. It saves the CodexAPI.pro API route and your wallet username into Codex's config file so future sessions can start with normal Codex commands.

Windows PowerShell setup

Install public OpenAI Codex CLI on Windows, then start CodexAPI.pro.

Follow the first setup box to install the official public Codex CLI, save CodexAPI.pro into the normal Windows Codex config, and start Codex automatically. After that, the normal codex and codex resume --search commands keep using your wallet-backed CodexAPI.pro route.

2

Open PowerShell as Administrator

Click Start, type PowerShell, right-click Windows PowerShell, then choose Run as administrator. Approve the Windows security prompt. This admin window is only needed for installing Node.js, npm, and Git.

3

Install required Windows dependencies

Copy and paste this whole block into the Administrator PowerShell window. It updates Winget sources, installs Node.js LTS, installs Git, and allows local user scripts to run. When it finishes, close PowerShell completely.

# Run PowerShell as Administrator for this dependency step.
winget source update
winget install --id OpenJS.NodeJS.LTS -e --accept-package-agreements --accept-source-agreements
winget install --id Git.Git -e --accept-package-agreements --accept-source-agreements
Set-ExecutionPolicy -Scope CurrentUser RemoteSigned -Force
# Close PowerShell, open a new PowerShell window, then run the verification step.
4

Reopen PowerShell and verify tools

Open a normal PowerShell window, not necessarily as Administrator. Run this check to confirm Windows can now see Node.js, npm, and Git. Each command should print a version number. If any command is not found, restart Windows and try this verification step again.

node --version
npm --version
git --version
5

Install the official public Codex CLI

Run this in the normal PowerShell window. This installs the official OpenAI Codex CLI from npm and then prints the installed Codex version. Installing Codex does not spend CodexAPI.pro wallet credit.

npm install -g @openai/codex@0.130.0
codex --version
6

Reference: what the one-time setup writes

The first box above writes CodexAPI.pro into the normal Codex config file so Windows can use plain Codex commands later. Keep this reference only if support asks you to inspect the generated config.

Configuration is generated in the first Windows setup box above.
8

Resume your latest CodexAPI.pro Codex session

Use this when you come back to continue previous work. It points Codex back to the same isolated CodexAPI.pro profile and asks Codex to resume the latest stored session history with search enabled.

Shown after signup or login
9

Run a quick smoke test

Run this short non-interactive test after setup. It confirms the official Codex CLI can reach CodexAPI.pro, your API key is accepted, and your wallet-backed provider config is working before you begin a real project.

Shown after signup or login

Linux Instructions

Linux Instructions

Use these commands for Linux or WSL. The first setup box writes CodexAPI.pro and your wallet username into Codex's normal config file, starts Codex automatically, and lets future sessions begin with plain Codex commands.

Official OpenAI Codex install command npm install -g @openai/codex@latest

Installs the official public OpenAI Codex CLI. This is the standard CLI package. After installing it, use the Public Codex startup command below so the official CLI talks to CodexAPI.pro with your wallet-backed API token.

Linux one-time setup command mirror Shown after signup or login

This mirrors the Linux setup-and-start command above for compatibility with older dashboard references. Use it once to save CodexAPI.pro into Codex's normal config.

Future Linux start commands Shown after signup or login

After setup, your wallet username and CodexAPI.pro route are saved. Start future sessions with codex or codex --search without redoing the setup block.

Public Codex smoke test command Shown after signup or login

Runs a small test request to confirm the CLI, CodexAPI.pro provider URL, API token, and wallet billing are all working. Use this before starting a large project or after moving the token to a new computer.

CodexAPI.pro-managed helper install npm install -g @embire2/codex@latest

This is optional and not the recommended first step. It installs the CodexAPI.pro helper CLI for clients who specifically want codexapi-codex convenience commands such as login, wallet status, project creation, and guided setup.

CodexAPI.pro-managed helper login codexapi-codex login

Starts the optional CodexAPI.pro helper login flow. Use it only if the client installed the helper package above. Official Codex users should use the startup commands instead.

CLI username Sign in to view

This is the dashboard and CodexAPI.pro-managed CLI username. Use it with the CodexAPI.pro login form or with codexapi-codex login.

CLI password Shown after signup or login

This password is shown after signup and after dashboard login so you can reconnect the CodexAPI.pro-managed CLI without creating a new API token.

Generated CLI passwords are shown immediately after signup and after dashboard login.

Future macOS start commands Shown after signup or login

After setup, open Terminal in any project folder and use codex or codex --search. The saved config supplies the CodexAPI.pro API route and your wallet username automatically.

Future macOS resume commands Shown after signup or login

Use these when you return to an existing local Codex project. Resume uses the local Codex history on that Mac and the saved CodexAPI.pro config.

macOS smoke test command Shown after signup or login

Runs a short non-interactive request to prove the saved config, API token, provider URL, and wallet billing path are working before a large coding session.

VS Code setup

Use the official Codex IDE extension with CodexAPI.pro.

Confirmed: this is possible because the official Codex IDE extension uses the Codex CLI and reads the shared Codex configuration file. CodexAPI.pro works by writing a CodexAPI.pro model provider into ~/.codex/config.toml and making your dashboard username available as the API token.

What works

VS Code can run Codex against CodexAPI.pro when the official Codex extension can see the shared Codex config, including the CodexAPI.pro provider URL and your wallet username.

What not to use

Do not use a generic OpenAI-compatible VS Code extension for this setup. Use the official Codex IDE extension so approvals, project context, edits, and terminal workflows match Codex behavior.

Model shown to clients

The dashboard displays GPT-5.5. The provider URL stays https://codexapi.pro/v1, and billing stays attached to this wallet.

1

Install VS Code and the official Codex extension

Install Visual Studio Code, open Extensions, search for the official OpenAI Codex extension, and install it. If it is already installed, update it first. Open the project folder in VS Code after the configuration steps below are complete.

2

macOS, Linux, or WSL: write the shared Codex config

Run this in a terminal before opening VS Code. It writes the CodexAPI.pro provider into the normal Codex config path, saves your wallet username in that provider config, and enables full-access Codex permissions for trusted project folders.

Shown after signup or login
3

Windows PowerShell: write the shared Codex config

Run this in PowerShell. It writes %USERPROFILE%\.codex\config.toml, saves your wallet username in the CodexAPI.pro provider config, and avoids any per-session environment-variable setup. Close all VS Code windows afterwards so the extension can reload the new config.

Shown after signup or login

Token usage and wallet spend

Tokens are charged after each completed prompt at $5 per million input tokens and $30 per million output tokens.

Completed Input Output Charged Balance after
Token usage appears here after dashboard data loads.

Top up after setup

Load more wallet credit when you are ready.

These options are intentionally placed after the startup instructions. Install and test Codex first, then choose a credit pack when the client is ready to run real prompts. Stripe credits the wallet after successful payment and keeps the existing Codex API token unchanged.

New accounts receive $5 free credit automatically. Stripe Checkout is secure and card details are saved at Stripe for future automatic top-ups.

Subscription

$199 Unlimited Credit

No hard credit limit. Usage is monitored under a fair-use policy and access only pauses if a rolling usage window is exceeded.

Automatic top-up

Make one wallet payment first so Stripe can attach a card to your account.