AgentReport

0xfd53…a3a8

0xfd5318610d84d95af5e52ed2cb2c975e8258a3a8Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
264
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3067.43M Roundhouse has indexed across 1,401,742 wallets — less than 0.0001% of it.

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

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%$0.032641

$0.03 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.

  • 0x6482…b779 · last paid 276d ago
    $0.03
    264 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

MayJunJulAugSepOctNov
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x6482…b779$0.03$0.00264276d 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 264 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams348d ago0x7a2d9d…cc1409
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams349d ago0x5762e9…1cb5bc
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams349d ago0x39e529…ef82e5
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams349d ago0x6d9474…589245
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams349d ago0xad8329…82d6e8
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams349d ago0x66c3f5…289438
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams349d ago0x788d56…7a406e
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams350d ago0x335779…bb92f9
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams350d ago0x93ccae…4ebcc6
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams350d ago0xe23758…1c9a68
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams350d ago0x4e7ea1…ffc887
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams350d ago0xddd313…9370ce
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams350d ago0x01be23…d36061
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams351d ago0x298337…d16868
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams351d ago0x97967f…7c8c5d
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams351d ago0xdc327d…47e01c
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams351d ago0xdb24cd…122a3f
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams351d ago0xa58e92…204071
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams351d ago0x03504a…4f9278
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams351d ago0xfb1b03…2ba6cd
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams352d ago0x5019ea…934b34
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams352d ago0x6891ed…7ab030
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams352d ago0xb08063…341ab2
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams352d ago0x91ee4e…5b4c1d
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams352d ago0xd51b11…17efd7

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

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

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: 0xfd53…a3a8

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