# Obol EVM Address Snapshot

> Obol EVM Address Snapshot is a paid API for AI agents from obol.danieldutoit.net, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-13).

Returns a verified on-chain snapshot of an EVM wallet address's state (balances, tokens, activity) for a given chain, paid per-call via x402 in USDC.

## Facts

- Endpoint: GET https://obol.danieldutoit.net/v1/evm/address-snapshot
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/obol-evm-address-snapshot-9c3c176e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_bvuG1yl5_yZ2HG7LFOMxO

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability obol-evm-address-snapshot-9c3c176e
```

Example prompt: Pull a verified on-chain snapshot for wallet address 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 on Ethereum (chain ID 1) and tell me what tokens and balances it currently holds.

## When to prefer this

Choose this endpoint when you need verified, point-in-time on-chain data for a specific EVM wallet or contract address and are comfortable with a per-call micropayment model via x402/USDC. It is well-suited for agents that need trustworthy blockchain state without running their own node, and for use cases where auditability of the data source matters. Prefer alternatives if you need historical time-series data, event logs, or bulk multi-address lookups.

## Known failure modes

- Invalid or malformed Ethereum address returns an error
- Unsupported or unrecognized chain_id returns an error or empty result
- Network or RPC unavailability for the requested chain causes a timeout or failure
- Payment failure via x402 protocol prevents data delivery
- Address with no on-chain history may return minimal or empty data

## How this service works

Obol sells verified blockchain data over x402, settled in USDC on Base.

## Output

A verified snapshot object containing the on-chain state of the specified EVM address on the requested chain — typically including native token balance, ERC-20 token holdings, and related account metadata, returned as a JSON object settled after a $0.001 USDC x402 micropayment.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "chain": {
   "id": 10,
   "name": "OP Mainnet"
  },
  "native": {
   "symbol": "ETH",
   "balance": "0.000000000000000000",
   "decimals": 18,
   "balance_units": "0"
  },
  "address": "0x4094383033C1861E2686eaC4d4BBae6F0031F5d2",
  "network": "eip155:10",
  "observed_at": "2026-09-07T11:04:21.000Z",
  "observed_block": 156590142,
  "provider_consistency": {
   "agreement": true,
   "providers": [
    "mainnet.optimism.io",
    "optimism-rpc.publicnode.com"
   ],
   "provider_count": 2
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/obol-evm-address-snapshot-9c3c176e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from obol.danieldutoit.net](https://www.zero.xyz/host/obol.danieldutoit.net/llms.txt)