0xb667…83a1
Paid $3.68 of the $3066.17M Roundhouse has indexed across 1,400,092 wallets — less than 0.0001% of it.
Whole-history totals from the index rollup, which can be up to 30 minutes behind.
Chains (from the recent scan): Base (234)
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 | 54% | $2.00 | 1 | 1 |
| Web & Content | 46% | $1.68 | 233 | 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.
- 0x6e31…b687 · last paid 249d ago$2.001 call
▸1 of 20 catalogued endpoints list a price this agent paid
- /v0/drafts$0.00 listed
- /v0/domains/:domain_id$0.00 listed
- /v0/domains$0.00 listed
- /v0/metrics$0.00 listed
- /v0/drafts/:draft_id$0.00 listed
- /v0/inboxes$0.00 listed
- /v0/webhooks$0.00 listed
- /v0/threads$0.00 listed
12 further catalogued endpoints not listed.
- 0x6d6e…9192 · last paid 171d ago$1.68233 calls
▸3 of 3 catalogued endpoints list a price this agent paid
- /searchPrice matchWeb search$0.007 listed
- /contentsPrice match$0.001 listed
- /pay/agent_exa_aiPrice match$0.007 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 | |
|---|---|---|---|---|---|
| 0x6e31…b687 | $2.00 | $0.00 | 1 | 249d ago | Graph |
| 0x6d6e…9192 | $1.68 | $0.00 | 233 | 171d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
54% of observed volume is with a single counterparty, in all 234 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 0xb667…83a1 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xb667e02591db55f47bcb59beb7ff9cd6886b83a1
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: 0xb667…83a1 curl -s 'https://api.roundhouseai.io/v0/agents/0xb667e02591db55f47bcb59beb7ff9cd6886b83a1' curl -s 'https://api.roundhouseai.io/v0/entities/0xb667e02591db55f47bcb59beb7ff9cd6886b83a1/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.