Keep provider keys on your router

Save provider keys, supported sign-in profiles, and private gateway credentials on the router host you control. A generated TEKIZ.AI key is for the hosted API and its account limits and reports.

Choose a backup route

TEKIZ.AI considers availability, speed, model support, and your preferred order. If you configure another eligible model, the router can try it when a provider is down or rate-limited.

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.

Test a configured local router

After you receive and configure the router installation, start it in one terminal. Leave it running and check the available models from a second terminal.

python3 router.py --port 8790

export OPENAI_BASE_URL=http://localhost:8790/v1
export OPENAI_API_KEY=local-router

curl "$OPENAI_BASE_URL/models" \
  -H "Authorization: Bearer $OPENAI_API_KEY"

Add the hosted service when you need it

The local router runs on your infrastructure. The hosted service adds account keys, usage limits, reports, health checks, and a public API endpoint. Check your plan and live capacity for included hosted models. Your own provider accounts and local models remain on the router you run.

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 API when tools need an internet-accessible endpoint. Keep private routers and provider credentials on machines you control.

Next steps

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