0x8a6f…2ae1
Paid $38.94 of the $3180.09M Roundhouse has indexed across 1,433,243 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (1) · Ethereum (2)
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 | 56% | $21.72 | 1 | 1 |
| Onchain Data | 44% | $17.21 | 2 | 1 |
$21.72 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.
- 0x3fe2…bcc1 · last paid 118d ago$21.721 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x0000…0000 · last paid 141d ago$17.212 calls
▸1 catalogued endpoints, none priced at an amount this agent paid
- /x402/gasGas price$0.80 listed
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 | |
|---|---|---|---|---|---|
| 0x3fe2…bcc1 | $21.72 | $0.00 | 1 | 118d ago | Graph |
| 0x0000…0000 | $17.21 | $0.00 | 2 | 141d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
56% of observed volume is with a single counterparty, in all 3 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x8a6f…2ae10x3fe2…bcc1 | Base | $21.72 | 70% | 0x4661…93fd | 118d ago | 0xc19f90…92c136 |
| 0x8a6f…2ae10x0000…0000 | Ethereum | $6.30 | 70% | 0x3c27…bb3a | 141d ago | 0x3b563f…dcca07 |
| 0x8a6f…2ae10x0000…0000 | Ethereum | $10.91 | 70% | 0x3c27…bb3a | 142d ago | 0x006d52…f2946a |
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 0x8a6f…2ae1 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x8a6f1a02b4e3c35cdbfed31455e5bc4cc8bb2ae1
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: 0x8a6f…2ae1 curl -s 'https://api.roundhouseai.io/v0/agents/0x8a6f1a02b4e3c35cdbfed31455e5bc4cc8bb2ae1' curl -s 'https://api.roundhouseai.io/v0/entities/0x8a6f1a02b4e3c35cdbfed31455e5bc4cc8bb2ae1/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.