0x6847…1f8d
Paid $6.78 of the $3104.95M Roundhouse has indexed across 1,404,805 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (47)
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 |
|---|---|---|---|---|
| Company & People | 100% | $6.78 | 44 | 2 |
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 2 the amount paid narrows the list to the ones listed at that price.
- 0xade0…89ab · last paid 96d ago$5.8325 calls
▸2 catalogued endpoints, none priced at an amount this agent paid
- /api/company/enrichCompany enrichment$0.10 listed
- /api/person/from-email$0.12 listed
- 0xe740…cf46 · last paid 89d ago$0.9519 calls
▸11 of 15 catalogued endpoints list a price this agent paid
- /agent/v1/profiles/enrichPrice matchCompany enrichment$0.05 listed
- /agent/v1/companies/enrichPrice matchCompany enrichment$0.05 listed
- /agent/v1/profiles/emailPrice matchEmail verification$0.05 listed
- /agent/v1/profiles/:profilePrice match$0.05 listed
- /agent/v1/jobs/getPrice match$0.05 listed
- /agent/v1/geo-id$0.01 listed
- /agent/v1/profiles/searchWeb search$0.30 listed
- /agent/v1/profiles/posts$0.25 listed
7 further catalogued endpoints not listed.
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 | |
|---|---|---|---|---|---|
| 0xa449…15ac | $0.00 | $7.50 | 3 | 96d ago | Graph |
| 0xade0…89ab | $5.83 | $0.00 | 25 | 96d ago | Graph |
| 0xe740…cf46 | $0.95 | $0.00 | 19 | 89d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
53% of observed volume is with a single counterparty, in all 47 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 0x6847…1f8d has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x68478766862eaf5e4c6d8a0a02da6ddb6a2c1f8d
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: 0x6847…1f8d curl -s 'https://api.roundhouseai.io/v0/agents/0x68478766862eaf5e4c6d8a0a02da6ddb6a2c1f8d' curl -s 'https://api.roundhouseai.io/v0/entities/0x68478766862eaf5e4c6d8a0a02da6ddb6a2c1f8d/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.