routiform-claude-code-setup

Connect Claude Code to Routiform

Claude Code talks the Anthropic Messages API. Routiform serves that API at /v1/messages, so Claude Code needs no plugin — only a base URL and a token.

Prerequisites

• Routiform running and reachable. Default: http://localhost:20128. Confirm with curl -s -o /dev/null -w '%{http_code}\n' http://localhost:20128/v1/models → 200.
• At least one provider connection configured at /dashboard/providers. Without one, requests reach the gateway and fail with No credentials for provider: <id>.
• Claude Code installed: npm install -g @anthropic-ai/claude-code.

Steps

1. Create a gateway API key. This is Routiform's own key, not a provider key. Dashboard → API Manager → create, or:

routiform key create claude-code

Copy the sk-... value. It is shown once.

2. Point Claude Code at Routiform. Both variables are required — the token is what Routiform authenticates, and Claude Code will otherwise try to use a stored Anthropic login.

export ANTHROPIC_BASE_URL="http://localhost:20128"
export ANTHROPIC_AUTH_TOKEN="sk-your-routiform-key"

Add them to ~/.zshrc or ~/.bashrc to survive a new shell. To scope it to Claude Code alone, put them in ~/.claude/settings.json instead:

{
  "env": {
    "ANTHROPIC_BASE_URL": "http://localhost:20128",
    "ANTHROPIC_AUTH_TOKEN": "sk-your-routiform-key"
  }
}

Leave /v1 off ANTHROPIC_BASE_URL — Claude Code appends /v1/messages itself, which is why the dashboard's own CLI Tools page writes the bare origin. Routiform happens to answer the doubled /v1/v1/messages too, so a base URL ending in /v1 will not break; it is just wrong on paper and will confuse the next person reading your shell profile.

3. Choose what serves the request. Routiform maps the incoming Claude model name onto whatever you configured. To pin a specific one, set ANTHROPIC_MODEL to an id from GET /v1/models, or build a combo at /dashboard/combos and let Routiform pick.