Skip to main content
Balance reads are read-only and accept any address. They need no authenticated wallet, no credential, and none of the durable storage that stateful operations require.

Read balances

IndexerClient takes the same publishable key and origin-setting fetch as the wallet transport. It is independent of ServerWallet, so you can construct it on its own.

Result shape

balance is a string in the asset’s base units. Convert it with the asset’s decimals for display. decimals and balanceUSD are optional and absent when the indexer does not know them. Do not default an unknown decimals to 18: an unknown precision makes the balance undisplayable, and guessing it misreports the amount by orders of magnitude. fetchedAt records when the result was read, which matters because balances move independently of your read.

Errors are not zero balances

errors reports the chains that failed, while items holds the results that succeeded. A chain in errors has an unknown balance, not a zero balance.
Treating a failed chain as zero understates holdings, so keep the two apart in anything that sums balances or decides whether funds exist.

Paginate

nextPage is absent on the final page. A result with a nextPage is incomplete, so follow it before reporting a total.

Supported networks

CHAINS lists the networks this SDK build accepts, each with its id, name, native symbol, and block explorer. Read it rather than hardcoding a list, and expect a chainId outside it to raise UNSUPPORTED_CHAIN. For the networks available to OMS wallets generally, see Supported networks.