0x210c…e7bb
Paid $7,401.47 of the $3103.01M Roundhouse has indexed across 1,403,877 wallets — 0.0002% of it.
Counted from this wallet’s own settlements. The index rollup has no row for it yet, which is normal for an address first seen in the last half hour.
Chains (from the recent scan): Robinhood Chain (3)
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% | $7,401.47 | 3 | 2 |
$7,401.47 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; no listed price matches an amount this agent paid, so nothing narrows them.
- 0xd29c…7978 · last paid 1d ago$6,213.112 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x52e6…71ca · last paid 1d ago$1,188.361 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0xd29c…7978 | $6,213.11 | $0.00 | 2 | 1d ago | Graph |
| 0x52e6…71ca | $1,188.36 | $0.00 | 1 | 1d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
84% of observed volume is with a single counterparty, in all 3 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x210c…e7bb0xd29c…7978 | Robinhood Chain | $1,215.16 | 70% | 0x07ae…0e67 | 1d ago | 0x20642b…07eb4a |
| 0x210c…e7bb0x52e6…71ca | Robinhood Chain | $1,188.36 | 70% | 0x07ae…0e67 | 1d ago | 0x4f73d2…2ee182 |
| 0x210c…e7bb0xd29c…7978 | Robinhood Chain | $4,997.95 | 70% | 0xc99d…a8f4 | 3d ago | 0xbfa68e…9eed27 |
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 0x210c…e7bb has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x210c55b74ad19f9da4c3cffdb85b869144a4e7bb
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: 0x210c…e7bb curl -s 'https://api.roundhouseai.io/v0/agents/0x210c55b74ad19f9da4c3cffdb85b869144a4e7bb' curl -s 'https://api.roundhouseai.io/v0/entities/0x210c55b74ad19f9da4c3cffdb85b869144a4e7bb/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.