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%daydreams337d ago0x771c2a…0d01f1
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams337d ago0x8cf371…6b9fee
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams338d ago0x2eeeb7…911006
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams338d ago0x728e30…55be72
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams338d ago0x984d29…1908ed
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams338d ago0x507845…68edba
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams338d ago0x295dde…3ffaec
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams338d ago0xdd42bb…048bdc
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams339d ago0x9bf834…6e12ef
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams339d ago0xe756e6…1567e8
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams339d ago0xad4925…e8ce0f
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams339d ago0xe8e422…8ed127
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams339d ago0xd929e2…252f6a
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams340d ago0xc10dbd…161db2
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams340d ago0x23dd98…4d4715
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams340d ago0x651905…24adb2
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams340d ago0x911406…0987b7
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams340d ago0x5ea2be…92c093
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams340d ago0x06ddca…5198e0
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams340d ago0x076e30…442988
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams340d ago0x86588f…72a6bb
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams340d ago0xac4584…2fc0b0
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams340d ago0x2fbda3…085545
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams340d ago0x36a1a2…fdcf42
0x53f2…77dd0x6482…b779BaseBase$0.0001100%daydreams341d ago0x9c2e68…cec066

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.