One setup for every tool

Codex, Cursor, Aider, Continue, Claude Code, OpenHands, OpenClaw, and SDK clients can use stable profiles such as tekizai/frontier while TEKIZ.AI chooses among your connected providers.

Keep working when an account is busy

When a model, provider, API key, or subscription path rate-limits, TEKIZ.AI can fail over to another authorized route. Each coding tool keeps one gateway configuration.

Local plus hosted

Keep local Ollama and Tailnet routes available as backups, then use hosted sk_tekiz_* keys for usage limits, reports, and public access.

Set up coding agent setup

export OPENAI_BASE_URL=https://api.tekiz.ai/v1
export OPENAI_API_KEY=sk_tekiz_your_generated_key

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"
base_url = "https://api.tekiz.ai/v1/"
env_key = "OPENAI_API_KEY"
wire_api = "responses"
TOML
fi

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

# Plain codex keeps using ChatGPT. TEKIZ.AI is explicit.
codex --profile tekizai

Send files to services that accept them

Image, audio, video, and document inputs route only to capable models, so coding agents do not accidentally send multimodal tasks to text-only routes.

Use accounts you are allowed to use

Bring authorized provider keys, OAuth profiles, Dario paths, or local models. TEKIZ.AI public plans do not grant unauthorized provider access.

See which route handled the request

Hosted routing records the selected route and basic request details without exposing provider secrets.

Stop maintaining a different setup for every tool

One provider key can hit a limit, one tool may lack a local backup, and file support varies by model. TEKIZ.AI handles those choices once and gives every coding tool the same address.

Next steps

Create an API key, configure Codex, browse integrations, or estimate routing fit.