# Obol Ethereum Address Cluster Lookup

> Obol Ethereum Address Cluster Lookup is a paid API for AI agents from obol.danieldutoit.net, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-21).

Returns heuristic cluster assignments for a given Ethereum address, grouping it with related addresses based on on-chain behavioral analysis.

## Facts

- Endpoint: GET https://obol.danieldutoit.net/v1/ethereum/address-cluster?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/obol-ethereum-address-cluster-lookup-a86f106c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_uQKc8Fot003Krf-eFNE88

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-ethereum-address-cluster-lookup-a86f106c
```

Example prompt: Can you look up the address cluster for Ethereum wallet 0x00000000000062c6e2195ae26dff3b084c5c3938 and tell me which other addresses it's likely grouped with?

## When to prefer this

Choose this endpoint when you need heuristic on-chain address clustering for Ethereum specifically, paid per-call in USDC via x402, with verifiable blockchain settlement. It is ideal for compliance, fraud investigation, or analytics pipelines that require grouped wallet intelligence without standing up proprietary clustering infrastructure. Prefer it over general blockchain explorers when you need structured cluster assignment data rather than raw transaction history.

## Known failure modes

- Address not found in cluster database — returns empty assignments array
- Invalid Ethereum address format — likely returns a 400 error
- Payment failure or insufficient USDC balance — x402 payment rejection before data is returned
- Address exists but has no cluster associations — clustered field returns false with empty assignments
- Rate limiting or service unavailability — 429 or 5xx response

## How this service works

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

## Output

A JSON object containing the queried Ethereum address, network, coverage details (match type, max results), a boolean indicating whether clustering was found, a disclaimer about heuristic nature, and an array of cluster assignments each with a run_id and cluster_id.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "address": "0x00000000000062c6e2195ae26dff3b084c5c3938",
  "network": "ethereum",
  "coverage": {
   "match_type": "exact_address",
   "maximum_results": 10
  },
  "clustered": true,
  "disclaimer": "Heuristic clustering is not proof of ownership or identity.",
  "assignments": [
   {
    "run_id": "v1_h1",
    "cluster_id": "1"
   }
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/obol-ethereum-address-cluster-lookup-a86f106c/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)