0x49a1…953d
Paid $0.31 of the $846.52M Roundhouse has indexed across 1,329,508 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (31)
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 | 65% | $0.20 | 20 | 1 |
| Web & Content | 35% | $0.11 | 11 | 1 |
$0.20 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.
- 0x7f1e…3a86 · last paid 22d ago$0.2020 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xb0ae…2099 · last paid 22d ago$0.1111 calls
▸23 of 55 catalogued endpoints list a price this agent paid
- /web/searchPrice matchWeb search$0.01 listed
- /agent/wantPrice match$0.01 listed
- /web/placesPrice match$0.01 listed
- /relay/crypto-newsPrice match$0.01 listed
- /llm/chatText completion$0.002 listed
- /crypto/feed/renew$2.00 listed
- /x402/counterparty-check$0.02 listed
- /x402/settlement-attest$0.25 listed
47 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 | |
|---|---|---|---|---|---|
| 0x7f1e…3a86 | $0.20 | $0.00 | 20 | 22d ago | Graph |
| 0xb0ae…2099 | $0.11 | $0.00 | 11 | 22d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
65% of observed volume is with a single counterparty, in all 31 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 0x49a1…953d has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x49a1bb680ae42e04a3c5ed3707fb4e99c8c8953d
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: 0x49a1…953d curl -s 'https://api.roundhouseai.io/v0/agents/0x49a1bb680ae42e04a3c5ed3707fb4e99c8c8953d' curl -s 'https://api.roundhouseai.io/v0/entities/0x49a1bb680ae42e04a3c5ed3707fb4e99c8c8953d/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.