1. Create a gateway key
In the console, open API keys and create one. It is scoped to the workspace you are in.2. Point Claude Code at Nemu
ANTHROPIC_AUTH_TOKEN, not ANTHROPIC_API_KEY. The first sends
Authorization: Bearer, which is what a Nemu gateway key expects. Nemu also
accepts x-api-key, so ANTHROPIC_API_KEY works, but the bearer header is the
one to reach for.
To keep it out of your shell profile, put it in ~/.claude/settings.json
instead. Values there win over shell exports.
The base URL ends in
/anthropic. Claude Code appends /v1/messages itself.
Setting it to a bare https://api.nemu.cc also works for inference, but the
/anthropic prefix is what serves the Anthropic-shaped model list, so prefer
it.3. Choose a model
Claude Code’s/model picker can be filled from Nemu:
/model lists the models enabled in your workspace by their
gateway name. Without it, name one directly:
GET /anthropic/v1/models reports the exact strings that are accepted:
claude-sonnet-4-5 to whatever should actually serve it.
Verifying the connection
content array means Claude Code will work. A 404 saying
Invalid URL means the base URL is missing the /anthropic segment. A 404
naming the model means it is not enabled in this key’s workspace.
What Claude Code asks Nemu for
Nemu serves all four. Fast-mode availability and WebFetch domain checks go to
Anthropic directly and never touch the gateway.