0xefa5…9d2c
Paid $0.16 of the $3154.54M Roundhouse has indexed across 1,427,537 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (18)
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.16 | 18 | 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; no listed price matches an amount this agent paid, so nothing narrows them.
- 0x8581…c402 · last paid 74d ago$0.1317 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$0.0079 listed
- /x402/api/twitter/v2/tweets/counts/all$0.01 listed
- /x402/api/twitter/v2/users/:userId/following$0.98 listed
- /x402/api/twitter/v2/users/by/username/:username$0.01 listed
8 further catalogued endpoints not listed.
- 0x0f99…afc2 · last paid 56d ago$0.021 call
▸1 catalogued endpoints, none priced at an amount this agent paid
- /v1/chat/completionsText completion$0.003302 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 | |
|---|---|---|---|---|---|
| 0x8581…c402 | $0.13 | $0.00 | 17 | 74d ago | Graph |
| 0x0f99…afc2 | $0.02 | $0.00 | 1 | 56d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
84% of observed volume is with a single counterparty, in all 18 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 0xefa5…9d2c has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xefa597c9de55742bb079f72aef4f83ba77229d2c
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: 0xefa5…9d2c curl -s 'https://api.roundhouseai.io/v0/agents/0xefa597c9de55742bb079f72aef4f83ba77229d2c' curl -s 'https://api.roundhouseai.io/v0/entities/0xefa597c9de55742bb079f72aef4f83ba77229d2c/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.