0xd29c…56cd
Paid $0.10 of the $833.89M Roundhouse has indexed across 1,300,243 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (1)
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% | $0.10 | 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; for 1 of 1 the amount paid narrows the list to the ones listed at that price.
- 0x3f60…bf2c · last paid 8d ago$0.101 call
▸7 of 29 catalogued endpoints list a price this agent paid
- /v1/index/fixing$0.01 listed
- /v1/tokens/quotes$0.01 listed
- /v1/capacity/stress$0.01 listed
- /v1/reserved$0.01 listed
- /v1/term/instance$0.01 listed
- /v1/index/history$0.05 listed
- /v1/tokens/historyCrypto price history$0.05 listed
- /v1/spot/export/history$3.00 listed
21 further catalogued endpoints not 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 | |
|---|---|---|---|---|---|
| 0x3f60…bf2c | $0.10 | $0.00 | 1 | 8d 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 all 1 observed settlement.
Organic volume $0.10 of $0.10 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xd29c…56cd0x3f60…bf2c | Base | $0.10 | 100% | coinbase | 8d ago | 0xc55e87…a536e9 |
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 0xd29c…56cd has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xd29ceb047d5cdd9777e56bd8c3b79b267c8256cd
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: 0xd29c…56cd curl -s 'https://api.roundhouseai.io/v0/agents/0xd29ceb047d5cdd9777e56bd8c3b79b267c8256cd' curl -s 'https://api.roundhouseai.io/v0/entities/0xd29ceb047d5cdd9777e56bd8c3b79b267c8256cd/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.