0xb31f…a9d7
Paid $1.00 of the $3218.17M Roundhouse has indexed across 1,446,529 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 |
|---|---|---|---|---|
| Not in any catalogue | 100% | $1.00 | 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; no listed price matches an amount this agent paid, so nothing narrows them.
- 0x6b7b…a4e5 · last paid 7d ago$1.001 call
▸3 catalogued endpoints, none priced at an amount this agent paid
- /x402/decode$0.005 listed
- /x402/decode$0.005 listed
- /native/evm/encode-call$0.002 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 | |
|---|---|---|---|---|---|
| 0x6b7b…a4e5 | $1.00 | $0.00 | 1 | 7d ago | Graph |
| 0x53cc…dbfc | $0.00 | $0.28 | 1 | 52d ago | Graph |
| 0xb74d…0a1a | $0.00 | $0.13 | 2 | 7d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
71% of observed volume is with a single counterparty, in all 4 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xb31f…a9d70x6b7b…a4e5 | Base | $1.00 | 100% | coinbase | 7d ago | 0xb5846e…342c27 |
| 0xb74d…0a1a0xb31f…a9d7 | Base | $0.03 | 100% | coinbase | 7d ago | 0xdf8d14…0773e4 |
| 0xb74d…0a1a0xb31f…a9d7 | Base | $0.10 | 100% | coinbase | 7d ago | 0xccd35f…2e52d2 |
| 0x53cc…dbfc0xb31f…a9d7 | Base | $0.28 | 100% | fluxa | 52d ago | 0x085d1d…a0a687 |
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 0xb31f…a9d7 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xb31f233dc73180be98d7683c2c20c3a273d9a9d7
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: 0xb31f…a9d7 curl -s 'https://api.roundhouseai.io/v0/agents/0xb31f233dc73180be98d7683c2c20c3a273d9a9d7' curl -s 'https://api.roundhouseai.io/v0/entities/0xb31f233dc73180be98d7683c2c20c3a273d9a9d7/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.