0x648c…e15d
Paid $0.00045 of the $258.65M Roundhouse has indexed across 713,540 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 | 100% | $0.00045 | 3 | 1 |
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; no listed price matches an amount this agent paid, so nothing narrows them.
- 0x8581…c402 · last paid 92d ago$0.000453 calls
▸16 catalogued endpoints, none priced at an amount this agent paid
- /x402/api/twitter/v2/tweets/search/recent$0.05 listed
- /x402/api/inference/v1/chat/completionsText completion$0.003302 listed
- /x402/api/twitter/v2/tweets/search/all$0.05 listed
- /min30/v1/chat/completionsText completion$0.003301 listed
- /x402/api/twitter/v2/tweets/counts/all$0.01 listed
- /x402/api/twitter/v2/tweets$0.0079 listed
- /x402/api/twitter/v2/users/:userId/tweets$0.05 listed
- /x402/api/twitter/v2/tweets/:tweetId$0.0079 listed
8 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 | |
|---|---|---|---|---|---|
| 0x8581…c402 | $0.00045 | $0.00 | 3 | 92d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 3 observed settlements.
Organic volume $0.00045 of $0.00045 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x648c…e15d0x8581…c402 | Base | $0.00015 | 25% | Payer-submitted | 92d ago | 0xeb25e3…3200da |
| 0x648c…e15d0x8581…c402 | Base | $0.00015 | 25% | Payer-submitted | 92d ago | 0x95655f…da18bf |
| 0x648c…e15d0x8581…c402 | Base | $0.00015 | 25% | Payer-submitted | 92d ago | 0x068a96…018db4 |
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 0x648c…e15d has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x648c2413f86f50561779a0bfe91876d72256e15d
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: 0x648c…e15d curl -s 'https://api.roundhouseai.io/v0/agents/0x648c2413f86f50561779a0bfe91876d72256e15d' curl -s 'https://api.roundhouseai.io/v0/entities/0x648c2413f86f50561779a0bfe91876d72256e15d/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.