Blueprint

Package blueprint is what a template costs to run, worked out before you deploy.

blueprint

GET /v1/blueprint/health

Reports blueprint liveness and echoes the compute rate card in force.

The rate card is the one the estimator actually applies after the operator env overlay, so an operator can confirm a tuned knob took effect rather than inferring it from a price. Not JWT-gated — a liveness probe must be reachable — and it always answers 200 while the subsystem is mounted.

GET /v1/blueprint/sbom

A blueprint's bill of images and what running it costs

Answers a blueprint's SBOM — the container images its compose stack runs, each with the CPU/memory footprint that was applied to it — together with the compute cost that footprint prices out to on the active rate card.

ONE address, TWO shapes at 200: ?template=<id> returns that blueprint's Estimate alone (404 on an id no embedded blueprint carries), and no template returns {data:[Estimate]} for every blueprint — the batch the console's template gallery reads in one round-trip.

The blueprints are reference content embedded in the binary and validated at mount, so this read is the same for every caller and is scoped to no tenant. The per-hour figure it returns is the one the deploy path meters the deploying org on and the 20% author royalty is taken from; GET /v1/blueprint/health echoes the rate card it was priced from.

GET /v1/blueprint

Returns every deployable blueprint with its service count and estimated monthly compute cost.

It is the lightweight index the console renders as a template gallery before drilling into one stack's bill of images — GET /v1/blueprint/sbom?template=<id> is the detail view. The cost is the same figure the deploy path meters the deploying org on and the 20% author royalty is taken from, priced from the active rate card (GET /v1/blueprint/health echoes that card).

---

All Hanzo APIs · Interactive reference