Claude Code
Claude Code is Anthropic’s terminal coding agent. Override its base URL and auth token to send every request through Merge Gateway, with routing policies, cost governance, and full request observability in the Gateway dashboard.
Before you start
- Install Claude Code:
curl -fsSL https://claude.ai/install.sh | bashornpm install -g @anthropic-ai/claude-code - Grab an API key from gateway.merge.dev/settings/api-keys
- Pick the Claude models you want available. Gateway model names take the form
provider/model, for exampleanthropic/claude-opus-4-7andanthropic/claude-sonnet-4-6. Browse the full catalog withGET /v1/modelsor in the dashboard.
Configure Claude Code
Export environment variables in your project shell
In a terminal scoped to your project, set:
ANTHROPIC_API_KEY must be explicitly empty, or Claude Code prefers it over ANTHROPIC_AUTH_TOKEN and bypasses Gateway. The ANTHROPIC_DEFAULT_*_MODEL variables map Claude Code’s opus, sonnet, and haiku tiers to the Gateway provider/model slugs you want to use.
If you previously signed in to Claude Code with Anthropic credentials, run /logout and relaunch so the env vars take effect.
Launch Claude Code
Run claude in your project. The new session uses Gateway via the env vars you exported above.
Verify with /status
Run /status. Confirm the output shows:
Auth token: ANTHROPIC_AUTH_TOKENAnthropic base URL: https://api-gateway.merge.dev/v1/anthropic
Then send a quick prompt to confirm streaming works, and ask Claude Code to make a small code change to verify tool calls and file edits flow through Gateway. The request appears in your Gateway dashboard within a few seconds.
Claude Desktop app
Anthropic’s Claude Desktop app — including its Chat, Cowork, and built-in Claude Code surfaces — can also route through Gateway. Unlike the CLI, it isn’t configured with ANTHROPIC_BASE_URL. There are two ways to point it at Gateway: Developer mode (manual, per user) or managed configuration (MDM, for fleets).
Developer mode (manual, per user)
The fastest way to point Claude Desktop at Merge Gateway:
Add the Gateway endpoint
In the developer inference settings, add an endpoint and set it to Gateway’s Anthropic-compatible base URL:
The path must end in /v1/anthropic — Gateway serves the Anthropic Messages API under that prefix.
Add your API key
Add the API key for that endpoint — your key from gateway.merge.dev/settings/api-keys.
Select a model and test
Pick a Gateway model, then send a prompt. The request appears in your Gateway dashboard within a few seconds.
Exact menu labels vary by app version, but the flow is always Developer mode → add endpoint → add API key.
Managed configuration (MDM, for fleets)
To roll Gateway out to many users at once, distribute a managed configuration file instead of having each person enable Developer mode. See Anthropic’s Claude Desktop configuration reference for how the configuration is delivered on each platform. Point it at Gateway with the gateway inference provider:
inferenceGatewayBaseUrlmust end in/v1/anthropic.modelDiscoveryEnabled: truepopulates the in-app model picker from Gateway’sGET /v1/anthropic/v1/models. To pin a fixed list instead, setinferenceModelsto the Gatewayprovider/modelslugs you want.inferenceGatewayAuthSchememay bebearerorx-api-key; Gateway accepts both. UseinferenceCustomHeadersfor any tenant or routing headers your setup needs.
Caveats
ANTHROPIC_API_KEY must be empty
Claude Code reads both ANTHROPIC_API_KEY and ANTHROPIC_AUTH_TOKEN. If ANTHROPIC_API_KEY is set to anything non-empty, it wins and Claude Code bypasses your Gateway base URL. The explicit export ANTHROPIC_API_KEY="" in the recipe above clears any inherited value for the session.
Mapping Claude Code's model tiers
The ANTHROPIC_DEFAULT_OPUS_MODEL, ANTHROPIC_DEFAULT_SONNET_MODEL, and ANTHROPIC_DEFAULT_HAIKU_MODEL env vars override the model identifier Claude Code sends in each request. Set them to Gateway provider/model slugs (anthropic/claude-opus-4-7, anthropic/claude-sonnet-4-6, anthropic/claude-haiku-4-5-20251001) so Gateway can resolve them. Without these overrides Claude Code sends the bare Anthropic alias (for example claude-sonnet-4-6), which Gateway accepts but does not let you steer per request.
Let Gateway choose the model
Instead of hard-picking a model, point at a routing policy and let Gateway select the vendor and model per request based on your rules (cost, performance, or prompt complexity). Useful when you want cheap models for simple edits and stronger models for hard problems without switching by hand.
Persisting the configuration
The recipe above lives in your shell, so it applies only to that terminal. To persist it, add the same export lines to your shell profile (~/.zshrc, ~/.bashrc, or ~/.config/fish/config.fish), or use a project-scoped .claude/settings.local.json with an env block (Claude Code does not read .env files).
Tool calling
Claude Code relies on tool calls to read and edit files. Tool calling works through Gateway for any model whose capabilities.supports_tool_calling is true on the chosen vendor route. See Tool calling.