Claude Code
Keep your Claude subscription and see every session.
Install a Nautili Proxy Gateway and point Claude Code at it. You keep your own key or seat, Claude Code works the way it did, and Nautili records the tokens, cost and latency of every request, and the developer on a Claude login.
From install to first session
In the dashboard, open Connections → Install gateway and follow the four steps. Nautili doesn't send test traffic. It waits for your first real request and shows it within a few seconds.
All integrationsSelect deployment
Self-host with Helm or Docker Compose, or pick Hosted Gateway, where Nautili runs a dedicated gateway for your team. The wizard pre-selects Shared Gateway when it's available; for Claude Code, pick one of the others.
Install gateway
Run the install command for Helm or Docker Compose. For a Hosted Gateway there's no command: click Provision gateway.
Connect to your gateway
Pick the Coding tools track, then Claude Code, and copy the snippet. It already has your gateway's address, and your key or seat token stays the same.
Verify traffic
Ask Claude Code something. The wizard shows Traffic detected, then First request received.
Point Claude Code at your gateway
Set ANTHROPIC_BASE_URL to your gateway and carry on. The gateway forwards your key or seat token as-is. Use your Proxy Gateway for this, since the Shared Gateway only accepts Nautili keys or a Nautili sign-in token.
Connect coding toolsEverything else stays the same
- Your Claude subscription or API key
- Claude Code and the way you work
- Your prompts and responses
Watch a session come in
Run Claude Code through your gateway and the work shows up on the Sessions page as you go, one request at a time.
See every session
Nautili records the tokens, cost, latency and cache outcome of each Claude Code request, and groups them into sessions by Claude Code's own session ID. On a Claude subscription login it also knows the developer and links them to the team member with the same email. On a plain API key, set X-Dz-User in ANTHROPIC_CUSTOM_HEADERS.
Attribution docsObserved on your key, governed on ours
On your own key or seat, the gateway forwards your token as-is and records the request. Budgets, rate limits and routing profiles need a Nautili-issued key.
Keys and accesspassthrough
On your own key or seat
- Your subscription keeps paying
- Tokens, cost, latency and cache per request
- Sessions, and the developer on a Claude login
- Model allowlists, through a seat guardrail
- Not available: Budgets, rate limits and routing profiles
keyed
On a Nautili-issued key
- Routing profiles per team, identity or key
- Budgets, rate limits and model access lists
- Metering and attribution on every keyed request
- Nautili response headers on each reply
Frequently asked questions
Questions teams ask before they point Claude Code at a gateway.
Read the docsCan Claude Code use the Shared Gateway?
Not with your subscription or your own Anthropic key. Every team gets a Shared Gateway, but it only accepts Nautili keys or a Nautili sign-in token. For Claude Code, install a Proxy Gateway: self-host it with Helm or Docker Compose, or use a Hosted Gateway, which Nautili runs for your team.
Does Nautili change my Claude Code requests?
Only minimal protocol fixes, and your credential is untouched. The gateway adds anthropic-version if it's missing, turns a [1m] model suffix into the matching context-1m beta header, and strips any X-Dz headers before the request reaches Anthropic. A seat guardrail can also apply a model allowlist. Budgets, rate limits and routing profiles only apply to Nautili-issued keys.
Do I need a separate Nautili key to use Claude Code?
No. Your ANTHROPIC_API_KEY or Claude seat token stays as it is. Once the Proxy Gateway is installed, the only thing you change is the base URL.
Does it work with my Claude subscription?
Yes, and your subscription keeps paying. A seat has no per-request bill, so Nautili shows seat utilization and an estimate at API prices of what the traffic would have cost.
How are Claude Code sessions grouped?
By Claude Code's own session ID. Claude Code doesn't send Nautili's X-Dz-Session-Id header, so the gateway reads the session ID Claude Code puts in each request and groups by that. You don't configure anything.
How does Nautili know which developer sent a request?
On a Claude subscription login, the gateway reads the account from the request, pulls its email and name, and links it to the team member with that email. Use People → Linking when the emails don't match or the person isn't in the workspace yet; until then the row shows the account's name or email. On a plain ANTHROPIC_API_KEY, the developer shows as a dash unless you send X-Dz-User through ANTHROPIC_CUSTOM_HEADERS.
Can I tag Claude Code requests?
Yes. Set ANTHROPIC_CUSTOM_HEADERS to one or more lines like X-Dz-User: priya or X-Dz-Project: checkout. The gateway reads X-Dz headers on every request, including traffic on your own key or seat, and strips them before the request reaches Anthropic. A project tag shows up as a department in Attribution.
Does Nautili's response cache apply to Claude Code?
Coding traffic can skip it, on purpose. A coding conversation is long and mostly unique, and it relies on Anthropic's own prompt cache. A response cache can't help there and can get in the way.
What do I need an issued key for?
Budgets, rate limits and routing profiles. On your own key or seat, Claude Code still gets full telemetry and sessions, the developer on a Claude login, and a seat guardrail can apply a model allowlist.
Claude Code returns invalid_model_id. What do I do?
That comes from an older self-hosted gateway, when Claude Code sends its own model name on a Nautili-issued key. Upgrade the gateway, or set ANTHROPIC_MODEL to the catalog spelling, for example anthropic/claude-sonnet-4.5. Current gateways accept Claude Code's own model names.
Connect Claude Code to your gateway
Install a Proxy Gateway and set one base URL. Your first request shows up within seconds.