Zen
Zen — reached at co-resident on ai's router; not in the public REST contract.
Zen ships in every Hanzo cloud. It carries no operations in the public API document, so it has no generated REST reference — it is reached another way.
| Reached at | co-resident on ai's router — it claims zen-SKU requests and passes the rest on |
| In the public contract | no — see below |
Why there is no reference here
This reference is generated from the public API document, one page per operation. This capability contributes no operation to that document — which is a fact about its door, not about whether it is finished. It is GA and it runs in every deployment. It is reached at co-resident on ai's router — it claims zen-SKU requests and passes the rest on.
Specification
Specification pending — no HIP in hanzoai/hips declares capability: zen yet. What this capability serves is below, from the API document; what it is — the store it owns, how it meters, what it publishes — is written as a HIP under HIP-0139.
How is this guide?
AI
Package ai is 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…
Engine
Package engine is Hanzo Engine: which models the serving runtime has loaded, and the GPUs under it.