Plan

plan: 14 operations.

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

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

Tool	`plan`
Address	`https://api.hanzo.ai/v1/mcp`
Method	`tools/call` (JSON-RPC 2.0)
Arguments	2, 1 required
Operation	`GET /v1/plan/blockchain` · `GET /v1/plan/dns` · `GET /v1/plan/gpu` · `GET /v1/plan/health` · `GET /v1/plan/policy` · `GET /v1/plan/schema` · `GET /v1/plan/storage` · `GET /v1/plan/vocab`
Product	plan

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": "plan",
         "arguments": {
           "op": "list_plans"
         }
       }
     }'

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

plan dispatches to 14 operations. 8 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_plan_blockchain`	`GET /v1/plan/blockchain`	plan	Returns the blockchain RPC plan catalog: the tiers metered in monthly compute units, with their prices, limits and overage terms.
`get_plan_dns`	`GET /v1/plan/dns`	plan	Returns the DNS plan catalog: the tiers priced on zones, records per zone and queries per day.
`get_plan_gpu`	`GET /v1/plan/gpu`	plan	Returns the rentable GPU configurations, each with its accelerator count and model, VRAM, vCPUs, host memory and hourly price.
`get_plan_health`	`GET /v1/plan/health`	plan	Reports that the plans subsystem is mounted and serving.
`get_plan_policy`	`GET /v1/plan/policy`	plan	Returns the published pricing policy: whether pricing is transparent, the revenue-sharing terms (idle compute resale and the open-source share) and the principles the catalog is priced by.
`get_plan_schema`	`GET /v1/plan/schema`	plan	Returns the two JSON Schema documents this surface speaks: entitlements.schema.json, which declares every entitlement key with its type, unit and enum, and plan.schema.json, which a catalog plan record conforms to.
`get_plan_storage`	`GET /v1/plan/storage`	plan	Returns the block-storage price block: the price per GB per month and the volume size bounds a cloud plan may attach.
`get_plan_vocab`	`GET /v1/plan/vocab`	plan	Returns the entitlement key vocabulary: every key with its namespace, JSON type, nullability, unit, enum and title, the list of namespaces, and the engine features a license can grant.

The same capability over plain HTTP is in the plan 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?

PreviousPatrol NextPlatform