0x4e42…861d
Paid $0.03 of the $3243.89M Roundhouse has indexed across 1,458,802 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (5)
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 | 60% | $0.02 | 3 | 1 |
| Web & Content | 40% | $0.01 | 2 | 1 |
$0.02 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 2 the amount paid narrows the list to the ones listed at that price.
- 0xffa7…9d04 · last paid 4d ago$0.023 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xbd94…9c3d · last paid 5d ago$0.012 calls
▸9 of 9 catalogued endpoints list a price this agent paid
- /res/v1/web/searchPrice matchWeb search$0.005 listed
- /res/v1/local/place_searchPrice matchWeb search$0.005 listed
- /res/v1/local/descriptionsPrice matchWeb search$0.005 listed
- /res/v1/news/searchPrice match$0.005 listed
- /res/v1/images/searchPrice matchWeb search$0.005 listed
- /res/v1/llm/contextPrice matchWeb search$0.005 listed
- /res/v1/local/poisPrice matchWeb search$0.005 listed
- /res/v1/web/searchPrice matchWeb search$0.005 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 | |
|---|---|---|---|---|---|
| 0xffa7…9d04 | $0.02 | $0.00 | 3 | 4d ago | Graph |
| 0xbd94…9c3d | $0.01 | $0.00 | 2 | 5d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
60% of observed volume is with a single counterparty, in all 5 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x4e42…861d0xffa7…9d04 | Base | $0.005 | 70% | 0x8273…e5a1 | 4d ago | 0xeb8c23…2ff2a2 |
| 0x4e42…861d0xffa7…9d04 | Base | $0.005 | 70% | 0x8273…e5a1 | 4d ago | 0x92df3c…3d174d |
| 0x4e42…861d0xffa7…9d04 | Base | $0.005 | 70% | 0x8273…e5a1 | 4d ago | 0x1554ea…16ab0a |
| 0x4e42…861d0xbd94…9c3d | Base | $0.005 | 70% | 0x8273…e5a1 | 5d ago | 0xf2572e…f7a173 |
| 0x4e42…861d0xbd94…9c3d | Base | $0.005 | 70% | 0x8273…e5a1 | 5d ago | 0xbdc684…65c66b |
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 0x4e42…861d has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x4e429b2000bc95864aa9b2d8fb75a18c51da861d
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: 0x4e42…861d curl -s 'https://api.roundhouseai.io/v0/agents/0x4e429b2000bc95864aa9b2d8fb75a18c51da861d' curl -s 'https://api.roundhouseai.io/v0/entities/0x4e429b2000bc95864aa9b2d8fb75a18c51da861d/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.