0x2729…861b
Paid $7.33 of the $3067.00M Roundhouse has indexed across 1,401,091 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (432) · Ethereum (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 | 59% | $4.32 | 6 | 2 |
| Onchain Data | 41% | $3.01 | 365 | 1 |
$4.32 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 3 the amount paid narrows the list to the ones listed at that price.
- 0x8707…f9ad · last paid 31d ago$3.325 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xc210…e9ff · last paid 5d ago$3.01365 calls
▸81 of 81 catalogued endpoints list a price this agent paid
- /v1/evm/verdictPrice matchText completion$0.02 listed
- /v1/ai/imagePrice matchImage generation$0.02 listed
- /v2/inferenciaPrice matchText completion$0.001 listed
- /v1/evm/ensPrice match$0.005 listed
- /v1/evm/token-safetyPrice match$0.01 listed
- /v1/crypto/sanctionsPrice matchSanctions screening$0.01 listed
- /v1/doPrice matchText completion$0.02 listed
- /v1/content/word-of-the-dayPrice match$0.005 listed
73 further catalogued endpoints not listed.
- 0x5da4…6c70 · last paid 62d ago$1.001 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.
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 | |
|---|---|---|---|---|---|
| 0xc210…e9ff | $3.01 | $5.30 | 430 | 5d ago | Graph |
| 0x8707…f9ad | $3.32 | $0.00 | 5 | 31d ago | Graph |
| 0x5da4…6c70 | $1.00 | $0.00 | 1 | 62d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
66% of observed volume is with a single counterparty, in all 436 observed settlements.
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 0x2729…861b has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x27295608671e37654dad42a3e366290897a9861b
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: 0x2729…861b curl -s 'https://api.roundhouseai.io/v0/agents/0x27295608671e37654dad42a3e366290897a9861b' curl -s 'https://api.roundhouseai.io/v0/entities/0x27295608671e37654dad42a3e366290897a9861b/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.