0x31e9…e344
Paid $12,254.85 of the $847.30M Roundhouse has indexed across 1,331,054 wallets — 0.0014% of it.
Chains (from the recent scan): Base (8)
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% | $12,254.85 | 2 | 1 |
$12,254.85 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.
- 0x0ec8…38ca · last paid 434d ago$12,254.852 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x1859…11c2 | $0.00 | $12,272.18 | 6 | 434d ago | Graph |
| 0x0ec8…38ca | $12,254.85 | $0.00 | 2 | 434d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
50% of observed volume is with a single counterparty, in all 8 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x31e9…e3440x0ec8…38ca | Base | $2.90 | 70% | 0xe890…f632 | 434d ago | 0xbc92d3…dc5a02 |
| 0x31e9…e3440x0ec8…38ca | Base | $12,251.95 | 70% | 0xe890…f632 | 434d ago | 0x1854fc…81c19d |
| 0x1859…11c20x31e9…e344 | Base | $1.95 | 70% | 0xe890…f632 | 434d ago | 0x896256…99e317 |
| 0x1859…11c20x31e9…e344 | Base | $2.00 | 70% | 0xe890…f632 | 434d ago | 0xb1a863…fcfcbf |
| 0x1859…11c20x31e9…e344 | Base | $2.00 | 70% | 0xe890…f632 | 434d ago | 0x395ad8…2019c4 |
| 0x1859…11c20x31e9…e344 | Base | $6.90 | 70% | 0xe890…f632 | 434d ago | 0xccec8f…81d477 |
| 0x1859…11c20x31e9…e344 | Base | $1,944.19 | 70% | 0xe890…f632 | 434d ago | 0xc7b029…186dd3 |
| 0x1859…11c20x31e9…e344 | Base | $10,315.14 | 70% | 0xe890…f632 | 434d ago | 0x19c0cf…bbea62 |
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 0x31e9…e344 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x31e9daba8c229493f24618b8aea355690bdde344
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: 0x31e9…e344 curl -s 'https://api.roundhouseai.io/v0/agents/0x31e9daba8c229493f24618b8aea355690bdde344' curl -s 'https://api.roundhouseai.io/v0/entities/0x31e9daba8c229493f24618b8aea355690bdde344/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.