0xdc30…4077
Paid $0.05 of the $258.78M Roundhouse has indexed across 713,781 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (3)
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 |
|---|---|---|---|---|
| AI & Media | 59% | $0.03 | 2 | 1 |
| Not in any catalogue | 41% | $0.02 | 1 | 1 |
$0.02 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; no listed price matches an amount this agent paid, so nothing narrows them.
- 0xe903…1abf · last paid 197d ago$0.032 calls
▸200 catalogued endpoints, none priced at an amount this agent paid
- /api/v1/chat/completionsText completion$0.002 listed
- /api/v1/messages$0.01 listed
- /api/v1/exa/answerText completion$0.01 listed
- /api/v1/exa/searchWeb search$0.01 listed
- /api/v1/exa/contents$0.003 listed
- /api/v1/images/generations$0.04 listed
- /api/v1/searchWeb search$0.26 listed
- /api/v1/stocks/us/price/AAPL$0.002 listed
192 further catalogued endpoints not listed.
- 0x1b09…5e99 · last paid 197d ago$0.021 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 | |
|---|---|---|---|---|---|
| 0xe903…1abf | $0.03 | $0.00 | 2 | 197d ago | Graph |
| 0x1b09…5e99 | $0.02 | $0.00 | 1 | 197d 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 3 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xdc30…40770x1b09…5e99 | Base | $0.02 | 100% | coinbase | 197d ago | 0x24bc8d…77bc15 |
| 0xdc30…40770xe903…1abf | Base | $0.01 | 100% | coinbase | 197d ago | 0x12b224…8c3a52 |
| 0xdc30…40770xe903…1abf | Base | $0.01 | 100% | coinbase | 197d ago | 0x371c92…bf8ca1 |
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 0xdc30…4077 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xdc30677cb80eb6206a313b7e91e18933a3d24077
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: 0xdc30…4077 curl -s 'https://api.roundhouseai.io/v0/agents/0xdc30677cb80eb6206a313b7e91e18933a3d24077' curl -s 'https://api.roundhouseai.io/v0/entities/0xdc30677cb80eb6206a313b7e91e18933a3d24077/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. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402, or use an organization key from https://roundhouseai.io/dashboard/team. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.