Documentation
Build Anything with Hanzo. Every model, every tool, one key — in our cloud or on your own machine.
Build Anything with Hanzo
Over 400 models, one platform. Pick how much you want to type.
Build me a multiplayer snake game with a
leaderboard, and deploy it.Every model, one key
Browse every model we serve — the catalogue is live, so the id you copy and the rate beside it are the gateway's current answer — or see what a request costs before you send one.
The platform, by domain
Every capability has one name and one route — /v1/<name> — and lives in exactly
one domain. Nothing is duplicated, so nothing is ambiguous.
Intelligence
Every model, agent and tool you can call — one key, one endpoint, and the standard chat-completions shape, so a client you already have works unchanged.
Make your first callIdentity & Trust
Who someone is, what they may touch, and where secrets stay. Every other domain reads its caller's identity from here.
Set up an orghanzo auth login && hanzo keys create --name prodObservability
Metrics, logs, traces and evals for everything above — including the model calls, tagged by org and project so tenants stay separate.
See what is happeningCommerce
Turn usage into money — meter it, price it, bill it. The same ledger the gateway debits when you call a model.
Meter usagehanzo billing balanceApplications
The finished products built on the domains above — useful on their own, and a worked example of the platform if you are building your own.
Open the appshanzo devTake it with you
The cloud above and the one you can run yourself are the same
software — same binary, same contract, same /v1 routes. Bring
your own GPU or Kubernetes, or mine on any device.
curl -fsSL hanzo.sh | bashThis is V8 · Open Edition, specified in HIP-0127: one contract, many bindings, thin clients, and a wire — never FFI — between languages. See Engineering Philosophy for the why.
Build with it
- The
hanzoCLI — one ~15 MB Rust binary that talks to any live cloud: prod, laptop, or self-host - SDKs — Python, TypeScript, Go, Rust and more, all derived from one contract
- API reference — every endpoint, generated from its spec
- ZAP protocol — Zero-Copy App Proto, the wire the Go and Rust halves speak
- Zen models — frontier open-weight models, 4B edge to 1T+ reasoning
- Architecture — one binary, one contract, and why
Resources
- GitHub — source code and open-source projects
- console.hanzo.ai — dashboard and API keys
- hips.hanzo.ai — Hanzo Improvement Proposals
How is this guide?