TEKIZ.AI cloud
Use https://api.tekiz.ai/v1 with an active
sk_tekiz_* key for usage limits, request history,
automatic backup, and access from anywhere.
Local router
Use http://127.0.0.1:8790/v1 for local agents, Docker
Desktop, Umbrel, or developer machines where provider credentials
and subscriptions stay on your machine.
Private network
Use http://<tailnet-host>:8790/v1 for private
access across your TEKIZ.AI computers without exposing them to
the public internet.
Copy a configuration file
Keep your default Codex setup unchanged and opt into TEKIZ.AI with
a named profile. The guide writes the provider to
~/.codex/config.toml and the profile to
~/.codex/tekizai.config.toml.
Use your harness’s native file
Aider uses ~/.aider.conf.yml; Continue uses
~/.continue/config.yaml; and OpenClaw uses
~/.openclaw/openclaw.json. Each guide includes a
copy button and a key placeholder. Never paste a real key into a
repository file.
When there is no config file
Cursor uses its Settings interface, while Claude Code can use shell environment variables. We do not invent unsupported files: use the exact setup screens and commands in their guides.
Choose the client you already use
Every setup uses the same model profiles. Connect only providers you are allowed to use, and keep credentials out of support messages.
OpenAI SDKs, LangChain, LiteLLM, and custom clients
Set
OPENAI_BASE_URL=https://api.tekiz.ai/v1 or
local port 8790, then call
tekizai/frontier through chat completions or
Responses API-compatible routes.
Codex CLI and OpenClaw Codex profiles
Use wire_api = "responses",
model = "tekizai/frontier", and the hosted,
local, or Tailnet base URL where you run TEKIZ.AI.
Cursor, Aider, Continue, Claude Code, and OpenHands
Point OpenAI-compatible settings at TEKIZ.AI. TEKIZ.AI then chooses an available model from the services you connected.
Ollama, Ollama Cloud, NVIDIA NIM, and BYOK endpoints
Run TEKIZ.AI beside Ollama or another model service. It finds available models where supported, while your tools connect only to TEKIZ.AI.
DeepSeek V4 for Codex and OpenAI-compatible clients
Keep one or more DeepSeek API keys on the router host, isolate failures per credential, and use V4 Flash directly or through a route profile. Open the DeepSeek guide.
Claude-style client adapters
Use Anthropic-compatible client routes where your harness expects them. Provider credentials stay private on your router.
OpenClaw, Hermes, and Pi agents
Start with tekizai/auto, then select
tekizai/frontier or tekizai/fusion
when your authenticated model list shows capacity.
Connect your models and subscriptions
Bring your own key (BYOK) by saving a provider API key on your TEKIZ.AI Router computer. Bring your own subscription (BYOS) by connecting a provider-supported subscription or sign-in. Local Ollama usually needs no key.
You can add more than one key for the same provider. If one fails, TEKIZ.AI pauses only that key and tries the others. Subscription sign-ins work only through integrations approved by that provider.
Do not paste prompts or secrets
When asking for help, share your account email, plan, time of the problem, HTTP status, request ID, error type, and only the first few characters of a key. Never send prompts, API keys, passwords, cookies, model responses, or customer data.