Hanzo
Cloud MCPunmapped

get_v1_commerce_topup_rails

TopupRails lists the accepted (chain, token, treasury) triples, so a browser can render "send USDC here" without the addresses being baked into its bundle.

TopupRails lists the accepted (chain, token, treasury) triples, so a browser can render "send USDC here" without the addresses being baked into its bundle.

This exists because the console previously gated its top-up UI on NEXT_PUBLIC_HANZO_HUSD_ADDRESS/_TREASURY — build-time constants. Enabling a rail therefore meant rebuilding and redeploying the frontend, and with them unset the UI reported "not available yet" no matter what the server could actually accept. Serving the set at runtime keeps ONE source of truth (the server's config) and lets a rail be switched on without shipping a bundle.

Everything here is public on-chain data; no secret is exposed, and the set is empty on a deployment that accepts no crypto rail.

Toolget_v1_commerce_topup_rails
Doorhttps://api.hanzo.ai/v1/mcp
Methodtools/call (JSON-RPC 2.0)
Arguments0
Operationnone in the OpenAPI document
Product

Arguments

This tool declares no arguments. Call it with an empty arguments object.

Call it

A tools/call carries its arguments in one flat object. This tool declares none, so the object is empty.

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": "get_v1_commerce_topup_rails",
         "arguments": {}
       }
     }'

tools/list needs no credential; tools/call does — called without one the door 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

The door exposes get_v1_commerce_topup_rails, but the copy of the OpenAPI document this build holds (pinned at 4e41f04ca) describes no operation for it — neither under that name nor at the route the name implies. That is either a route the document has yet to declare, or one the door has renamed since the pin. Everything on this page comes from tools/list; there is no REST reference to link to until the two agree.


All 755 tools · The door · API reference

Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).

How is this guide?

On this page