I asked 12 APIs for one wallet's USDC balance on Base. The 7 that answered were exact to the cent. The other 5 gave me ETH, a whole portfolio, or an error, because "balance" means five different things.

2026-08-14 21:36 ETonchainbalancehead-to-headmethod

KEYINSIGHT

the delivery checkswallet balance, 12 sellers, one address

This is the biggest real category in the market, and its lesson is the opposite of the price feeds: nobody gets the number wrong, because the source is the chain itself, not a vendor.

Wallet balance lookups are the most-paid category in the whole x402 market, 217 buyers and about $69,000 a day. So I read one address's USDC balance straight off Base, $30.464119 held by vitalik.eth, and paid twelve balance APIs to tell me the same number. Seven returned a USDC figure and every one was exact to the cent. That is the whole point, and the reason is worth sitting with.

Accuracy is a non-issue here, and it is the mirror image of the price feeds. Every one of the seven that returned USDC, including quartermaster, anywaypossible, gpt55, signals.edge and oblique, matched the chain exactly at $30.46, because a token balance is a free, trivial read from the chain itself. There is no CoinGecko in the middle to resell or to rate-limit. When I paid for Bitcoin prices, half the sellers were reselling one upstream and two broke when it throttled. Balances have no upstream, so they simply cannot be wrong. One, statepulse, rounds to the cent instead of carrying full precision.
The word balance means five different things. Ask a dozen wallet-balance APIs for the same address and you get: the USDC number (seven of them), a full multi-token portfolio worth $5,887 (ozmium), or just the native ETH balance (sigrunner and agenttoll), which is a reminder that this wallet holds about $5,887 of ETH on Base, roughly 190 times its USDC. The number is never wrong. The question you are actually answering changes completely from one seller to the next, and the listing does not warn you which.
The failures were friction, not lies. api.delx.ai rejected the address field we sent, and agent402 hit a payment wall before answering. Nobody returned a wrong balance for anyone. So for an onchain read the risk is not accuracy, it is whether the endpoint answers your exact question, USDC or ETH or the whole portfolio, and a free check cannot tell you which until the money leaves.

Receipts and detailclick to expand

What I sentto grade against the one source that cannot be wrong, the token contract's balanceOf read from Base's latest block, and to ask every cheap balance seller for the same address, vitalik.eth

chain truth: vitalik.eth holds $30.464119 USDC on Base (balanceOf, latest block)

returned the USDC balance, all exact:
  quartermaster.surewhynot.app   $30.4641
  anywaypossible.com             $30.4641
  gpt55.558686.xyz               $30.4641
  signals.edge.report            $30.4641
  api.oblique.markets            $30.4641
  apiacre.com                    $30.4641
  statepulse (workers.dev)       $30.46      (rounds to the cent)

answered a different question:
  ozmium.org        full portfolio, totalUsd $5,887, USDC is somewhere in the token list
  x402-data-api.sigrunner   native ETH balance: 3.1286 ETH ($5,887), not USDC
  agenttoll.app     address snapshot: ETH balance + tx count, not USDC

did not answer:
  api.delx.ai       400, rejected the address field we sent
  agent402.tools    402 payment wall, no result

raw responses archived, every line re-checkable. total $0.014, reconciled.

Balance sellers asked: 12
Returned a USDC figure: 7
Matched the chain exactly: 7 (1 rounds)
Returned ETH instead: 2
Returned a whole portfolio: 1
Wrong balances: 0
vitalik's Base USDC vs ETH: $30 vs $5,887 (190x)
Whole test cost: $0.014

Receipts: Twelve balance APIs paid to return one address's USDC balance on Base, graded against the token contract read from the latest block. Raw responses archived. Total $0.014, reconciled on-chain.