Skip to main content

CloudService for Codex

Connect Codex CLI to a CloudService OpenAI-compatible route.

Use Codex with an OpenAI-capable CloudService key and the base URL that matches its billing mode. The CloudService CLI can configure and verify the connection, or you can follow the manual Codex guide.

Recommended key
OpenAI token key
Alternative
API-credit key
Protocol
OpenAI-compatible
Verification
cloudservice doctor

Two billing modes, one Codex workflow.

OpenAI token key
Use this when you want a fixed prepaid token allowance for supported OpenAI-family models. The Codex base URL is the token-budget OpenAI-compatible route.
API-credit key
Use this when you want a published-price USD credit balance that can also cover supported Claude-compatible routes. Codex uses the API-credit OpenAI-compatible route.
Automatic or manual
The CloudService installer detects Codex configuration and writes the matching provider settings after authentication. The manual guide shows the same settings when you prefer to review each field.

Codex base URLs.

Both routes are OpenAI-compatible. Choose exactly one based on the key you purchased.

OpenAI token key

https://api.cloudservice.services/token/v1

Recommended for a prepaid OpenAI token allowance.

API-credit key

https://api.cloudservice.services/v1

For a prepaid USD credit balance.

Set up Codex without guessing.

  1. Install CloudService

    Install the published CloudService CLI, sign in with the API key you intend to use, and let it detect Codex.

  2. Apply the Codex configuration

    Select Codex in the setup flow. The installer chooses /v1 or /token/v1 from the authenticated key type.

  3. Verify before a long task

    Run cloudservice doctor and cloudservice models. Use a model ID returned to that same key.

  4. Keep the error context

    If a request fails, save the status code, request ID, selected model ID, and Codex version for support.

What this page does and does not promise.

  • Codex support means CloudService exposes an OpenAI-compatible route and documented configuration for Codex.
  • The model picker must use an ID returned by your authenticated CloudService catalog.
  • A displayed model name and its copyable API ID are separate; use the API ID in configuration.
  • Availability and optional capabilities can change with the active model route, so verify before a large run.

Configure Codex from the key, not from memory.

Start with guided setup for automatic route selection, then verify the authenticated model list before sending a full coding task.

Open guided setup