0x2971…fc2d
Paid $0.06 of the $258.54M Roundhouse has indexed across 713,171 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (65)
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 |
|---|---|---|---|---|
| Crypto Markets | 100% | $0.06 | 62 | 1 |
Every merchant paid publishes at least one catalogued endpoint.
Services it paid
A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; for 1 of 1 the amount paid narrows the list to the ones listed at that price.
- 0x0e84…b808 · last paid 73d ago$0.0662 calls
▸33 of 80 catalogued endpoints list a price this agent paid
- /crypto-newsPrice match$0.001 listed
- /base-ecosystem-newsPrice match$0.001 listed
- /rh-seasonPrice match$0.001 listed
- /pools-trendingPrice match$0.001 listed
- /tweet-search$0.005 listed
- /equity-news$0.003 listed
- /market-risk$0.002 listed
- /base-season$0.002 listed
72 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 | |
|---|---|---|---|---|---|
| 0x0e84…b808 | $0.06 | $0.00 | 62 | 73d ago | Graph |
| 0xab1f…7b37 | $0.00 | $0.007 | 3 | 77d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
90% of observed volume is with a single counterparty, in all 65 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 0x2971…fc2d has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x2971dd412c2a97de2130fe9c65b63f00a9affc2d
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: 0x2971…fc2d curl -s 'https://api.roundhouseai.io/v0/agents/0x2971dd412c2a97de2130fe9c65b63f00a9affc2d' curl -s 'https://api.roundhouseai.io/v0/entities/0x2971dd412c2a97de2130fe9c65b63f00a9affc2d/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. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402, or use an organization key from https://roundhouseai.io/dashboard/team. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.