Hanzo

Tokens

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. GET /v1/tokens/{chain}/{address}, operation get_tokens_by_chain_by_address:

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.

tokens

GET /v1/tokens/{chain}/{address}

Reads an address's native balance on a chain.

ERC-20 positions are NOT enumerated here: eth_getBalance answers the native one, but "every token this address holds" is an indexer question — there is no RPC call that answers it, and walking a token list would return a number that silently omits whatever the list missed. explorer owns the indexer relationship; this returns the balance the chain itself can prove.

ParameterInTypeRequiredDescription
chainpathstringyesChain is the registry id.
addresspathstringyesAddress is the account, 0x-prefixed.

All Hanzo APIs · Interactive reference

How is this guide?

On this page