0x876a…e3c3
Paid $2.97 of the $3053.48M Roundhouse has indexed across 1,395,044 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (196)
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% | $2.94 | 196 | 2 |
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 2 the amount paid narrows the list to the ones listed at that price.
- 0x8b29…721d · last paid 23m ago$1.9698 calls
▸1 of 2 catalogued endpoints list a price this agent paid
- /shop/x402/buyPrice match$0.02 listed
- /x402/cheap-health$0.001 listed
- 0x7284…299c · last paid 23m ago$0.9898 calls
▸2 catalogued endpoints, none priced at an amount this agent paid
- /api/dashboard/q-verdict/resource$0.02 listed
- /api/dashboard/q-verdict/resource$0.02 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 | |
|---|---|---|---|---|---|
| 0x8b29…721d | $1.96 | $0.00 | 98 | 23m ago | Graph |
| 0x7284…299c | $0.98 | $0.00 | 98 | 23m ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
67% of observed volume is with a single counterparty, in all 196 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 0x876a…e3c3 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x876aabda72e80c38651df2e15cfeed4f1cb6e3c3
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: 0x876a…e3c3 curl -s 'https://api.roundhouseai.io/v0/agents/0x876aabda72e80c38651df2e15cfeed4f1cb6e3c3' curl -s 'https://api.roundhouseai.io/v0/entities/0x876aabda72e80c38651df2e15cfeed4f1cb6e3c3/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.