Capabilities
Every Hanzo capability — 131 of them, 2481 operations, generated from the OpenAPI document.
One cloud, one credential. 131 capabilities, and each is one word that names the same thing everywhere — its address, its command group, its client class, its MCP tool, this page and its HIP. 125 of them speak REST over HTTPS and carry 2481 operations, generated straight from the OpenAPI document that also generates the SDKs, the CLI and the MCP tools.
The other 6 carry no operation in it. Most answer somewhere a document cannot describe — a port, a /.well-known/ convention, another app's router, a control plane the address relays onto — and two are the operator surface, which serves ordinary HTTP and is withheld because its audience is not a customer. All 6 are GA and run in every deployment; each page names its own address and prints no endpoint table it does not have.
The names below are the canonical ones. cloud also answers at the other spelling of a name that has one — /v1/sandboxes reaches /v1/sandbox — so an older client keeps working; only the canonical name is published, documented and generated from.
Authentication
Every product accepts the same bearer credential — a Hanzo IAM JWT or a sk- secret key.
curl -H "Authorization: Bearer $HANZO_API_KEY" https://api.hanzo.ai/v1/modelsGet a key at console.hanzo.ai. New here? Get started walks the same journeys as CLI, SDK, HTTP and MCP.
Start anywhere
Every product page opens with a Quickstart: what the product is, in its own words, and its first call shown as the CLI, an SDK, raw HTTP and an MCP tool. For 116 of the 125 that first call is a read that needs nothing but the key — paste it and it answers. The other 9 take an argument, and say so rather than printing a sample that cannot run.
Identity & trust
who you are · what you may touch · where secrets live — 16 capabilities.
Hanzo's identity provider: users, organizations, applications, and the OIDC/OAuth2 endpoints every Hanzo service authenticates against. · 162 operations
Your own account: API keys you mint and revoke, and org onboarding. · 11 operations
The access decision behind an org-scoped call: who may do what, where, answered allow or deny. · 3 operations
Secret custody: your org's secrets sealed at rest, plus threshold signing. · 5 operations
Secret scanning for your code: submit sources, get findings, masked never raw. · 7 operations
What your org may run: what the plan grants, and which of those products are switched on. · 3 operations
Your org's tamper-evident audit trail: every security-relevant event, hash-chained and readable. · 1 operations
Your KYC/KYB onboarding, accreditation records, and the evidence trail behind them. · 17 operations
Your trust centre: the controls you publish, the coverage they compute to, the documents a reviewer asks for, and who you send data to. · 17 operations
HANZO RISK's model plane: the per-organisation feature surface and the per-organisation models trained on it. · 11 operations
The per-org dataset plane of /v1/risk: a dataset is a VERSIONED, IMMUTABLE snapshot of one tenant's own event surface, and this is where it is declared, materialised, described, exported and disposed of. · 7 operations
The ground-truth plane: what actually turned out to be fraud, who said so, and when they could first have said it. · 7 operations
The lookup data a risk decision needs but cannot derive: which email domains hand out throwaway inboxes, which addresses belong to a datacentre or a Tor exit, which card scheme an issuer prefix belongs to, which browsers the fleet sees everywhere, and how current the designation lists the screening engine holds actually are. · 5 operations
One-click validator onboarding: prove your Genesis NFT, get a node provisioned, queue its registration. · 4 operations
Blockchain key custody: create wallets, rotate their keys, and sign with them. · 8 operations
Your org's shared space: documents edited together, files, seats, and agents as teammates. · 45 operations
Intelligence
models · agents · evaluation — the mind of the cloud — 18 capabilities.
Hanzo AI — the model API on /v1 (/v1/chat/completions, /v1/messages, /v1/models and the rest of hanzoai/ai's surface) — mounted into a cloud binary with the money, ingest and telemetry callbacks cloud BUILDS but cannot INSTALL. · 311 operations
co-resident on ai's router — it claims zen-SKU requests and passes the rest on
Hanzo Engine: which models the serving runtime has loaded, and the GPUs under it. · 4 operations
Model serving: deploy a model behind an endpoint and call it. · 7 operations
The cloud's one training endpoint, /v1/train (HIP-1333): clients the caller drives on the engine, and jobs the org's linked machines or Hanzo's executor run, whose adaptation, protection, objective and output are fields and whose artifacts, bases and evaluations are what they produce. · 24 operations
Autonomous agents for your org: define them, run them, keep every run. · 57 operations
What a codebase is before its agent starts: the commands that install it, the command that starts it, and the secrets it reads. · 6 operations
/.well-known/agent-skills/ — the Agent Skills discovery convention, GET-only
Scoring a model on your own data, with a judge you choose. · 16 operations
One honest score for any model, on the tests everyone quotes. · 9 operations
Your prompt library, versioned, so nothing changes silently. · 6 operations
The code interpreter: run a snippet in a sandbox, and move files in and out of the session that sandbox IS. · 3 operations
The ONE compute primitive: a sandbox is a gVisor pod that runs somebody else's code, and every lifetime is the same object. · 23 operations
Everything your org can call, in one list: connector actions, functions, agents, skills and your own MCP servers. · 19 operations
A plain-language question about your business, answered with real numbers. · 2 operations
Search and symbols across your repos, for you and your agents. · 7 operations
Live semantic code intelligence — definitions, references, types, hover, outline and diagnostics — over a repository AND its resolved dependencies, with no toolchain on the caller's machine. · 5 operations
Text in, the same text out in the language you asked for. · 3 operations
Data
the stores every capability writes to and reads from — 14 capabilities.
Managed Hanzo Base: a hosted backend for your app — collections, records, access rules and sign-in. · 3 operations
One-click data add-ons: a SQL, key-value, document, vector, search or object store, wired straight into your app. · 28 operations
Object storage: your buckets and the files in them, with signed URLs for upload and download. · 11 operations
Where work lives: drives, folders and the files in them. · 7 operations
Your key-value store: buckets of versioned values your apps read and write by key. · 6 operations
One organization's entities and the relations between them, held as assertions: somebody, at some moment, from some evidence, asserted that this thing stands in that relation to that other thing. · 15 operations
One ranked result set over everything your org has stored. · 1 operations
Fast full-text search over your own data, typos forgiven. · 17 operations
Your team's wiki and your agents' memory, searchable by meaning. · 19 operations
One place to browse every project, app and site built here. · 1 operations
The product catalogue's shape: which categories exist, what each product is called, which category it sits in, what it is tagged with, and the order the two are shown in. · 5 operations
Data sync: link two endpoints and keep them in step, on a webhook, on a schedule, or on demand. · 6 operations
Any web page turned into clean markdown a model can read. · 1 operations
A web search and a page fetch your agents can call. · 7 operations
Streams
messaging · durable tasks · async orchestration — 13 capabilities.
Hanzo Workflow: durable workflows that survive a crash, with every run visible and replayable. · 5 operations
Your message bus: publish, subscribe, and durable streams your apps read at their own pace. · 2 operations
:9092 — the Kafka binary protocol, translated onto the same JetStream node
:5672 — AMQP 0-9-1, translated onto the same JetStream node
Queue and stream admin for your org: create them, watch them drain, ack what you pulled. · 15 operations
Transactional email and SMS, sent through your org's own provider credential. · 6 operations
The telecommunications surface: phone numbers, calls and messages, on whatever carrier the deployment is configured for. · 10 operations
Workflows that run themselves, on a schedule or a webhook. · 26 operations
Hanzo Flow: build an agent workflow on a visual canvas, run it, and read every run. · 8 operations
How your app hears about events: register an endpoint, pick the events, get each one delivered and signed. · 8 operations
One inbox for the chat apps you connect — Discord, Slack, Teams, Telegram. · 9 operations
Your events forwarded to the ad and analytics tools you use. · 5 operations
How your org connects third-party accounts like Slack, and revokes them. · 71 operations
Observability
see everything — telemetry · analytics · usage — 6 capabilities.
Your logs, metrics and traces: ship them in, query them, chart them. · 341 operations
· 11 operations
Product analytics: send an event, read back who did what. · 13 operations
What your org ran and what it cost, broken down per account. · 5 operations
The ranking of who uses AI most, in your org and globally. · 5 operations
The served contract: the OpenAPI document every client, tool list and command group is generated from, its command projection, the agent endpoint that offers the same operations over MCP, and the index a client follows from the API root to reach any of it. · 5 operations
Economy
the economy — meter · price · bill · reward — 20 capabilities.
Selling: checkout, subscriptions, invoices, spend alerts, payment webhooks and the storefront catalog. · 164 operations
Your org's balance, what it has spent, and the cards it pays with. · 49 operations
The reserve fund behind every payout: real capital, held and accounted for. · 2 operations
The plan catalog: every tier you can buy, what it costs, and what it grants. · 14 operations
The price list: what every model, provider, GPU tier, tool and hosting plan costs. · 28 operations
How much a plan lets you do without paying, and how much of it you have left today. · 1 operations
The one market between orgs: agents and personas to hire, apps, skills, MCP servers and tools to buy, each sold by the org that owns it, and the two-sided work one org buys from another. · 23 operations
Double-entry accounting: chart of accounts, ledger, bank reconciliation, and the reports that prove the books balance. · 23 operations
Your cap table: stakeholders, share classes, grants, SAFEs, rounds, and who owns what. · 31 operations
Referral ATTRIBUTION: who referred whom, and whether that referee ever became a real customer. · 2 operations
A partner program that pays commission on what your referrals spend. · 10 operations
A royalty for open-source work: your repo runs, you get paid. · 5 operations
What an org has bought and may run: signed licenses to issue, verify and revoke, and the releases they unlock. · 9 operations
Pay-per-request over HTTP 402: quote a price, take the payment, serve the resource. · 2 operations
Lifecycle email: drip sequences that reach the right people. · 35 operations
One go-to-market push across paid, organic and email at once. · 11 operations
Your paid ad campaigns, launched and paused from one place. · 7 operations
A/B testing anything: a flag, an ad, a subject line, a model. · 7 operations
Serves an org as an economic principal: who it is, what it may pay, and which agents answer to it. · 7 operations
How companies formed on Hanzo exchange W-9s, W-8s and 1099s with each other, from the payments that moved between them on Hanzo's rails. · 28 operations
Fabric
the cloud fabric — deploy · provision · route · host — 16 capabilities.
Hanzo PaaS: deploy containers to your own tenant namespace — builds, releases, environments, logs, custom domains. · 39 operations
Hanzo CD: see what each app is running, sync it, and roll back a bad release. · 14 operations
Where your sites live: create one, deploy a build, roll back to any release. · 57 operations
Your container and package registry: push images, pull them back, see what you store. · 6 operations
Live control of the policy your API applies to every incoming request: CORS, rate limits, cache TTL and allowed methods, changed without a redeploy. · 3 operations
Your edge: automatic TLS certificates and hostname routing to any backend, changed live. · 18 operations
Hanzo Domains: search a name, see the price, buy it from your prepaid wallet. · 7 operations
Your DNS records: the zones and records behind every name you point at Hanzo. · 12 operations
Your Cloudflare account, managed from Hanzo: zones, Pages, Workers, Workers AI, R2, KV and D1. · 32 operations
The compute you rent from Hanzo: machines, GPUs and clusters — launch one, resize it, tear it down. · 30 operations
Mounts the CI fleet dashboard as a capability of this binary. · 2 operations
Your machines: the ones you own, connected and ready to take a command. · 4 operations
Mounts the Hanzo Cloud NETWORKING surface: the tenant's Hanzo Zero Trust footprint — the overlay network, its routers and its services — served as clean, org-scoped REST off the unified cloud binary and fronting the Hanzo Zero Trust controller (hanzoai/zt, an ZT-based fabric). · 9 operations
Feature flags: ship it dark, then turn it on for who you pick. · 8 operations
/v1/admin — the operator surface, SuperAdmin-only and not in the public contract
/v1/admin/plugins — the operator's view of which capabilities are enabled
Applications
the user-facing surfaces built on all of the above — 25 capabilities.
Git hosting for your org: create repos, clone, push, and see what they cost. · 52 operations
A gallery of starter kits you can deploy as they come. · 5 operations
What a template costs to run, worked out before you deploy. · 3 operations
A bot doing your work on a real desktop, live, while you watch. · 4 operations
A live news feed filtered to what your project cares about. · 6 operations
Hanzo Task: boards, the work items on them, and the filters that make a board. · 14 operations
Stands watch over an estate: sites, units, tours, keys, cameras, and the incidents that interrupt them. · 29 operations
Document types you define: describe a record once, then create, list, submit and cancel documents against it. · 16 operations
Marketing content from draft to published, on every channel. · 6 operations
The AI that builds an agentic company with you, one measured step at a time. · 15 operations
A support desk: customers file tickets, your team answers them. · 4 operations
The virtual office: it decides who may join a room and mints the short-lived token that lets them in. · 7 operations
A public URL for a service on your own machine, and a list of what you have open. · 2 operations
Posting to every social account you own, now or on a schedule. · 13 operations
The unified AI login manager's registry: the org+user-scoped record of WHICH provider accounts (Claude Max, ChatGPT Plus, a Hanzo API key, a raw provider key) a developer has signed into, ON WHICH MACHINES, with each account's latest usage snapshot. · 11 operations
A document out for signature, signed and filed with an audit trail. · 13 operations
A secure document room you share by link and watch page by page. · 26 operations
Incorporation end to end: pick a structure, add founders, pay, file, and e-sign. · 23 operations
Prices and tracks what it costs to KEEP a company, as distinct from what it cost to form one. · 1 operations
The paperwork your company needs, drafted, signed and filed. · 11 operations
Your own settings — theme, density, pinned nav — following you across every Hanzo app. · 2 operations
How an org configures each product it uses, secret fields included. · 2 operations
Your serverless code: publish it, call it over HTTP, watch every run and what it cost. · 11 operations
What is inside a container image: every component, resolvable by digest or image ref. · 1 operations
Search visibility as data: what a phrase is worth, what a site already places for, who places beside it, who links to it, and what one page gets wrong. · 7 operations
Chain
the networks the cloud speaks to — enumerate · call · read balances — 3 capabilities.
The chain-access surface: which chains this deployment can reach, a JSON-RPC endpoint onto each, and the two token reads every wallet UI needs. · 4 operations
Chain data: your block indexers and how far each has caught up, plus the on-chain price feeds. · 2 operations
What trades on each chain, and how far the read of it got. · 5 operations
Prefer to click? The interactive reference renders the same document.