0xa278…90ed
Paid $369.21 of the $3059.45M Roundhouse has indexed across 1,397,037 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (17)
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% | $369.00 | 2 | 2 |
| Onchain Data | <1% | $0.21 | 13 | 1 |
$300.00 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 1 of 3 the amount paid narrows the list to the ones listed at that price.
- 0x0a20…d8c2 · last paid 438d ago$300.001 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x0773…4d39 · last paid 335d ago$69.001 call
▸1 catalogued endpoints, none priced at an amount this agent paid
- /api/x402/ping$0.001 listed
- 0xb800…8a5f · last paid 16d ago$0.2113 calls
▸9 of 9 catalogued endpoints list a price this agent paid
- /samplePrice match$0.01 listed
- /pingPrice match$0.001 listed
- /tokenPrice matchToken metadata$0.01 listed
- /recommendPrice match$0.01 listed
- /checkPrice match$0.01 listed
- /pingPrice match$0.001 listed
- /checkPrice match$0.10 listed
- /marketPrice match$0.02 listed
1 further catalogued endpoints not 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 | |
|---|---|---|---|---|---|
| 0x0a20…d8c2 | $300.00 | $2.00 | 2 | 436d ago | Graph |
| 0x0773…4d39 | $69.00 | $0.00 | 1 | 335d ago | Graph |
| 0xd145…72ec | $0.00 | $33.77 | 1 | 440d ago | Graph |
| 0xb800…8a5f | $0.21 | $0.00 | 13 | 16d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
75% of observed volume is with a single counterparty, in all 17 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 0xa278…90ed has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xa278b3943c7c58eb0d26be397507285adf6490ed
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: 0xa278…90ed curl -s 'https://api.roundhouseai.io/v0/agents/0xa278b3943c7c58eb0d26be397507285adf6490ed' curl -s 'https://api.roundhouseai.io/v0/entities/0xa278b3943c7c58eb0d26be397507285adf6490ed/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.