Connect Claude Code in one click →
The guided connect page creates a managed key for your account and writes the
env block of ~/.claude/settings.json for you — no terminal work./v1), pass your AI Reserve key
as the auth token, and make sure ANTHROPIC_API_KEY is empty so the CLI
doesn’t prefer it:
env block of
~/.claude/settings.json) to make the routing permanent. Requests hit
/v1/messages — including count_tokens — so the full agent
loop, tool use, and prompt caching work unchanged.
Why the [1m] suffix?
When Claude Code talks to a gateway
it can’t verify 1M support, so it budgets a 200K window by default — the context meter
fills five times faster than first-party even though the gateway serves the full
window. The [1m] id form tells Claude Code to budget the same 1M-token
context it has first-party. It works on every extended-context model
(claude-sonnet-4-6, fable-5, opus-4-8):
anthropic-beta: context-1m-2025-08-07 opt-in, which the gateway relays to
Anthropic — and the gateway also accepts the [1m] id form directly, so
either convention works. Selecting a 1M variant from the /model picker is
known not to stick behind a custom base URL; pin it through the environment variable
instead. Tokens are billed at the model’s normal rates.
Claude Agent SDK
The embeddable agent runtime takes the same three variables viaoptions.env: