Anthropic-compatible setup

Claude Code and Claude-style clients can use ANTHROPIC_BASE_URL=https://api.tekiz.ai with a generated sk_tekiz_* key for hosted account control.

Use an Anthropic subscription

Connect the Anthropic access you already have. A route requires an active subscription before TEKIZ.AI can use it.

Keep working when an account is busy

When a provider account or model reaches a limit, TEKIZ.AI can choose another working route that supports the request.

Configure Claude Code

export ANTHROPIC_BASE_URL=https://api.tekiz.ai
export ANTHROPIC_API_KEY=sk_tekiz_your_generated_key

# Claude Code uses Anthropic-compatible messages traffic.
# Keep provider keys on your router host or in the hosted account path.
claude --append-system-prompt "Use TEKIZ.AI for model routing"

Optional Claude Code settings file

Merge this JSON into ~/.claude/settings.json. Keep the API key in your shell, secret manager, or service environment; do not paste this file example into a terminal.

{
  "env": {
    "ANTHROPIC_BASE_URL": "https://api.tekiz.ai"
  }
}

Backups that support tool calls

Coding profiles only switch to models that can handle the tool calls Claude Code needs.

Send files to services that accept them

Image, audio, video, and document requests are matched to models that can handle those files.

Use accounts you are allowed to use

TEKIZ.AI uses only the Claude and Anthropic access you authorize. You can also use hosted routing through your TEKIZ.AI account.

Change routed models from one Claude Code setup

Claude Code keeps the same Anthropic-compatible setup while TEKIZ.AI Router checks availability, uses more than one authorized key, and switches to local or cloud backups when needed.

Next steps

Create an API key, open the Claude Code guide, review Anthropic-compatible routing, or request Anthropic access review.