Agent-native routing

Agent-native model routing

Give Codex-style and OpenAI-compatible agents one endpoint that can choose frontier routes, use Fusion when capacity is live, respect tool-use needs, fail over across healthy authorized providers, and keep provider credential custody local or under your own control.

Run Tekiz View dashboard demo Join hosted beta Configure Codex

Use GitHub or email. Your key is shown once.

Profiles agents can name

Use stable aliases such as sage-router/frontier, sage-router/balanced, sage-router/agentic, and premium sage-router/fusion instead of hard-coding one vendor model into every harness.

Responses API ready

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

Health-aware fallback

Each request can build an ordered fallback chain from authorized local, Tailnet, BYOK, and hosted routes without switching providers mid-stream.

Built for agent harnesses, not just chat demos

Tekiz looks at tool schemas, requested model profiles, prompt shape, provider health, quotas, and deployment context before choosing a route.

1

Route by intent

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

2

Keep custody clear

By default, provider keys and OAuth profiles stay with the customer-controlled router. Hosted keys authorize Tekiz account access; they do not imply pooled provider resale.

3

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 and code agents

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

Gateway migration

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

Local-first operations

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

Public metadata

Agents and operators can inspect public feature metadata at https://api.tekiz.ai/features/agent-native. Public hosted model traffic is enabled only when the edge reports verified capacity.