Gateway migration

Move OpenAI-compatible clients to Tekiz.

Switch the base URL, use a generated sk_sage_* key, and start with sage-router/auto. Check your authenticated model list before selecting Frontier or Fusion.

Create hosted API key Quickstart API reference Compare gateways Check status

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

Hosted Tekiz routes only authorized provider access, local models, customer subscriptions, API keys, cloud accounts, or endpoints. It does not grant unauthorized provider access, pool personal accounts, or bypass provider terms.

Existing gateway setupTekiz hosted setupMigration note
OPENAI_BASE_URL=https://gateway.example/api/v1 OPENAI_BASE_URL=https://api.tekiz.ai/v1 Most OpenAI-compatible SDKs only need the base URL changed.
LEGACY_GATEWAY_API_KEY or a Bearer key OPENAI_API_KEY=sk_sage_your_key_here Generate the Tekiz key on the hosted account page. Raw keys are shown once.
Provider-prefixed model IDs from the hosted catalog Start with sage-router/auto; select Frontier or Fusion only when your authenticated model list shows capacity. Provider-specific routes remain available only when your Tekiz profile has authorized provider access configured. Fusion plans bounded work, runs eligible independent tasks in parallel, then verifies one final response.
Gateway /models Public https://api.tekiz.ai/model-catalog and authenticated GET /v1/models Discovery metadata is public; live model APIs still require an active generated key.

Before

Typical gateway environment.

export OPENAI_BASE_URL=https://gateway.example/api/v1
export OPENAI_API_KEY=$LEGACY_GATEWAY_API_KEY

After

Hosted Tekiz environment.

export OPENAI_BASE_URL=https://api.tekiz.ai/v1
export OPENAI_API_KEY=sk_sage_your_key_here
export OPENAI_MODEL=sage-router/auto

First request

Verify routing before moving production traffic.

Use a small chat completion first, then move agents and job queues after the generated key, plan state, quota, and backend health are confirmed.

curl https://api.tekiz.ai/v1/chat/completions \
  -H "Authorization: Bearer $OPENAI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "sage-router/auto",
    "messages": [
      {"role": "user", "content": "Reply with one migration check."}
    ]
  }'
OpenAI SDK

JavaScript

import OpenAI from "openai";

const client = new OpenAI({
  apiKey: process.env.OPENAI_API_KEY,
  baseURL: "https://api.tekiz.ai/v1",
});

await client.chat.completions.create({
  model: "sage-router/auto",
  messages: [{ role: "user", content: "Route this request." }],
});
Routes

Profile migration

  • Use sage-router/auto for the first hosted request, then consult authenticated /v1/models for available profiles.
  • Use sage-router/frontier or sage-router/fusion only when the authenticated model list shows capacity. On Pro/Max, Fusion derives explicit bounded work locally, runs eligible workers in parallel, and returns a verified final response. The dedicated Fusion page lives at /fusion.
  • Existing Fusion tool calls can keep {"type":"sage-router:fusion"}; Tekiz handles that server tool before downstream provider routing and applies the same Fusion plan gate.
  • Use sage-router/local when the router has local Ollama routes available.
  • Use model catalog discovery before mapping provider-specific IDs.
Safety

Provider boundary

Tekiz does not grant unauthorized provider access. Managed provider access is private beta only and requires provider authorization, margin policy, quotas, durable operator audit events, abuse controls, and acceptable-use enforcement before activation.

StatusLikely migration causeNext action
401Missing, inactive, malformed, or revoked generated key.Generate or rotate an sk_sage_* key on the account page.
402Checkout, subscription, plan, or monthly quota blocks model traffic.Finish checkout or choose an active hosted plan.
429Request-per-minute limit or burst control triggered.Back off, reduce concurrency, or move to a higher plan.
503No healthy authorized backend route is available.Check public status, Tailnet/router health, provider credentials, local Ollama, and fallback policy.

For response headers, safe probes, and no-secret support context, use API troubleshooting.

Cutover checklist

Move one client at a time.

  1. Create a hosted account and generated sk_sage_* key.
  2. Set OPENAI_BASE_URL=https://api.tekiz.ai/v1 in one development client.
  3. Send a sage-router/auto chat completion, then consult /v1/models before choosing another profile.
  4. Confirm usage, quota, and status before moving agent jobs.
  5. Keep existing gateway fallback in your deployment plan until Tekiz provider credentials and profiles are healthy.