0xd03a…8528
Paid $0.003 of the $3058.83M Roundhouse has indexed across 1,396,904 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 |
|---|---|---|---|---|
| Not in any catalogue | 67% | $0.002 | 2 | 1 |
| Location & Weather | 33% | $0.001 | 1 | 1 |
$0.002 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.
- 0x480a…4132 · last paid 20h ago$0.0022 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xd6fc…fb0a · last paid 20h ago$0.0011 call
▸19 of 23 catalogued endpoints list a price this agent paid
- /weather/currentPrice matchWeather forecast$0.001 listed
- /geo/forwardPrice matchGeocoding$0.001 listed
- /crypto/bundlePrice match$0.001 listed
- /weather/marinePrice matchWeather forecast$0.001 listed
- /weather/nowPrice matchWeather forecast$0.001 listed
- /defi/yieldsPrice match$0.001 listed
- /crypto/pricePrice matchCrypto spot price$0.001 listed
- /screen/entityPrice matchSanctions screening$0.001 listed
15 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 | |
|---|---|---|---|---|---|
| 0x480a…4132 | $0.002 | $0.00 | 2 | 20h ago | Graph |
| 0xd6fc…fb0a | $0.001 | $0.00 | 1 | 20h ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
67% of observed volume is with a single counterparty, in all 3 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xd03a…85280x480a…4132 | Base | $0.001 | 100% | payAI | 20h ago | 0x52db5f…379e37 |
| 0xd03a…85280x480a…4132 | Base | $0.001 | 100% | payAI | 20h ago | 0xa44497…a14bf7 |
| 0xd03a…85280xd6fc…fb0a | Base | $0.001 | 100% | coinbase | 20h ago | 0x714370…c9bffb |
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 0xd03a…8528 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xd03a66ec5077037f882b5cf424a073d9fdcd8528
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: 0xd03a…8528 curl -s 'https://api.roundhouseai.io/v0/agents/0xd03a66ec5077037f882b5cf424a073d9fdcd8528' curl -s 'https://api.roundhouseai.io/v0/entities/0xd03a66ec5077037f882b5cf424a073d9fdcd8528/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.