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.25M Roundhouse has indexed across 1,401,192 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%daydreams341d ago0x4f5adf…b74508
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams341d ago0x88258a…2b953b
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams341d ago0xc4259a…2bb7e1
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams342d ago0xdb1dd4…ff26dd
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams342d ago0x03e3d9…f1c060
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams342d ago0xd87ccb…e3df52
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams342d ago0xf7a916…a0a149
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams342d ago0xb50d72…e0f60f
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams342d ago0xa2604c…22151a
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams342d ago0xeea2bc…151904
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams342d ago0x8b846f…46388c
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams342d ago0xeab9ad…214403
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams342d ago0x8ff174…fe2d9b
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams343d ago0x02cb53…3c63d1
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams343d ago0x40e74b…786049
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams343d ago0x055c16…324845
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams343d ago0x0ba196…00060a
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams343d ago0x6a5be0…dcc6ca
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams343d ago0x098d2a…6de4f9
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams343d ago0xd8b029…d3a210
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams343d ago0x23ca4e…1dacd0
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams343d ago0xb401b5…584f1f
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams343d ago0xd1568a…4a6a4d
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams344d ago0xdd0bc8…36b6b9
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams344d ago0xf2f3df…a48d98

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.