Using Claude Code

Compatibility: doesn't work with luv13 today. Claude Code only talks to endpoints in Anthropic's formats: the Anthropic Messages API (/v1/messages), Amazon Bedrock InvokeModel, or Google Cloud's Agent Platform rawPredict. luv13 serves only the OpenAI-style POST /v1/chat/completions, and POST /v1/messages returns 404. Claude Code's docs also say Anthropic doesn't support routing Claude Code to non-Claude models through any gateway, and every luv13 model is a non-Claude model. This page explains why, what you'd see if you tried, and which tools to use instead.

Why it doesn't work

Claude Code's gateway docs (the "Gateway compatibility guide", read 2026-09-30, when Claude Code's changelog listed v2.1.285 as the latest) say a gateway must expose at least one of these formats:

OpenAI Chat Completions isn't on that list. The request and response shapes are different: Anthropic's format sends system separately, uses content blocks and anthropic-version headers, and streams different event types. So Claude Code can't use luv13 even though luv13 accepts a bearer token.

The docs also say that Anthropic "doesn't endorse, maintain, or audit third-party gateway products, and doesn't support routing Claude Code to non-Claude models through any gateway."

What you'd see if you tried

Say you set:

export ANTHROPIC_BASE_URL=https://api.luv13.ai
export ANTHROPIC_AUTH_TOKEN=$LUV13_API_KEY

Claude Code would send its inference requests to https://api.luv13.ai/v1/messages?beta=true. You can reproduce what luv13 does with that request using the same check Claude Code's docs recommend:

curl -sS -w '\n%{http_code}\n' -X POST "https://api.luv13.ai/v1/messages" \
  -H "Authorization: Bearer $LUV13_API_KEY" \
  -H "anthropic-version: 2023-06-01" \
  -H "content-type: application/json" \
  -d '{"model": "luv13/glm-5.3-flash", "max_tokens": 16, "messages": [{"role": "user", "content": "hi"}]}'

On 2026-09-30 this returned HTTP 404 with an HTML "404 Not Found" page. Setting the base URL to https://api.luv13.ai/v1 doesn't help, because Claude Code adds /v1/messages itself, giving /v1/v1/messages, which also returns 404.

Check that your luv13 key works

Your key and model work fine with tools that speak OpenAI's format. If you don't have a key yet, the Quickstart shows how to get one. The model used below is GLM-5.3 Flash. Confirm both with the standard checks:

Run these two checks in a terminal before you touch the tool. They take a few seconds and rule out key and model problems.

1. The model id exists. This call needs no key:

curl -s https://api.luv13.ai/v1/models

The list should include "id":"luv13/glm-5.3-flash".

2. Your key works for chat. Set the key in your shell first (export LUV13_API_KEY="your luv13 key"), then run:

curl -s https://api.luv13.ai/v1/chat/completions \
  -H "Authorization: Bearer $LUV13_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "luv13/glm-5.3-flash",
    "messages": [{"role": "user", "content": "Reply with the word ready."}],
    "max_tokens": 20
  }'

With a valid key you should get back a JSON chat completion whose choices[0].message.content holds the reply, plus a usage block. If you see {"error":{"code":401,"message":"unauthorized","type":"invalid_auth"}} instead, the key is missing or wrong, and no tool setting will fix that.

What to use instead

Common errors

General tip: remove ANTHROPIC_BASE_URL and ANTHROPIC_AUTH_TOKEN from your shell profile and from any env block in ~/.claude/settings.json if you added them while testing, so Claude Code goes back to its normal login.

Sources

• Claude Code docs, "Other LLM gateways" (read 2026-09-30)
• Claude Code docs, "Gateway compatibility guide" (API formats) (read 2026-09-30)
• Claude Code docs, "Connect Claude Code to an LLM gateway" (variables, verification request, troubleshooting table) (read 2026-09-30)
• Claude Code changelog (latest entry 2.1.285 on 2026-09-30)
• luv13's /v1/messages checked live with curl on 2026-09-30 (404).

Related: Endpoints, OpenAI-Compatible APIs.