0xd460…bd5a
Paid $0.02 of the $3058.83M Roundhouse has indexed across 1,396,904 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 |
|---|---|---|---|---|
| Crypto Markets | 59% | $0.01 | 1 | 1 |
| Not in any catalogue | 41% | $0.007 | 1 | 1 |
$0.007 went to wallets that publish no endpoint in any catalogue we crawl — spend we can see and cannot describe.
Services it paid
A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; for 1 of 2 the amount paid narrows the list to the ones listed at that price.
- 0x7d9c…cb5b · last paid 29d ago$0.011 call
▸162 of 200 catalogued endpoints list a price this agent paid
- /v1/services/macro-tr-central-government-debtPrice match$0.01 listed
- /v1/services/perp-funding-ratesPrice matchPerp funding and open interest$0.01 listed
- /v1/services/eth-etf-flow-pulsePrice match$0.01 listed
- /v1/services/eth-leverage-riskPrice match$0.01 listed
- /v1/services/xrp-liquidity-reportPrice match$0.01 listed
- /v1/services/zar-fx-asset-manager-positioningPrice match$0.01 listed
- /v1/services/edge-signal-snapshotPrice match$0.01 listed
- /v1/services/eth-network-valuation-intelligence$0.10 listed
192 further catalogued endpoints not listed.
- 0xb98e…2dbc · last paid 28d ago$0.0071 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
One merchant publishes more endpoints than a single catalogue read returns; its list is partial.
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x7d9c…cb5b | $0.01 | $0.00 | 1 | 29d ago | Graph |
| 0xb98e…2dbc | $0.007 | $0.00 | 1 | 28d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
59% of observed volume is with a single counterparty, in all 2 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xd460…bd5a0xb98e…2dbc | Base | $0.007 | 70% | 0xa483…ad30 | 28d ago | 0xa81544…8efdac |
| 0xd460…bd5a0x7d9c…cb5b | Base | $0.01 | 100% | coinbase | 29d ago | 0xc551c1…62c4cd |
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 0xd460…bd5a has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xd460d1c713ad04e14eac4ec78daaff407fe1bd5a
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: 0xd460…bd5a curl -s 'https://api.roundhouseai.io/v0/agents/0xd460d1c713ad04e14eac4ec78daaff407fe1bd5a' curl -s 'https://api.roundhouseai.io/v0/entities/0xd460d1c713ad04e14eac4ec78daaff407fe1bd5a/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.