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

..

registry.js

The catalog reads its origin from api.hanzo.ai

2026-09-16 23:50:51 -07:00

snapshot.js

the ladder is not an edge resource

2026-08-17 09:22:42 -07:00

worker.js

catalog: one host, one answer — the api.hanzo.ai mirror and its auth fork are gone

2026-08-01 10:59:16 -07:00