Reads an address's native balance on a chain.
Reads an address's native balance on a chain.
GET /v1/web3/tokens/{chain}/{address}
| Address | https://api.hanzo.ai/v1/web3/tokens/{chain}/{address} |
| Method | GET |
| Operation | get_web3_tokens_by_chain_by_address |
| Auth | Authorization: Bearer $HANZO_API_KEY |
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.
Request
2 fields.
| Field | In | Type | Required | Description |
|---|---|---|---|---|
chain | path | string | yes | Chain is the registry id. |
address | path | string | yes | Address is the account, 0x-prefixed. |
Response
| Status | Body | Meaning |
|---|---|---|
200 | balances | ok |
200 body — 3 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
address | body | string | — | Address is the account they belong to. |
chain | body | string | — | Chain is the chain the balances were read from. |
native | body | string | — | Native is the chain's own currency, as a 0x-quantity — the RPC's own encoding, not a float, because a wei value does not survive float64. |
Failure carries the platform error shape — see Errors.
Examples
hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.
import { Configuration, Web3Api } from 'hanzoai';
const api = new Web3Api(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getWeb3TokensByChainByAddress({ chain: 'chain', address: 'address' });from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import Web3Api
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = Web3Api(client).get_web3_tokens_by_chain_by_address(chain='chain', address='address')cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.Web3API.GetWeb3TokensByChainByAddress(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, web3_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = web3_api::get_web3_tokens_by_chain_by_address(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.Web3Api;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new Web3Api(client).getWeb3TokensByChainByAddress();The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →
curl https://api.hanzo.ai/v1/web3/tokens/<chain>/<address> \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches web3 through the web3 tool, which names its 3 operations with its own verbs — this one among them, under a name only the door declares. describe explains any of them:
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "describe",
"arguments": {
"op": "list_chains"
}
}
}'How is this guide?