BTC address balance API with exact balances and UTXOs

Yes. The balance API accepts batched addresses and returns the exact balance, received, sent and UTXOs for each, which is ideal for wallets and reconciling cold storage across large address sets.

Confirmed balances come from the reconciled chain, and pending activity is visible through the mempool. Everything is computed from the fully-indexed chain, so no node is needed. It is data only, not financial advice.

Yes. Add a block height or a timestamp to the request and the balance comes back as of that point, computed from the outputs the address had received and spent by then. Ordinary explorer APIs cannot do this because they hold only the current unspent set, which is why year-end and audit figures usually have to be reconstructed by hand.

An explicit zero rather than an error or a missing row. That distinction matters when you are reconciling a list, because a row that silently disappears looks the same as a row you forgot to submit, and only one of those is a real problem.

Request the address and read the confirmed balance in satoshis. Under the hood a balance is not stored anywhere on the chain, it is the sum of the unspent outputs pointing at that address, so the endpoint has to hold an indexed UTXO set to answer at all. We verified ours against two independent explorers on 17 September 2026 and the totals matched to the satoshi on every address.

Almost always because one figure includes unconfirmed mempool activity and the other does not, or because one rounds. Decide explicitly which you want: a confirmed-only balance is stable and reproducible, while a balance including pending transactions can move in either direction and can be reversed by a replacement. Reconciliations should use confirmed balances pinned to a block height.

This one returns integers in satoshis, which is the only representation that survives accounting. Several commercial balance feeds return two decimal places of BTC, which throws away up to 999,999 satoshis per address and makes a tie-out to the chain impossible. If a vendor cannot express 224,683.07908858 BTC exactly, it cannot be the source of record for a reserve report.

Single-address lookups against public endpoints came back in roughly 0.2 to 0.6 seconds when we timed them on 17 September 2026, and the speed difference stops mattering once you need more than a handful. Five addresses checked sequentially against Esplora took 3.035 seconds because it has no batch endpoint at all. Volume, not single-call latency, is what decides which API you need.

Yes, and you usually need them. The balance tells you how much an address holds, while the UTXO list tells you what shape it is in: how many outputs, what sizes, and therefore what a spend will cost in fees. Wallets use it for coin selection and treasury teams use it to spot fragmentation before a consolidation.