Wallet overview and transfers
● Livezato.org
Use when an agent needs a one-call overview of a wallet before acting - e.g. to check a counterparty wallet before paying it, due diligence or a portfolio check - on Ethereum (default) or Base (network=base): ETH balance, nonzero balances of top tokens (USDC, USDT, DAI, WETH ...), nonce, contract flag and recent ERC-20 transfers of those tokens. One GET replaces four lookups; the response also lists related endpoints.
- Price
- $0.003
- Asked in its payment challenge
- Chain
- Base
- Paid in
- USDC
- Live
- 1 of 1 check
Endpoint
$0.003 asked in its payment challenge on 20 Nov 2026
- addressquery, required0xd8da6bf26964af9d7eed9e03e53415d37aa96045Wallet or contract address to report on (0x + 40 hex chars)
- networkqueryethereumNetwork: "ethereum" (default, mainnet) or "base" (Base mainnet)
curl -i 'https://api.zato.org/api/chain/wallet-report?address=0xd8da6bf26964af9d7eed9e03e53415d37aa96045&network=ethereum'
Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/api.zato.org
Recent checks
- Median response
- 627 ms
- Last checked
- 20 Nov, 06:29 UTC
Our probes look for a payment challenge. They don't test payment or delivery.
All 1 checks
| When (UTC) | Result | HTTP | Response |
|---|---|---|---|
| 20 Nov, 06:29 UTC | Live | 402 | 627ms |
Questions
Did our last probe detect a payment challenge?
At our last probe on 20 Nov, 06:29 UTC, it returned HTTP 402 or another detected payment-challenge signal.
What payment terms does api.zato.org advertise?
The listing advertises x402, Base and USDC. It names cdp as its facilitator. Check the seller's current payment challenge and authentication requirements before paying.
Something wrong on this page? Tell us.