Registry
Package registry is your container and package registry: push images, pull them back, see what you store.
Package registry is your container and package registry: push images, pull them back, see what you store.
| Base URL | https://api.hanzo.ai |
| Operations | 6 |
| Auth | Authorization: Bearer $HANZO_API_KEY |
registry
GET /v1/registry/images
Images lists the org's container repositories, read live from the OCI catalog and filtered server-side to the org's namespace — the page can only ever hold the caller's own images.
GET /v1/registry/packages
Packages lists the org's npm packages — <org> and @<org>/… — from the
npm registry's search index, optionally narrowed by a query within that
scope. The org boundary is applied server-side after the search, so a query
can never widen it.
| Parameter | In | Type | Required | Description |
|---|---|---|---|---|
query | query | string | — | Query narrows the listing within the org's scope when present; the org boundary itself is never widened by it. |
GET /v1/registry/projects
Projects lists the namespaces the caller can see with what each holds: the org's slug, its repository count on the OCI catalog, and its package count on the npm registry. Today that is exactly one row — the caller's org.
GET /v1/registry/status
Status reports whether the OCI and npm registries are reachable and, when the OCI half is auth-gated, which token realm its challenge advertises — an honest lens for "is the registry plane up", never a fabricated ok.
GET /v1/registry/tags
Tags lists one org-owned repository's tags, read live from the OCI registry. The repository is addressed inside the org's namespace — a name outside it cannot be expressed, and an unknown one answers 404.
| Parameter | In | Type | Required | Description |
|---|---|---|---|---|
image | query | string | — | Image is the repository name inside the org's namespace, as returned by the images op. |
POST /v1/registry/token
Token mints a short-lived, pull-only registry token for exactly one of the
org's images, through the same IAM realm the docker CLI authenticates
against. The scope is pinned server-side to <org>/<image> with the pull
action — no field exists to name another org's image or ask for push. Use it
as Authorization: Bearer … on the OCI wire; it expires in minutes.
Request body — application/json (required)
| Field | Type | Required | Description |
|---|---|---|---|
image | string | — | Image is the repository name inside the org's namespace (e.g. |
How is this guide?