0x5837…2a7c
Paid $85.63 of the $3066.54M Roundhouse has indexed across 1,400,510 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (1000)
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% | $33.55 | 1,000 | 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.
- 0xa4bb…3c91 · last paid 8m ago$33.551,000 calls
▸39 catalogued endpoints, none priced at an amount this agent paid
- /x402/portfolio-tracker$0.00 listed
- /x402/multi-chain-balance$0.00 listed
- /x402/seamless-chain-bridge$0.000001 listed
- /x402/approval-manager$0.000001 listed
- /x402/token-price$0.00 listed
- /x402/instant-agent-wallet$0.000001 listed
- /x402/smart-contract-audit$0.001 listed
- /x402/construction-progress$0.000001 listed
31 further catalogued endpoints not listed.
Folded from this wallet's 1,000 most recent settlements of 1,818 lifetime, which is as far back as one scan reaches — so every figure in this section is a floor, and the totals above are not.
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 | |
|---|---|---|---|---|---|
| 0xa4bb…3c91 | $33.55 | $0.00 | 1,000 | 8m 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; all observed volume is with one counterparty, in the 1000 most recent settlements scanned (its history is longer than the 2000-row scan cap).
Organic volume $33.55 of $33.55 total.
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 0x5837…2a7c has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x5837a864c03912ea14a5609968f73e75b9d42a7c
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: 0x5837…2a7c curl -s 'https://api.roundhouseai.io/v0/agents/0x5837a864c03912ea14a5609968f73e75b9d42a7c' curl -s 'https://api.roundhouseai.io/v0/entities/0x5837a864c03912ea14a5609968f73e75b9d42a7c/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.