OpenClaw skill setup

Merge the TEKIZ.AI provider into OpenClaw’s native model configuration. Use the hosted endpoint with an active TEKIZ.AI key, or replace both endpoint and credential boundary with your local router.

Works with both common client formats

OpenClaw tools can use OPENAI_BASE_URL=http://localhost:8790/v1 or ANTHROPIC_BASE_URL=http://localhost:8790. Provider credentials stay on the router computer.

Use the Codex account already connected to OpenClaw

TEKIZ.AI can read OpenClaw-managed Codex authentication from the profile store or environment. It does not ask you to sign in through a separate device-login page.

Configure OpenClaw

This example uses a hosted TEKIZ.AI key. Add the provider object below to OpenClaw, then validate the merged configuration. For your own provider credentials, run a local router and change both the base URL and API key.

# Keep the key in a shell, secret manager, or service environment.
export TEKIZAI_API_KEY=sk_tekiz_your_key

# Validate the merged JSON before restarting a managed OpenClaw service.
openclaw config validate

# For generic OpenAI-compatible tools running beside OpenClaw:
export OPENAI_BASE_URL=https://api.tekiz.ai/v1
export OPENAI_API_KEY="$TEKIZAI_API_KEY"

Optional native provider object

Merge this object under models.providers in ~/.openclaw/openclaw.json. It is JSON only. Do not paste it into a terminal or overwrite your existing configuration.

{
  "tekizai": {
    "baseUrl": "https://api.tekiz.ai/v1",
    "apiKey": "${TEKIZAI_API_KEY}",
    "api": "openai-completions",
    "models": [
      { "id": "tekizai/auto", "name": "TEKIZ.AI Auto" },
      { "id": "tekizai/frontier", "name": "TEKIZ.AI Frontier" },
      { "id": "tekizai/fusion", "name": "TEKIZ.AI Fusion" }
    ]
  }
}

Prefer local models when they fit

Keep Ollama and private Tailnet models first, then use a connected cloud provider when the task needs more context or a stronger model.

Credential load balancing across your keys

Add more than one key or account. TEKIZ.AI shares requests across those that are working and pauses only the one that fails.

Use accounts you are allowed to use

Keep authorized provider credentials on a router you control. A hosted TEKIZ.AI key uses the models available to your account.

Keep model setup in one place

A router you run can connect OpenClaw to local models, approved cloud APIs, and coding accounts through one address. Hosted access uses a separate TEKIZ.AI account key and the models available to that account.

Next steps

Create an API key, review the local router setup, copy the hosted quickstart, or estimate routing fit.