Connect Coding Tools
Pointing Claude Code, Codex, Cursor and Continue.dev at the gateway with a base-URL swap, on your existing subscription.
Connect Coding Tools
The coding-tools track points developer surfaces at the gateway with a base-URL swap. Your provider subscriptions keep paying -- the gateway observes and optimizes, and your existing key or seat token is forwarded byte for byte.
This is passthrough traffic. The request is carried byte-identically in both directions on your own credential, with no DevZero header added and no DevZero header returned. It is deliberately outside the published keyed contract.
What you get from it
Passthrough traffic is still telemetry. You get per-request token counts, cost, latency, cache outcomes, session reconstruction and per-developer attribution -- and on a subscription seat the value is denominated in rate-limit headroom rather than dollars, because no bill moved.
What you do not get on this track is the keyed product path: routing profiles, guardrail enforcement and the keyed surfaces all require a DevZero issued key. See API access for that.
Base URLs
Substitute your own gateway address. In-cluster that is the gateway service; on
Docker or a local binary it is localhost on the port for the surface you want.
Claude Code speaks the native Anthropic wire, so it goes to the Anthropic listener.
export ANTHROPIC_BASE_URL="http://localhost:8081"Your ANTHROPIC_API_KEY stays unchanged. A Claude seat token is a
subscription credential and keeps the passthrough; the gateway does not
reshape it.
Claude Code does not send DevZero's session header. On the native Anthropic surface the gateway falls back to Claude Code's own client session id, which is precisely the client that fallback exists to serve -- so sessions still reconstruct correctly without any configuration.
The install flow lists the clients it has snippets for: Claude Code, Codex CLI, Cursor, Continue.dev, SDK or curl, and a generic backend service. The snippet you copy from the dashboard is pre-filled with your own gateway's address.
Verification
The coding-tools track verifies on any traffic reaching the installation -- not on a specific key. Open a coding session and make one request; the wizard shows it within a few seconds.
Verification is passive. Nothing in the product will originate a model request on your behalf, so the wizard waits for a request you make.
Optimization on this track
Coding-client traffic can bypass the caches, and that is intentional: a coding conversation is long, mostly unique, and heavily dependent on the provider's own prompt cache, which a response cache cannot help and can hurt.
What does apply is the subscription-regime value story: tokens the gateway does not spend extend how far your prepaid seats stretch. Any dollar figure attached to that is an estimate and is labelled as one. See AI spend.
Do not send keyed traffic to the wrong listener
The native OpenAI listener declares no keyed product surface. A request carrying
an sk-dz- key aimed at it takes the subscription passthrough and gets none of
the keyed product path -- no guardrail enforcement, no routing profile, no keyed
surface. The spend and allowlist gate on the key still runs, so the traffic is
not exempt from governance.
Keyed OpenAI-shaped traffic belongs on the OpenAI-compatible listener; keyed
Anthropic-shaped traffic belongs on POST /v1/messages on the Anthropic
listener.