Model routing for coding agents

Connect your coding tools to the models you choose.

Set up Codex, Cursor, Aider, Continue, Claude Code, OpenHands, and OpenClaw with TEKIZ.AI. Start with models available to your hosted account, or run the router yourself to use provider accounts and local models you control.

Create API key Read the API quickstart Codex setup Browse integrations

One place to manage model routes

Codex, Cursor, Aider, Continue, Claude Code, OpenHands, OpenClaw, and SDK clients can use stable profiles such as tekizai/frontier. Hosted access uses models available to your account. A router you run uses the providers you configure.

When a coding model reaches a limit

Hosted requests can retry on another eligible TEKIZ.AI route. A router you run can try another authorized provider or local model after a retryable failure. Your tool keeps its configured address for that setup.

Choose hosted or local routing

Use https://api.tekiz.ai/v1 with a generated sk_tekiz_* key for hosted models. Run the router beside Ollama or on a private Tailnet host for your own provider access.

Configure Codex for the hosted API

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

A hosted key reaches models available to your TEKIZ.AI account. Configure authorized provider keys, supported sign-in profiles, or local models on a router you run. Those providers bill you separately.

See which route handled the request

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

Keep your model choices in one place

A provider key can reach its limit, and some models cannot handle files. Check which routes are available in your chosen setup. TEKIZ.AI can retry a new request when another eligible route is available.

Next steps

Create an API key, configure Codex, set up your own router, browse integrations, or estimate routing fit.