# Zen

URL: https://docs.hanzo.ai/docs/openapi/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.

> [All capabilities →](https://docs.hanzo.ai/docs/openapi) · [How the four surfaces line up →](https://docs.hanzo.ai/docs/guides)

|                            |                                                                                |
| -------------------------- | ------------------------------------------------------------------------------ |
| **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 address, 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](https://github.com/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.

---

[All Hanzo capabilities](https://docs.hanzo.ai/docs/openapi) · [Interactive reference](https://docs.hanzo.ai/docs/openapi/reference)