Pricing

pricing: 28 operations.

Also for this capability: API · CLI · MCP · SDKs

pricing: 28 operations. Name one in "op" and pass that operation's own arguments in "input". describe returns an operation's input schema.

Tool	`pricing`
Address	`https://api.hanzo.ai/v1/mcp`
Method	`tools/call` (JSON-RPC 2.0)
Arguments	2, 1 required
Operation	`GET /v1/pricing/base` · `GET /v1/pricing/blockchain` · `GET /v1/pricing/cloud` · `GET /v1/pricing/cloud/storage` · `GET /v1/pricing/compute` · `GET /v1/pricing/datastore` · `GET /v1/pricing/enablement` · `GET /v1/pricing/featured` · `GET /v1/pricing/free` · `GET /v1/pricing/gpu` · `GET /v1/pricing/health` · `GET /v1/pricing/iam` · `GET /v1/pricing/policy` · `GET /v1/pricing/summary` · `GET /v1/pricing/tariff`
Product	pricing

Arguments

Field	Type	Required	Default	Values	Description
`input`	`object`	—	—	—	arguments for the chosen op
`op`	`string`	yes	—	—	—

tools/list declares a type, a description, which fields are required and an enumerated value set for each field and nothing further, and every column above is MCP's own. This tool takes an operation name and that operation's arguments, so what the document constrains is what goes inside input, field by field, on the operation you name — ask describe for that. A — means MCP does not constrain the field.

Call it

A tools/call carries every argument in one flat object — nothing binds to a path or a query string. This call carries exactly the arguments the operation requires, so it is the smallest one that can run.

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "pricing",
         "arguments": {
           "op": "list_pricings"
         }
       }
     }'

Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. tools/list needs no credential; tools/call does — called without one MCP answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →

The operation behind it

pricing dispatches to 28 operations. 15 of them MCP names exactly as the document ids them, and those are below; for the rest MCP has its own verb, which describe resolves.

Operation	Route	Product	Summary
`get_pricing_base`	`GET /v1/pricing/base`	pricing	Returns the Hanzo Base plans — the managed-instance tiers, each with its monthly and annual price, storage and request allowances and feature list.
`get_pricing_blockchain`	`GET /v1/pricing/blockchain`	pricing	Returns the blockchain access plans — the RPC and node tiers, each with its monthly price, compute-unit allowance and feature list.
`get_pricing_cloud`	`GET /v1/pricing/cloud`	pricing	Returns the public cloud section of the catalog in one document: its instance plans, its regions and its block-storage prices.
`get_pricing_cloud_storage`	`GET /v1/pricing/cloud/storage`	pricing	Returns the block-storage prices of the cloud section: the per-GB monthly rate and the volume size bounds a caller may ask for.
`get_pricing_compute`	`GET /v1/pricing/compute`	pricing	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.
`get_pricing_datastore`	`GET /v1/pricing/datastore`	pricing	Returns the Hanzo Datastore rate card: the tier list, the per-GB storage and egress usage rates, the annual discount and the trial.
`get_pricing_enablement`	`GET /v1/pricing/enablement`	pricing	Returns what the caller's org can actually use: every managed item with its global state, whether it is effective here, whether this org is already opted into its beta, and whether it may still opt in.
`get_pricing_featured`	`GET /v1/pricing/featured`	pricing	Returns the models the catalog highlights, filtered to what the caller's org may see.
`get_pricing_free`	`GET /v1/pricing/free`	pricing	Returns the models that cost nothing to call, filtered to what the caller's org may see.
`get_pricing_gpu`	`GET /v1/pricing/gpu`	pricing	Returns the rentable GPU configurations, each with its accelerator count and model, VRAM, vCPU, host memory and hourly price.
`get_pricing_health`	`GET /v1/pricing/health`	pricing	Reports that the pricing subsystem is mounted and serving.
`get_pricing_iam`	`GET /v1/pricing/iam`	pricing	Returns the identity plans — the Hanzo IAM tiers, each with its monthly and annual price, monthly-active-user allowance and feature list.
`get_pricing_policy`	`GET /v1/pricing/policy`	pricing	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_pricing_summary`	`GET /v1/pricing/summary`	pricing	Returns the catalog's headline statistics — model counts by family and the provider directory.
`get_pricing_tariff`	`GET /v1/pricing/tariff`	pricing	Returns the platform's rate card: what a bill is made of, what each part costs, and the completion windows a request may ask for.

The same capability over plain HTTP is in the pricing API reference, on https://api.hanzo.ai.

All 120 tools · MCP · API reference

Generated from tools/list on https://api.hanzo.ai/v1/mcp — 120 tools captured 2026-09-30.

Was this page useful?

PreviousPlatform NextPrincipal