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%daydreams338d ago0xb1783c…719fc0
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams338d ago0x2c3818…6d93cf
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams338d ago0xe1f166…a7e5ee
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams338d ago0x522fb1…6761f4
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams339d ago0x013b0c…b58b3d
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams339d ago0xd7570d…80ec02
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams339d ago0x6604db…ada4a6
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams339d ago0x1f2fe3…7230ea
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams340d ago0xa31a4e…79bd6e
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams340d ago0xb7774b…e57f9b
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams340d ago0xbeadce…d832e8
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams340d ago0x0dc05e…342c95
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams340d ago0x0b444c…425577
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams340d ago0xa5c098…6b4bc0
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams340d ago0xb2624e…9649ed
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams340d ago0xb5c584…128cfd
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams340d ago0x550787…2598d4
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams340d ago0xa10a78…eed8bd
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams340d ago0xe966e2…f15ea4
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams341d ago0xb39487…84433c
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams341d ago0x453d35…896287
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams341d ago0x2e8ed3…ef1323
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams341d ago0x749a5f…0e673b
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams341d ago0x0e35ab…b1e4bc
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams341d ago0x297df2…319382

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.