0xb40e…0e9a
Paid $0.59 of the $3058.83M Roundhouse has indexed across 1,396,716 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (6)
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% | $0.59 | 6 | 2 |
$0.52 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.
- 0x5da4…6c70 · last paid 48d ago$0.522 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x6a9c…5c67 · last paid 48d ago$0.074 calls
▸2 of 2 catalogued endpoints list a price this agent paid
- /x402/resource/temple.catalogPrice match$0.01 listed
- /x402/resource/hermes.pulsePrice match$0.01 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 | |
|---|---|---|---|---|---|
| 0x5da4…6c70 | $0.52 | $0.00 | 2 | 48d ago | Graph |
| 0x6a9c…5c67 | $0.07 | $0.00 | 4 | 48d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
88% of observed volume is with a single counterparty, in all 6 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xb40e…0e9a0x5da4…6c70 | Base | $0.26 | 70% | 0x35ad…204d | 48d ago | 0x8a80ab…806b5f |
| 0xb40e…0e9a0x6a9c…5c67 | Base | $0.01 | 100% | payAI | 48d ago | 0x06b900…6f2f85 |
| 0xb40e…0e9a0x5da4…6c70 | Base | $0.26 | 70% | 0x35ad…204d | 48d ago | 0xd7c28b…667c75 |
| 0xb40e…0e9a0x6a9c…5c67 | Base | $0.02 | 100% | payAI | 50d ago | 0xacb203…6914f5 |
| 0xb40e…0e9a0x6a9c…5c67 | Base | $0.02 | 100% | payAI | 50d ago | 0x5b589c…15ecce |
| 0xb40e…0e9a0x6a9c…5c67 | Base | $0.02 | 100% | payAI | 50d ago | 0x87c1d2…f4b554 |
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 0xb40e…0e9a has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xb40ed814c9e088c6d22f083944ca4cc874cb0e9a
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: 0xb40e…0e9a curl -s 'https://api.roundhouseai.io/v0/agents/0xb40ed814c9e088c6d22f083944ca4cc874cb0e9a' curl -s 'https://api.roundhouseai.io/v0/entities/0xb40ed814c9e088c6d22f083944ca4cc874cb0e9a/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.