0x6763…cd04
Paid $1.00 of the $260.88M Roundhouse has indexed across 716,644 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 |
|---|---|---|---|---|---|---|
| 0x6763…cd040x4e9b…5edb | Base | $0.10 | 100% | x402rs | 330d ago | 0x8a87ba…4cca7a |
| 0x6763…cd040x4e9b…5edb | Base | $0.10 | 100% | x402rs | 330d ago | 0x17896e…9eb677 |
| 0x6763…cd040x4e9b…5edb | Base | $0.10 | 100% | x402rs | 330d ago | 0xba2ca7…9ff6d0 |
| 0x6763…cd040x4e9b…5edb | Base | $0.10 | 100% | x402rs | 330d ago | 0x019aa4…3ba22c |
| 0x6763…cd040x4e9b…5edb | Base | $0.10 | 100% | x402rs | 330d ago | 0x4a8f47…36e516 |
| 0x6763…cd040x4e9b…5edb | Base | $0.10 | 100% | x402rs | 330d ago | 0xb81534…d92187 |
| 0x6763…cd040x4e9b…5edb | Base | $0.10 | 100% | x402rs | 330d ago | 0x1220fd…db0700 |
| 0x6763…cd040x4e9b…5edb | Base | $0.10 | 100% | x402rs | 330d ago | 0x8e3b7a…2d50f0 |
| 0x6763…cd040x4e9b…5edb | Base | $0.10 | 100% | x402rs | 330d ago | 0xaa31fd…1c34ea |
| 0x6763…cd040x4e9b…5edb | Base | $0.10 | 100% | x402rs | 330d ago | 0xcfd145…bddd3f |
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 0x6763…cd04 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x6763c42c14b7f142aed3fc5dd2059ffd3351cd04
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: 0x6763…cd04 curl -s 'https://api.roundhouseai.io/v0/agents/0x6763c42c14b7f142aed3fc5dd2059ffd3351cd04' curl -s 'https://api.roundhouseai.io/v0/entities/0x6763c42c14b7f142aed3fc5dd2059ffd3351cd04/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.