AgentReport

0xa472…aa2f

0xa472a196aaf030ad46d1f82c6999e6c8917aaa2fExplorer
Paid out
$0.03
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 $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 (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%$0.032551

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

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.00255276d 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 $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams326d ago0xea8850…79b92a
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams326d ago0x302fbb…6f759c
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams326d ago0x9e806f…49ef72
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams326d ago0x21124f…4e15b6
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams326d ago0xf5f29e…857692
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams326d ago0xabd328…fe450d
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams326d ago0xe6a62d…d6d8e7
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams326d ago0x70d46d…cf8ea3
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams326d ago0x73da8e…09a60a
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams327d ago0x7be88d…dab263
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams327d ago0xa92f0f…0e5222
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams327d ago0xa13702…7dfbfb
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams327d ago0xd6a174…479273
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams327d ago0x19c416…1b1732
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams327d ago0xc23cd9…3692dc
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams328d ago0xdb4edf…005534
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams328d ago0xd60166…db8b42
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams328d ago0x307d9c…f13123
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams335d ago0x7d8a96…13ea8f
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams337d ago0x6fb82b…b7eae1
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams337d ago0x4dd258…660fb8
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams337d ago0x8b84aa…fc94f6
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams337d ago0x2d1911…d5cf89
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams337d ago0x677688…d94d92
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams338d ago0x9d29b9…6547d9

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

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

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: 0xa472…aa2f

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