Your keys stay with you

Provider API keys, OAuth profiles, local models, and private gateway credentials can stay on the router host. Hosted generated keys authorize TEKIZ.AI account access, quotas, and analytics.

Automatic backup routes

TEKIZ.AI considers availability, speed, model support, and your preferred order. If a provider is down or rate-limited, your apps can continue through another route.

Ollama and Tailnet

Use local Ollama and Ollama Cloud through your local runtime, then expose the router to trusted agents on port 8790 locally or across a private Tailnet.

30-second local start

python3 router.py --port 8790
export OPENAI_BASE_URL=http://localhost:8790/v1
export OPENAI_API_KEY=local-router

curl "$OPENAI_BASE_URL/chat/completions" \
  -H "Authorization: Bearer $OPENAI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "tekizai/frontier",
    "messages": [{"role": "user", "content": "Route this well"}]
  }'

Add the hosted service when you need it

The local router can stay useful by itself, but hosted TEKIZ.AI can add account keys, usage limits, reports, health checks, and a public endpoint. Hosted plans provide TEKIZ.AI service; model access is listed separately and you can always bring your own.

Multiple API keys

Configure multiple keys for the same provider, balance load, and fail over when a key hits 429 or another retryable provider error.

Send files to services that accept them

Image, audio, video, and document signals are routed to capable models with matching input support. TEKIZ.AI remembers confirmed model capabilities for later requests.

A public address when you need one

Use the hosted public edge when you need stable external access, while keeping private routers and provider credentials on trusted machines.

Next steps

Read the hosted/local quickstart, read the local-first routing guide, browse route families, or compare hosted plans.