AI Accounts
Link the AI accounts you already pay for and see every lane in one place — usage, spend, and remaining quota across desktop, web, and CLI, beside your Hanzo usage.
AI Accounts
Most people already hold a subscription or two before they arrive. AI Accounts links those accounts to your Hanzo profile and merges what they report into one board, so "how much have I used this week" has a single answer instead of three tabs.
This is a console surface — console.hanzo.ai → AI Accounts. For an org bringing its own provider keys so Hanzo can serve those models, see Connections instead.
Lanes
| Lane | Link it with |
|---|---|
| Hanzo | Nothing — it is your own account, read from the billing ledger |
| OpenAI / Codex | An API key, an OAuth sign-in, or a session cookie header |
| Anthropic / Claude | An API key, an OAuth sign-in, or a session cookie header |
The three link modes are api (paste a key), oauth (sign in), and web (paste
a session cookie header — how a consumer subscription with no API key reports its
usage). Whichever you choose, the credential is sealed server-side; the browser
never holds it, and the accounts list only ever returns a masked label.
Overview
The overview merges both sides of the feed. Provider lanes report what their own usage APIs expose — session and weekly quota consumed, cost, tokens, and requests. The Hanzo lane comes from the real commerce ledger over the last 30 days, with your top models broken out.
A lane that cannot be read says so rather than showing a zero: the board fails soft per lane, so one unreachable provider never blanks the rest.
Machines
Usage arrives from wherever you work — desktop, CLI, web. The Machines tab shows the surfaces reporting under your account, which is how the same subscription counted twice on two laptops becomes visible.
Routing
The routing toggle is your preference for whether Hanzo's smart routing is used on your sessions. It resolves against the org: if your organization has auto routing switched off, that wins and the toggle is disabled; otherwise your choice overrides the org default.
It is a preference, not a policy edit. Calls that explicitly ask for
"model": "auto" still follow the platform routing flag — the policy itself
lives in Router.
Accounts
Link, relink, and remove lanes here. Removing a lane deletes the stored credential and drops that lane from the board; historical Hanzo usage is unaffected, because it was never the provider's to begin with.
Related
- Connections — org-level provider keys, sealed to KMS, so Hanzo can serve those models
- Router — the routing policy the toggle opts into
- Usage — Hanzo's own metering
- Billing — the ledger the Hanzo lane reads
How is this guide?
Connections
Bring your own OpenAI, Anthropic, or Google account — Hanzo serves those models on your account and folds the spend into one usage board. Keys are sealed to KMS server-side.
Knowledge
Your wiki, your agents' memory, and your ingested sources in one store — searchable as a single retrieval surface and drawn as one graph.