Step 1 / API key

Connect Codex to TEKIZ.AI.

Create an API key in about 60 seconds. No credit card required.

Already have an account? Recover API key.

Step 2

Add the provider and opt-in profile.

Replace the placeholder with the sk_tekiz_* key from your account. Copy the setup below into a terminal. It adds the provider only when missing, then creates the matching profile files; TEKIZ.AI is selected only when you run the matching --profile command.

Keep your normal ~/.codex/config.toml on the built-in OpenAI provider. Do not set a root model_provider or oss_provider to TEKIZ.AI. Running codex stays on ChatGPT Codex; only codex --profile tekizai uses TEKIZ.AI.

Hosted Codex
mkdir -p ~/.codex
if ! grep -Fqx '[model_providers.tekizai]' ~/.codex/config.toml 2>/dev/null; then
cat >> ~/.codex/config.toml <<'TOML'
[model_providers.tekizai]
name = "TEKIZ.AI Hosted"
base_url = "https://api.tekiz.ai/v1/"
env_key = "TEKIZAI_API_KEY"
wire_api = "responses"
TOML
fi

cat > ~/.codex/tekizai.config.toml <<'TOML'
model_provider = "tekizai"
model = "tekizai/auto"
TOML

cat > ~/.codex/tekizai-frontier.config.toml <<'TOML'
model_provider = "tekizai"
model = "tekizai/frontier"
TOML

export TEKIZAI_API_KEY=sk_tekiz_your_key_here
codex --profile tekizai

Step 3

Verify before starting Codex.

A successful model-list response confirms that the endpoint and key are valid.

Hosted model list
curl https://api.tekiz.ai/v1/models \
  -H "Authorization: Bearer $TEKIZAI_API_KEY"

codex --profile tekizai

Optional / Fusion

Use parallel review when the work separates cleanly.

Fusion assigns independent numbered tasks to smaller workers, then returns one reviewed answer. Use it for planning, investigation, review, or a final written synthesis.

Keep tekizai/frontier for Codex turns that need to run tools or edit files. Fusion deliberately keeps client tools out of parallel worker calls.

Codex Fusion profile
# Run the Hosted Codex setup first, then paste this.
mkdir -p ~/.codex
cat > ~/.codex/tekizai-fusion.config.toml <<'TOML'
model_provider = "tekizai"
model = "tekizai/fusion"
TOML

codex --profile tekizai-fusion
Use a local or Tailnet TEKIZ.AI instead

Local profile

Connect through port 8790.

Local Codex
mkdir -p ~/.codex
if ! grep -Fqx '[model_providers.tekizai-local]' ~/.codex/config.toml 2>/dev/null; then
cat >> ~/.codex/config.toml <<'TOML'
[model_providers.tekizai-local]
name = "TEKIZ.AI Local"
base_url = "http://127.0.0.1:8790/v1/"
env_key = "TEKIZAI_API_KEY"
wire_api = "responses"
TOML
fi

cat > ~/.codex/tekizai-local-frontier.config.toml <<'TOML'
model_provider = "tekizai-local"
model = "tekizai/frontier"
TOML

export TEKIZAI_API_KEY=local
codex --profile tekizai-local-frontier

Tailnet profile

Connect to a private host.

Tailnet Codex
mkdir -p ~/.codex
if ! grep -Fqx '[model_providers.tekizai-tailnet]' ~/.codex/config.toml 2>/dev/null; then
cat >> ~/.codex/config.toml <<'TOML'
[model_providers.tekizai-tailnet]
name = "TEKIZ.AI Tailnet"
base_url = "http://<tailnet-host>:8790/v1/"
env_key = "TEKIZAI_API_KEY"
wire_api = "responses"
TOML
fi

cat > ~/.codex/tekizai-tailnet-frontier.config.toml <<'TOML'
model_provider = "tekizai-tailnet"
model = "tekizai/frontier"
TOML

export TEKIZAI_API_KEY=local
codex --profile tekizai-tailnet-frontier
Status Likely cause Next action
401 The Codex environment variable is missing, revoked, or not the key expected by the selected provider. Check env_key, regenerate a hosted sk_tekiz_* key, or set the local router token.
402 The hosted account plan, quota, or billing state blocks model traffic. Finish checkout, choose a plan, or review usage on the account page.
429 The account or router is rate limited. Reduce Codex concurrency, retry later, or upgrade the hosted plan limit.
503 No authorized healthy backend route is currently available. Check public status, local provider credentials, router health, and fallback policy.

For response headers, safe curl probes, and no-secret support context, use the hosted API troubleshooting page.

Support boundary

Keep prompts and secrets out of support requests.

Do not paste prompts, provider credentials, OAuth tokens, generated API keys, private keys, session cookies, raw provider responses, or customer data into public support channels. Safe troubleshooting context is limited to account email, plan, timestamp, request id, HTTP status, safe error class, and non-secret key prefix.