Setup paths

Tekiz Integrations

Use one Tekiz endpoint from hosted clients, local tools, Tailnet agents, and BYOK-compatible provider stacks. Start with generated sk_sage_* hosted keys for https://api.tekiz.ai/v1, or run the router on local port 8790 when provider credentials should stay on your own host.

Create hosted API key Read quickstart Configure Codex Agent-native routing

Create an account now. Connect an authorized provider or add billing when you are ready to route.

Hosted API

Use https://api.tekiz.ai/v1 with an active generated sk_sage_* key for account-managed quotas, usage analytics, fallback routing, and public edge reliability.

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 under local custody.

Tailnet router

Use http://<tailnet-host>:8790/v1 for private fleet routing across healthy Tekiz installations before placing a public edge in front.

Choose the client you already use

These setup paths share the same model profiles, provider authorization boundary, and no-secret support posture.

OpenAI-compatible

OpenAI SDKs, LangChain, LiteLLM, and custom clients

Set OPENAI_BASE_URL=https://api.tekiz.ai/v1 or local port 8790, then call sage-router/frontier through chat completions or Responses API-compatible routes.

Codex

Codex CLI and OpenClaw Codex profiles

Use wire_api = "responses", model = "sage-router/frontier", and the hosted, local, or Tailnet base URL that matches your custody model.

Code agents

Cursor, Aider, Continue, Claude Code, and OpenHands

Point OpenAI-compatible settings at Tekiz first, then let route profiles and health-aware fallback pick the best authorized backend.

Local models

Ollama, Ollama Cloud, NVIDIA NIM, and BYOK endpoints

Run Tekiz beside the provider runtime, discover available models where supported, and expose only the routing endpoint to agents.

DeepSeek BYOK

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.

Anthropic-compatible

Claude-style client adapters

Use Anthropic-compatible client routes where your harness expects them, while keeping provider credentials customer-authorized and private.

OpenClaw

OpenClaw, Hermes, and Pi agents

Use route profiles such as sage-router/frontier, sage-router/balanced, and sage-router/agentic instead of hard-coding one vendor model.

Bring the access you are authorized to use

BYOK uses provider API keys or workload credentials on your router host. BYOS uses a provider-supported subscription credential or OAuth profile. Local Ollama needs no credential unless its operator requires one.

All configured providers can use isolated credential pools. A failed key cools that credential, not every account for the provider. Consumer login sessions are supported only when the provider exposes an authorized integration path.

Provider credential matrix DeepSeek BYOK setup Ollama and Ollama Cloud NVIDIA NIM BYOK

Do not paste prompts or secrets

Support and setup reviews should use account email, plan, timestamp, HTTP status, request id, safe error class, and non-secret key prefix only. Do not paste prompts, workflow text, provider credentials, OAuth tokens, generated API keys, private keys, session cookies, raw provider responses, or customer data.