0xab51…bdcf
Paid $0.04 of the $846.70M Roundhouse has indexed across 1,330,126 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (4)
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 |
|---|---|---|---|---|
| Reference Data | 86% | $0.03 | 3 | 1 |
| Location & Weather | 14% | $0.005 | 1 | 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 2 of 2 the amount paid narrows the list to the ones listed at that price.
- 0x7373…2bef · last paid 3d ago$0.033 calls
▸5 of 5 catalogued endpoints list a price this agent paid
- /v1/dns-auditPrice matchDomain and DNS lookup$0.01 listed
- /v1/dns-auditPrice match$0.01 listed
- /v1/auditPrice match$0.01 listed
- /v1/auditPrice match$0.01 listed
- /v1/auditPrice match$0.01 listed
- 0x589a…b3d8 · last paid 3d ago$0.0051 call
▸9 of 14 catalogued endpoints list a price this agent paid
- /x402/pingPrice match$0.005 listed
- /x402/paymentPrice match$0.005 listed
- /x402/quotePrice match$0.005 listed
- /x402/statusPrice match$0.005 listed
- /x402/timePrice match$0.005 listed
- /x402/uuidPrice match$0.005 listed
- /x402/randomPrice match$0.005 listed
- /x402/ipPrice matchIP intelligence$0.005 listed
6 further catalogued endpoints not listed.
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x7373…2bef | $0.03 | $0.00 | 3 | 3d ago | Graph |
| 0x589a…b3d8 | $0.005 | $0.00 | 1 | 3d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
86% of observed volume is with a single counterparty, in all 4 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xab51…bdcf0x7373…2bef | Base | $0.01 | 100% | payAI | 3d ago | 0x2b9533…e55b2a |
| 0xab51…bdcf0x7373…2bef | Base | $0.01 | 100% | payAI | 3d ago | 0xfa3694…4fc138 |
| 0xab51…bdcf0x7373…2bef | Base | $0.01 | 100% | payAI | 3d ago | 0x2a5391…8fee95 |
| 0xab51…bdcf0x589a…b3d8 | Base | $0.005 | 100% | coinbase | 3d ago | 0xa1c1a3…0ead99 |
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 0xab51…bdcf has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xab51bd381431299fe1fbdaff9fb4e793132ebdcf
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: 0xab51…bdcf curl -s 'https://api.roundhouseai.io/v0/agents/0xab51bd381431299fe1fbdaff9fb4e793132ebdcf' curl -s 'https://api.roundhouseai.io/v0/entities/0xab51bd381431299fe1fbdaff9fb4e793132ebdcf/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.