0xa39d…b58d
Paid $15.05 of the $3059.45M Roundhouse has indexed across 1,397,282 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (56)
What it buys
Grouped by the capability each merchant's catalogue is mostly about. A merchant counts once, in one group — nothing records which of its endpoints a payment bought.
| Group | Share | Spent | Calls | Sellers |
|---|---|---|---|---|
| Not in any catalogue | 100% | $15.05 | 56 | 5 |
$3.60 went to wallets that publish no endpoint in any catalogue we crawl — spend we can see and cannot describe.
Services it paid
A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; for 2 of 5 the amount paid narrows the list to the ones listed at that price.
- 0x07f0…a045 · last paid 242d ago$8.003 calls
▸3 catalogued endpoints, none priced at an amount this agent paid
- /api/upload$0.01 listed
- /api/upload$0.01 listed
- /pay/agent_stablestudio_dev$0.01 listed
- 0x5406…2300 · last paid 242d ago$3.6018 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x6e10…98a7 · last paid 243d ago$3.003 calls
▸1 of 1 catalogued endpoints list a price this agent paid
- /api/projects/logo-by-generative-goods/x402-mintPrice match$1.00 listed
- 0x7dd5…2629 · last paid 242d ago$0.4530 calls
▸2 of 127 catalogued endpoints list a price this agent paid
- /api/tts/elevenlabs$0.02 listed
- /api/crypto/priceCrypto spot price$0.001 listed
- /api/travel/flights$0.02 listed
- /api/llm/kat-coder-pro-v2.5$0.01 listed
- /api/ipfs/pin$0.01 listed
- /api/crypto/trending$0.001 listed
- /api/travel/hotels$0.02 listed
- /api/ens/resolve$0.001 listed
119 further catalogued endpoints not listed.
- 0x8fb6…af8f · last paid 244d ago$0.0022 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
One merchant publishes more endpoints than a single catalogue read returns; its list is partial.
Funds flow over time
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x07f0…a045 | $8.00 | $0.00 | 3 | 242d ago | Graph |
| 0x5406…2300 | $3.60 | $0.00 | 18 | 242d ago | Graph |
| 0x6e10…98a7 | $3.00 | $0.00 | 3 | 243d ago | Graph |
| 0x7dd5…2629 | $0.45 | $0.00 | 30 | 242d ago | Graph |
| 0x8fb6…af8f | $0.002 | $0.00 | 2 | 244d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
53% of observed volume is with a single counterparty, in all 56 observed settlements.
Recent activity
Hand this page to an agent
Copy the prompt and paste it into Claude, an MCP client or your own agent — it will check what 0xa39d…b58d has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xa39dae98bf5c1f928095633e531d085dbc10b58d
Show the promptHide the prompt
Using Roundhouse, vet this agent for me: what is it, what has it paid for, and does its on-chain record support what its card claims? Agent: 0xa39d…b58d curl -s 'https://api.roundhouseai.io/v0/agents/0xa39dae98bf5c1f928095633e531d085dbc10b58d' curl -s 'https://api.roundhouseai.io/v0/entities/0xa39dae98bf5c1f928095633e531d085dbc10b58d/settlements' Roundhouse indexes public chain data and does not vouch for any agent's claims — treat the card as a claim and the settlements as the evidence. The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except /v0/unified* and /v0/endpoints. Either pay over x402 (mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402), or ask me for an organization key, which I create at https://roundhouseai.io/dashboard/connections. If you have neither, ask before going further. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.