Configure Codex CLI for GetAPI.ONE

Scope and prerequisites

This guide covers the terminal Codex CLI. It does not establish compatibility for every desktop client, IDE extension, model, or Codex feature.

• A GetAPI.ONE account with usable balance or an applicable package.
• A named, scoped GetAPI.ONE key stored privately.
• A model selected from the current catalog that explicitly lists the Responses endpoint.
• Permission to install Codex CLI and edit your user-level Codex configuration.

• Create a scoped key
• Check endpoint-compatible models

1. Install and identify Codex CLI

Use the current official Codex CLI page for the installer matching your operating system. The official macOS/Linux standalone installer reviewed on 2026-09-07 uses the command below. Windows users should follow the Windows tab on the official page rather than run a Unix shell command blindly.

curl -fsSL https://chatgpt.com/codex/install.sh | sh

codex --version

2. Load the key into the terminal

Set the key for the current shell before starting Codex. These examples deliberately contain a placeholder.

export GETAPI_ONE_API_KEY="replace-with-your-private-key"

$env:GETAPI_ONE_API_KEY = "replace-with-your-private-key"

3. Configure the ONE provider

Open the user-level Codex config.toml (normally under your .codex directory) and add the provider below. Replace YOUR_RESPONSES_MODEL with a current GetAPI.ONE catalog model that explicitly declares the Responses endpoint.

model_provider = "getapi_one"
model = "YOUR_RESPONSES_MODEL"

[model_providers.getapi_one]
name = "GetAPI One"
base_url = "https://www.getapi.one/v1"
env_key = "GETAPI_ONE_API_KEY"
wire_api = "responses"

4. Run and verify

1. Open a new terminal if you made the environment variable persistent; otherwise keep the current terminal where the variable is set.
2. Open a project directory and run codex. Confirm the displayed provider/model corresponds to the configuration you intended.
3. Send one minimal prompt only when you accept that it may be billed.
4. A successful check requires a valid CLI response and a corresponding GetAPI.ONE console request/usage record. No model call was made while producing this guide.

Troubleshoot in order

• Full troubleshooting guide
• Prepare a safe support report