Hanzo

Rpc

Package web3 is the chain-access surface: which chains this deployment can reach, a JSON-RPC door onto each, and the two token reads every wallet UI needs.

Package web3 is the chain-access surface: which chains this deployment can reach, a JSON-RPC door onto each, and the two token reads every wallet UI needs.

Base URLhttps://api.hanzo.ai
Operations1
AuthAuthorization: Bearer $HANZO_API_KEY

Quickstart

export HANZO_API_KEY=hk-...   # console.hanzo.ai → API keys

Then the first call. This one takes arguments — the placeholders are yours to fill. POST /v1/rpc/{chain}, operation post_rpc_by_chain:

hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.

Answers 200 with object — ok.

rpc

POST /v1/rpc/{chain}

Forwards a JSON-RPC call to the named chain and returns its answer unchanged. Only declared chains are reachable, and only to a caller with a validated principal — this is the deployment's upstream, not an open relay.

ParameterInTypeRequiredDescription
chainpathstringyesChain is the registry id, from the URL.

Request bodyapplication/json (required)

FieldTypeRequiredDescription
chainstringChain is the registry id, from the URL.
idID is echoed back untouched.
jsonrpcstringJSONRPC must be "2.0" when present.
methodstringMethod is the RPC method, e.g.
paramsParams is the method's parameters, passed through unread.

All Hanzo APIs · Interactive reference

How is this guide?

On this page