Hanzo

Chains

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
Operations2
AuthAuthorization: Bearer $HANZO_API_KEY

Quickstart

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

Then the first call — a read that needs nothing but the key. GET /v1/chains, operation get_chains:

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.

chains

GET /v1/chains/{chain}

Reports one chain and whether its upstream is answering. An unreachable chain is still a 200 with live:false — the chain is configured, which is a different fact from the chain being up, and a 502 here would make a console page error rather than show the outage.

ParameterInTypeRequiredDescription
chainpathstringyesChain is the registry id, as in /v1/chains/lux.

GET /v1/chains

Reports the chains this deployment can reach. The list is the declared registry, so it is exactly what /v1/rpc will accept — a chain that appears here is one this deployment actually has an upstream for.


All Hanzo APIs · Interactive reference

How is this guide?

On this page