0xa672…89df
Paid $1.00 of the $261.41M Roundhouse has indexed across 717,464 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (10)
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 | 100% | $1.00 | 10 | 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; for 1 of 1 the amount paid narrows the list to the ones listed at that price.
- 0x4e9b…5edb · last paid 330d ago$1.0010 calls
▸2 of 7 catalogued endpoints list a price this agent paid
- /twitter/@canza_ioPrice match$0.10 listed
- /token/addressPrice match$0.10 listed
- /token/gems-list$0.01 listed
- /token/leaderboard$0.01 listed
- /token/gems-list$0.01 listed
- /token/leaderboard$0.01 listed
- /twitter/@canza_io$1.00 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 | |
|---|---|---|---|---|---|
| 0x4e9b…5edb | $1.00 | $0.00 | 10 | 330d 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 10 observed settlements.
Organic volume $1.00 of $1.00 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xa672…89df0x4e9b…5edb | Base | $0.10 | 100% | x402rs | 330d ago | 0xa404fe…2bdfd7 |
| 0xa672…89df0x4e9b…5edb | Base | $0.10 | 100% | x402rs | 330d ago | 0xbb5ec7…223276 |
| 0xa672…89df0x4e9b…5edb | Base | $0.10 | 100% | x402rs | 330d ago | 0xee7e79…122fae |
| 0xa672…89df0x4e9b…5edb | Base | $0.10 | 100% | x402rs | 330d ago | 0xb668b3…20ea3b |
| 0xa672…89df0x4e9b…5edb | Base | $0.10 | 100% | x402rs | 330d ago | 0x4b4df8…2e0b50 |
| 0xa672…89df0x4e9b…5edb | Base | $0.10 | 100% | x402rs | 330d ago | 0x9326a2…9633eb |
| 0xa672…89df0x4e9b…5edb | Base | $0.10 | 100% | x402rs | 330d ago | 0xdbd08f…217f9e |
| 0xa672…89df0x4e9b…5edb | Base | $0.10 | 100% | x402rs | 330d ago | 0xb8cc4d…7a5b46 |
| 0xa672…89df0x4e9b…5edb | Base | $0.10 | 100% | x402rs | 330d ago | 0x510af8…4d23ba |
| 0xa672…89df0x4e9b…5edb | Base | $0.10 | 100% | x402rs | 330d ago | 0x17109c…3a9c27 |
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 0xa672…89df has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xa6727e31fe17f0e1ce6c40d82173b4a9bd0b89df
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: 0xa672…89df curl -s 'https://api.roundhouseai.io/v0/agents/0xa6727e31fe17f0e1ce6c40d82173b4a9bd0b89df' curl -s 'https://api.roundhouseai.io/v0/entities/0xa6727e31fe17f0e1ce6c40d82173b4a9bd0b89df/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.