Pricing

Package pricing is the price list: what every model, provider, GPU tier, tool and hosting plan costs.

Guide & examples → · All API references → · Six flows, four surfaces →


Base URL	`https://api.hanzo.ai`
Operations	25
Auth	`Authorization: Bearer $HANZO_API_KEY`

`GET /v1/pricing/base`

Returns the Hanzo Base plans — the managed-instance tiers, each with its monthly and annual price, storage and request allowances and feature list.

`GET /v1/pricing/blockchain`

Returns the blockchain access plans — the RPC and node tiers, each with its monthly price, compute-unit allowance and feature list.

`GET /v1/pricing/cloud/plans`

Returns just the cloud instance plans — each with its vCPU, memory, disk, CPU type, VM allowance, feature list and monthly and hourly price. It is the plans of the cloud section on their own.

`GET /v1/pricing/cloud/regions`

Returns the regions a cloud instance can be placed in, each with its id, display name and physical location. It is the regions of the cloud section on their own.

`GET /v1/pricing/cloud/storage`

Returns the block-storage prices of the cloud section: the per-GB monthly rate and the volume size bounds a caller may ask for.

Returns the public cloud section of the catalog in one document: its instance plans, its regions and its block-storage prices. The section's internal half — the provider costs Hanzo pays and the plan-to- provider routing table — is stripped before it is served, so this is what a customer may see and nothing more.

`GET /v1/pricing/compute/presets`

Returns just the named compute sizes — the short, human-labelled list ("Starter", "Pro") a size picker renders, each carrying its provider slug, vCPU, memory, disk and price. It is the presets of the compute section on their own, for a caller that does not need the full tier table.

`GET /v1/pricing/compute`

Returns the compute section of the catalog: the cloud provider and region the prices are quoted for, the monthly markup applied to them, the full instance-size tier list and the named presets. It is the whole section as the pricing source records it, un-gated — no model or provider identity appears in it.

`GET /v1/pricing/datastore`

Returns the Hanzo Datastore rate card: the tier list, the per-GB storage and egress usage rates, the annual discount and the trial. It is the section as authored, un-gated — no provider identity appears in it.

The route was missing while the data existed, so this 404d and every visitor to hanzo.ai's Infrastructure tab was told pricing was "temporarily unavailable".

`GET /v1/pricing/featured`

Returns the models the catalog highlights, filtered to what the caller's org may see. It is the same catalog as ListModels narrowed to entries the pricing source marks featured.

`GET /v1/pricing/free`

Returns the models that cost nothing to call, filtered to what the caller's org may see. It is the same catalog as ListModels narrowed to entries the pricing source marks free.

`GET /v1/pricing/gpu`

ListGPUTiers returns the rentable GPU configurations, each with its accelerator count and model, VRAM, vCPU, host memory and hourly price.

`GET /v1/pricing/health`

Health reports that the pricing subsystem is mounted and serving. It answers from the process itself and consults neither the catalog bundle nor the enablement store, so it stays "ok" while either is degraded.

`GET /v1/pricing/iam`

ListIAMPlans returns the identity plans — the Hanzo IAM tiers, each with its monthly and annual price, monthly-active-user allowance and feature list.

`GET /v1/pricing/model/{name}`

Returns one model's catalog entry — its pricing, context window and capabilities as the pricing source records them. A model hidden for the caller's org answers the same 404 an unknown name does, so a disabled model gets no existence oracle.

Parameter	In	Type	Required	Description
`name`	path	string	yes	Name is the model's name or its slugged id ("zen4", "acme/some-model-1"), matched case-insensitively.

`GET /v1/pricing/models`

Returns the whole model catalog — Hanzo's own Zen models and every third-party model — filtered to what the caller's org may see. A model an admin has disabled is absent; one in beta appears only for an org granted it. A SuperAdmin sees every model, each annotated with its enablement state.

`GET /v1/pricing/paas`

ListPaaSPlans returns the application-hosting plans — the deploy-and-host tiers, each with its monthly and annual price, app and memory allowances and feature list.

`GET /v1/pricing/policy`

Returns the pricing policy document: the revenue-sharing terms (the idle-resale share and the open-source share, each with its percentage and who is eligible) and the commitments Hanzo makes about how it bills — no hidden fees, no egress charges, no surprise bills.

`GET /v1/pricing/providers`

Returns the model providers the catalog knows, each with its info object, filtered to what the caller's org may see. A provider an admin has disabled is absent — and so are its models everywhere else on this surface, because a provider's state cascades to what it serves.

`GET /v1/pricing/services`

Returns the managed-service rate cards — Search, Crawl, Vector, Console and Managed Services — each with its own tiers, and some with usage rates or a comparison table. It is the section as authored, un-gated.

These are DISPLAY rate cards: what a product costs, not what a plan grants. No entitlement or limit fields ride here, so nothing can bill off them.

`GET /v1/pricing/subscriptions`

Returns the API subscription plans — the account-level tiers a customer subscribes to, each with its monthly and annual price, included credit, rate limits and feature list.

`GET /v1/pricing/summary`

Returns the catalog's headline statistics — model counts by family and the provider directory. The provider sub-object is filtered to what the caller's org may see, so a disabled provider's name never leaks; the aggregate counts are the catalog's own, over everything it holds.

`POST /v1/pricing/sync`

Refreshes the third-party section of the catalog from its upstream listings and returns the time the refreshed catalog was stamped with. The fetch runs in Go and the markup transform in the pricing bundle. SuperAdmin only; every other caller is refused.

`GET /v1/pricing/tools`

Returns the per-use tool prices — web search, code interpreter, file storage, image generation, speech-to-text and text-to-speech — each with the unit it is billed by and its price in that unit.

`GET /v1/pricing`

Returns the whole pricing catalog in one document: Zen and third-party models, providers, model families, the free-model list, plan and infrastructure pricing. Every model and provider it names is filtered to what the caller's org may see — the same gate the leaf routes apply, so this can never be an un-gated second source for what they hide.

Pricing guide · All Hanzo APIs · Interactive reference