Use APINebula in Codex
Generate a Codex config from the Responses-compatible endpoint in APINebula's docs. The API key in the config is a placeholder; replace it with a key you create at APINebula.
Endpoints
- Pay as you go
https://apinebula.ai/v1The token must be in the CODEX group.Docs · verified 2026-11-09
Generate the config
Save to ~/.codex/config.toml; merge it in if the file already exists
model = "gpt-6-astra"
model_provider = "apinebula"
[model_providers.apinebula]
name = "APINebula"
base_url = "https://apinebula.ai/v1"
env_key = "APINEBULA_API_KEY"
wire_api = "responses"
Models and prices
$ per 1M tokens. Each model uses the provider's cheapest group; the ratio uses the output price
How to check it works
Restart Codex and send a message. If it replies and the request shows up in APINebula's console, it is using this endpoint.
FAQ
Why is the key in an environment variable?
config.toml only holds the variable's name, so the key never goes into the config file and does not leak when you share or sync it. To keep it, add the export line to ~/.zshrc or ~/.bashrc.
How do I switch back to OpenAI?
Remove the model_provider line from config.toml, then restart Codex.
Does my key pass through this site?
No. The page only generates config text and never asks for your key; the key only goes into the terminal or environment variables on your own machine.