One model setup for coding tools

Stable model names

Use stable aliases such as tekizai/frontier, tekizai/balanced, tekizai/agentic, and premium tekizai/fusion. Every tool can use these stable aliases across eligible vendor models.

Works with the Responses API

Hosted, local, and Tailnet setups support OpenAI-compatible chat completions and the Responses API, including Codex profiles with wire_api = "responses".

Automatic fallback

TEKIZ.AI tries your local, Tailnet, provider-key, and hosted routes in order. It keeps a response on one provider once streaming begins.

Choose a model that fits the request

TEKIZ.AI looks at the requested profile, tool use, context, provider health, and account limits before choosing a model.

Match the task

Tool calls, code/debug language, long context, vision hints, and requested profiles can push traffic toward models that fit the task.

Keep keys private

Provider keys and sign-in profiles stay on the router you control. A hosted TEKIZ.AI key gives access only to the models included in your account.

Deploy where agents run

Use https://api.tekiz.ai/v1 for hosted access, http://127.0.0.1:8790/v1 for local agents, or http://<tailnet-host>:8790/v1 for private Tailnet routing.

Codex profile

# ~/.codex/config.toml - add this provider once
[model_providers.tekizai]
name = "TEKIZ.AI"
base_url = "https://api.tekiz.ai/v1/"
env_key = "OPENAI_API_KEY"
wire_api = "responses"

# ~/.codex/tekizai-frontier.config.toml
model_provider = "tekizai"
model = "tekizai/frontier"

Plain codex keeps using ChatGPT. Select this provider explicitly with codex --profile tekizai-frontier.
Local and Tailnet Codex profiles use the same model profile with port 8790 on the router host.

Codex and code agents

Point Codex, OpenClaw, Cursor-style tools, and OpenAI SDK clients at one endpoint while preserving tool-call and Responses API compatibility.

Switch from another gateway

Move from https://gateway.example/api/v1 to https://api.tekiz.ai/v1, keep OpenAI-compatible clients, and route with tekizai/frontier or premium tekizai/fusion.

Keep provider access under your control

Use hosted account and API-key management where useful, while keeping production provider access on local servers, private Tailnet hosts, or your own cloud.

Check availability

You can check the public feature status at https://api.tekiz.ai/features/agent-native. Public hosted model traffic is enabled only when the edge reports verified capacity.

Choose a setup

Start with the local-first quickstart, compare positioning on TEKIZ.AI model gateway, or estimate workflow fit with the model routing calculator.