0x439d…c5e2
Paid $2.00 of the $3061.41M Roundhouse has indexed across 1,398,509 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (2)
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 17m ago$1.001 call
▸1 catalogued endpoints, none priced at an amount this agent paid
- /x402/decode$0.005 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 | |
|---|---|---|---|---|---|
| 0x6b7b…a4e5 | $1.00 | $0.00 | 1 | 17m ago | Graph |
| 0x5cfa…e481 | $0.00 | $0.005 | 1 | 27m ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
100% of observed volume is with a single counterparty, in all 2 observed settlements.
Organic volume $1.01 of $1.01 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x439d…c5e20x6b7b…a4e5 | Base | $1.00 | 100% | coinbase | 17m ago | 0x9c7f92…a20cf3 |
| 0x5cfa…e4810x439d…c5e2 | Base | $0.005 | 100% | payAI | 27m ago | 0xf8e844…3fac8e |
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 0x439d…c5e2 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x439dd40f7d00f74999213d5fe6c3cd0dc155c5e2
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: 0x439d…c5e2 curl -s 'https://api.roundhouseai.io/v0/agents/0x439dd40f7d00f74999213d5fe6c3cd0dc155c5e2' curl -s 'https://api.roundhouseai.io/v0/entities/0x439dd40f7d00f74999213d5fe6c3cd0dc155c5e2/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.