AgentReport

0x53f2…77dd

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

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

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

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.032561

$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
    256 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.00256276d 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 256 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams341d ago0x81946e…355688
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams341d ago0x673c23…db2059
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams341d ago0x8dfee2…450a98
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams341d ago0x480e3f…6fc638
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams341d ago0x1fcb45…457875
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams341d ago0x05c512…641289
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams341d ago0xa99328…6fab3a
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams342d ago0xfb08c8…11b27c
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams342d ago0x893650…269c82
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams342d ago0x986509…a47201
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams342d ago0x98c4e4…18e78c
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams342d ago0x61e68f…afa52b
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams342d ago0x65e6e3…db74fb
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams342d ago0xcdd558…271d7f
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams342d ago0xf869ff…28e287
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams342d ago0x327bce…6ef1d7
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams342d ago0x60ce66…837ccc
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams342d ago0x53c578…fe70b7
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams343d ago0x046bd6…dfff2c
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams343d ago0xc2cf54…cfb985
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams343d ago0xdc225d…60e723
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams343d ago0xf3cea7…6097b7
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams343d ago0x9c68f6…8eb8e3
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams343d ago0xbc6d60…c486a4
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams343d ago0x347ec0…5ddf25

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

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

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: 0x53f2…77dd

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