Pricing
pricing: 33 operations.
Also for this capability: API · CLI · MCP · SDKs
pricing: 33 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 · 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/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 |
| 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": "get_admin_catalog"
}
}
}'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 33 operations. 14 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 | GET /v1/pricing | pricing | Returns the whole pricing catalog in one document: Zen and third-party models, providers,… |
get_pricing_base | GET /v1/pricing/base | pricing | Returns the Hanzo Base plans — the managed-instance tiers, each with its monthly and… |
get_pricing_blockchain | GET /v1/pricing/blockchain | pricing | Returns the blockchain access plans — the RPC and node tiers, each with its monthly… |
get_pricing_cloud | GET /v1/pricing/cloud | pricing | Returns the public cloud section of the catalog in one document: its instance plans, its… |
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… |
get_pricing_compute | GET /v1/pricing/compute | pricing | Returns the compute section of the catalog: the cloud provider and region the prices are… |
get_pricing_datastore | GET /v1/pricing/datastore | pricing | Returns the Hanzo Datastore rate card: the tier list, the per-GB storage and egress usage… |
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 | ListGPUTiers returns the rentable GPU configurations, each with its accelerator count and… |
get_pricing_health | GET /v1/pricing/health | pricing | Health reports that the pricing subsystem is mounted and serving. |
get_pricing_iam | GET /v1/pricing/iam | pricing | ListIAMPlans returns the identity plans — the Hanzo IAM tiers, each with its monthly and… |
get_pricing_policy | GET /v1/pricing/policy | pricing | Returns the pricing policy document: the revenue-sharing terms (the idle-resale share and… |
get_pricing_summary | GET /v1/pricing/summary | pricing | Returns the catalog's headline statistics — model counts by family and the provider… |
The same capability over plain HTTP is in the pricing API reference, on https://api.hanzo.ai.
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 121 tools captured 2026-08-16.
How is this guide?