AgentReport

0x52a8…60d1

0x52a82885b745f3211e8e2020c3d5d2865c7d60d1Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
267
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 (267)

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

$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
    267 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.00267276d 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 267 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x52a8…60d10x6482…b779BaseBase$0.0001100%daydreams341d ago0x16afff…334b5e
0x52a8…60d10x6482…b779BaseBase$0.0001100%daydreams341d ago0x3cf73e…216276
0x52a8…60d10x6482…b779BaseBase$0.0001100%daydreams341d ago0x78e01e…d458ba
0x52a8…60d10x6482…b779BaseBase$0.0001100%daydreams341d ago0x2f79cd…fdc3bf
0x52a8…60d10x6482…b779BaseBase$0.0001100%daydreams341d ago0xec7829…51b2db
0x52a8…60d10x6482…b779BaseBase$0.0001100%daydreams342d ago0x7864f0…9a5e2f
0x52a8…60d10x6482…b779BaseBase$0.0001100%daydreams342d ago0x9cbb65…73251a
0x52a8…60d10x6482…b779BaseBase$0.0001100%daydreams342d ago0x96c662…d88480
0x52a8…60d10x6482…b779BaseBase$0.0001100%daydreams342d ago0xd4588d…8cbd58
0x52a8…60d10x6482…b779BaseBase$0.0001100%daydreams342d ago0xc84d51…6eb3c3
0x52a8…60d10x6482…b779BaseBase$0.0001100%daydreams342d ago0x42bcd1…dcb329
0x52a8…60d10x6482…b779BaseBase$0.0001100%daydreams342d ago0xf085fe…431c77
0x52a8…60d10x6482…b779BaseBase$0.0001100%daydreams342d ago0x8ff174…0d9c5a
0x52a8…60d10x6482…b779BaseBase$0.0001100%daydreams342d ago0x031bc6…7f4d69
0x52a8…60d10x6482…b779BaseBase$0.0001100%daydreams342d ago0x3e2141…d571d2
0x52a8…60d10x6482…b779BaseBase$0.0001100%daydreams342d ago0x95f9a5…f8041e
0x52a8…60d10x6482…b779BaseBase$0.0001100%daydreams343d ago0xb15e6c…ae89e9
0x52a8…60d10x6482…b779BaseBase$0.0001100%daydreams343d ago0xe13400…ad2108
0x52a8…60d10x6482…b779BaseBase$0.0001100%daydreams343d ago0xec2ac4…de375a
0x52a8…60d10x6482…b779BaseBase$0.0001100%daydreams343d ago0x0a4f09…071d3e
0x52a8…60d10x6482…b779BaseBase$0.0001100%daydreams343d ago0x5bb223…644efd
0x52a8…60d10x6482…b779BaseBase$0.0001100%daydreams343d ago0x6736a8…433ba5
0x52a8…60d10x6482…b779BaseBase$0.0001100%daydreams343d ago0x747bd5…1aeb2d
0x52a8…60d10x6482…b779BaseBase$0.0001100%daydreams343d ago0x8a4cda…3ca2b4
0x52a8…60d10x6482…b779BaseBase$0.0001100%daydreams343d ago0xb0df99…b15e25

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

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

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: 0x52a8…60d1

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