AgentReport

0x5362…e401

0x5362504051fd865ec364fc3188494becb930e401Explorer
Paid out
$100.46
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
255
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $100.46 of the $261.16M Roundhouse has indexed across 717,066 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (255)

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.

GroupShareSpentCallsSellers
Not in any catalogue100%$100.462551

$100.46 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; no listed price matches an amount this agent paid, so nothing narrows them.

  • 0xef43…6c7f · last paid 222d ago
    $100.46
    255 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

Balance now
Reading the chain…
Spending power
Reading the chain…
Burn rate
Reading the chain…
Runway
Reading the chain…

Funds flow over time

Activity

MarAprMayJunJulAugSep
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0xef43…6c7f$100.46$0.00255222d agoGraph

Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.

Data quality

100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 255 observed settlements.

Organic volume $100.46 of $100.46 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x5362…e4010xef43…6c7fBase$0.50100%virtuals222d ago0x601fec…bb3eb7
0x5362…e4010xef43…6c7fBase$0.50100%virtuals222d ago0x33c783…f41033
0x5362…e4010xef43…6c7fBase$0.50100%virtuals222d ago0xdd8e90…4d7cf4
0x5362…e4010xef43…6c7fBase$0.50100%virtuals222d ago0x3e838f…4d9400
0x5362…e4010xef43…6c7fBase$0.50100%virtuals222d ago0xc7d8a4…b19de5
0x5362…e4010xef43…6c7fBase$0.50100%virtuals222d ago0xae77a6…149283
0x5362…e4010xef43…6c7fBase$0.50100%virtuals222d ago0x0f92e2…89d119
0x5362…e4010xef43…6c7fBase$0.50100%virtuals222d ago0x9a1f5e…705222
0x5362…e4010xef43…6c7fBase$0.50100%virtuals222d ago0x725d71…28a910
0x5362…e4010xef43…6c7fBase$0.50100%virtuals222d ago0xe5c494…0d0670
0x5362…e4010xef43…6c7fBase$0.50100%virtuals222d ago0x8f0c32…79121e
0x5362…e4010xef43…6c7fBase$0.50100%virtuals222d ago0x63d33b…d0de72
0x5362…e4010xef43…6c7fBase$0.50100%virtuals222d ago0x77ad19…c6cb97
0x5362…e4010xef43…6c7fBase$0.50100%virtuals222d ago0xf22a3f…b9b3b9
0x5362…e4010xef43…6c7fBase$0.50100%virtuals222d ago0x648072…29faf4
0x5362…e4010xef43…6c7fBase$0.50100%virtuals236d ago0xeb47d7…857c19
0x5362…e4010xef43…6c7fBase$0.50100%virtuals236d ago0xa0c934…65efe6
0x5362…e4010xef43…6c7fBase$0.50100%virtuals236d ago0x72ffd2…03ed26
0x5362…e4010xef43…6c7fBase$0.50100%virtuals236d ago0xa7d010…d2f488
0x5362…e4010xef43…6c7fBase$0.50100%virtuals236d ago0xde3fba…0b6364
0x5362…e4010xef43…6c7fBase$0.50100%virtuals236d ago0x274cf5…68387a
0x5362…e4010xef43…6c7fBase$0.50100%virtuals236d ago0x095fbb…754a5c
0x5362…e4010xef43…6c7fBase$0.50100%virtuals236d ago0x06e78e…0abe8d
0x5362…e4010xef43…6c7fBase$0.50100%virtuals236d ago0x41819f…8801fa
0x5362…e4010xef43…6c7fBase$0.50100%virtuals236d ago0x1d2d1a…52d46b

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 0x5362…e401 has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0x5362504051fd865ec364fc3188494becb930e401

Open skill.md
Show 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: 0x5362…e401

curl -s 'https://api.roundhouseai.io/v0/agents/0x5362504051fd865ec364fc3188494becb930e401'
curl -s 'https://api.roundhouseai.io/v0/entities/0x5362504051fd865ec364fc3188494becb930e401/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.