zeekayandHanzo Dev 1bce7184d9 The catalog reads its origin from api.hanzo.ai
cloud computes the model and pricing catalog in Go, and every path this
worker mirrors answers there, so the edge caches the origin directly
instead of a second hop.

Cloud and GPU pricing lose their rewrite: both are namespaced under
/v1/pricing at the origin, the same as every other sub-resource, so the
public path and the origin path are now the same string.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-16 23:50:51 -07:00

Hanzo Public Catalog

Cloudflare edge-cached, daily-refreshed public read-only catalog for Hanzo. Serves the model + pricing catalog to public consumers (marketing site, pre-login model browsing, docs) without a token, so api.hanzo.ai can stay fully authenticated.

Live: https://catalog.hanzo.ai

curl https://catalog.hanzo.ai/v1/models    # OpenAI-compatible model catalog
curl https://catalog.hanzo.ai/v1/pricing   # full pricing catalog
curl https://catalog.hanzo.ai/v1/plans     # subscription / cloud plans
curl https://catalog.hanzo.ai/             # self-describing index

This is the only host it serves. api.hanzo.ai is the authenticated API and the cloud origin owns every path on it — including /v1/models and /v1/pricing/*, which this worker used to intercept at the ingress. See LLM.md for what that cost.

See LLM.md for architecture, the resource registry, routing, and how to add a new cached resource.

S
Description
Edge-cached public catalog serving Hanzo's model, pricing, and plan data without authentication.
Readme
101 KiB
Languages
JavaScript 100%