CC Switch
Add RouteMux as a provider in CC Switch — and avoid the /v1 trap it is known for.
CC Switch stores one entry per provider and swaps the active one. Add RouteMux as a new Anthropic-compatible provider.
Configure
| Field | Value |
|---|---|
| Request URL / Base URL | https://api.routemux.com |
| API key | your RouteMux key (sk-...) |
| Model | any slug from GET /v1/models, e.g. anthropic/claude-sonnet-5 |
The /v1 trap
Filling the request URL as https://api.routemux.com/v1 is the most common CC Switch
misconfiguration. The Anthropic client appends /v1/messages, producing /v1/v1/messages.
RouteMux normalises that path instead of returning 404, so it will appear to work — but the correct value is the bare origin, and other providers you switch to will not be as forgiving.
Two headers, one key
CC Switch may send your key in both Authorization and x-api-key. That is fine when both
carry the same value — RouteMux de-duplicates them. Two different values return
400 AMBIGUOUS_API_KEY, which usually means a stale key is still stored in one field.
Model ids with date snapshots
Anthropic's own convention includes a date suffix (claude-haiku-4-5-20251001), and CC
Switch's default test model follows it. RouteMux slugs do not require the suffix — use what
GET /v1/models returns.