CC Switch

Three fields and two dropdowns. https://api.kunavo.com as the endpoint, your sk-kn-… key, and — the part most guides omit — leave API Format on Anthropic Messages (Native) and Auth Field on ANTHROPIC_AUTH_TOKEN. Kunavo speaks the Messages API natively, so no local routing is involved on the Claude Code side.

Provider Name   Kunavo
API Key         sk-kn-...
API Endpoint    https://api.kunavo.com      <- service root, no /v1, no trailing slash

Advanced Options
  API Format    Anthropic Messages (Native) <- the default; do NOT switch
  Auth Field    ANTHROPIC_AUTH_TOKEN (Default)

Step by step (Claude Code tab)

1. Create a key at /app/keys and copy it — it is shown once.
2. Open CC Switch on the top-level Claude Code tab and click the plus button. Keep the default Custom Configuration rather than a preset.
3. Fill Provider Name, API Key, and API Endpoint = https://api.kunavo.com.
4. Expand Advanced Options and confirm API Format is Anthropic Messages (Native) and Auth Field is ANTHROPIC_AUTH_TOKEN (Default). Both are the defaults; the point is to check, not to change.
5. Save, then Activate. The card should not show a Needs Routing marker — that marker only appears on providers whose protocol has to be translated.

Why there is no “Needs Routing” marker

CC Switch's local route exists to bridge protocols. Claude Code sends Anthropic Messages requests to /v1/messages; a gateway that only exposes OpenAI Chat Completions or the Responses API cannot answer one, so the route converts the request on the way out and converts the response on the way back. That conversion is where streaming events, tool calls and thinking config get re-shaped — it works, and it is one more moving part between your editor and the model.

Kunavo serves POST /v1/messages directly, so on the Claude Code side there is nothing to convert: the provider stays Anthropic Messages (Native) and the route is not in the path at all. It also serves POST /v1/chat/completions and POST /v1/responses under the same key, which is what makes the Codex direction below possible.

Running Claude models inside Codex

This is the direction the other provider guides do not cover. Codex talks to the OpenAI Responses API, so pointing it at a /v1/messages endpoint directly returns 404 — CC Switch solves it by keeping Codex on the local route and translating. On the Codex tab there is no Anthropic preset, so this is a Custom Configuration too:

Provider Name      Kunavo
API Key            sk-kn-...
API Request URL    https://api.kunavo.com
Default Model      claude-sonnet-4-6

Advanced Options
  Upstream Format  Anthropic Messages (routing required)

Model mapping

CC Switch maps Claude Code's three tiers onto real model ids. Fill all three plus the Default fallback model — unmatched requests otherwise pass through under the original Claude name and error at the upstream. Rates are USD per 1M tokens, input / output, read live from the catalog.

Verify before you debug the app

One pair of requests settles whether a failure is the key, the endpoint or CC Switch. If both return 200, anything still broken is a field in the form — and it is nearly always Auth Field or a /v1 that should not be in the endpoint.

# Settles whether a failure is the key, the endpoint, or CC Switch.
# 200 + a JSON list of model ids means the same key works in the app.
curl -sS https://api.kunavo.com/v1/models \
  -H "Authorization: Bearer sk-kn-..."

# The Anthropic face, which is the one the Claude Code tab actually calls.
curl -sS https://api.kunavo.com/v1/messages \
  -H "Authorization: Bearer sk-kn-..." \
  -H "anthropic-version: 2023-06-01" \
  -H "content-type: application/json" \
  -d '{"model":"claude-haiku-4-5","max_tokens":16,
       "messages":[{"role":"user","content":"ping"}]}'

Reference

CC Switch is open source at github.com/farion1231/cc-switch. The field names and behaviour above are from its own guides — the Claude Code routing guide and the Codex routing guide, both of which state they apply to 3.17.0 and later. On older versions the form differs; check the app's About panel if a field named here is missing. Kunavo's side is documented under the Messages API, chat completions and the integrations hub.