Guides
One task per page, each written four ways: a CLI command, an SDK call, an HTTP request and an MCP tool.
Guides
One key authenticates every request. sk- keys resolve to a user and belong on a server; pk- keys resolve only to an organisation and are safe in a browser.
export HANZO_API_KEY=sk-... # console.hanzo.ai
hanzo auth login # or sign in through Hanzo IAMFour surfaces, one contract
The CLI, the SDKs, the HTTP API and the MCP tools are generated from the same OpenAPI document. A command, a method, a path and a tool that do the same thing are the same operation under four names, so what you learn on one surface holds on the others.
| Surface | Address |
|---|---|
| CLI | hanzo <capability> <verb> |
| SDK | a method per operation, in your language |
| HTTP | https://api.hanzo.ai/v1/<capability> |
| MCP | one tool per capability, dispatched by operation |
Tasks
Each page below does one thing, and does it on all four surfaces.
Hello
Identity — prove the key works and print who it belongs to.
Chat
One completion.
Money
Balance, then the usage that moved it.
Store
KV round-trip — create a store, read it back, delete it.
Agent
Create an agent, run it, read the run back.
Tools
List the MCP tools this key can reach.
Every capability the API serves is in the reference, and the same key reaches all of it.
How is this guide?