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 $3068.58M Roundhouse has indexed across 1,402,396 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%daydreams344d ago0x3a7166…9d5a94
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams344d ago0x980d15…341823
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams344d ago0xb69985…58e477
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams344d ago0xb6e79a…59dea2
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams344d ago0x1fc7f0…9d0548
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams344d ago0x3eecf4…9d2463
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams344d ago0xf01b39…54eb69
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams345d ago0x9f2dd3…f460e2
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams345d ago0xebd244…351997
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams345d ago0x876d9c…21bb86
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams345d ago0xe9eab3…f96228
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams345d ago0xd4a3e7…89ee3e
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams345d ago0x16261e…b6840c
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams345d ago0xe07b2e…4a29e1
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams345d ago0x454c16…06bf68
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams345d ago0xfa6955…d608f4
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams345d ago0xa2838e…8cb0c4
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams345d ago0xaacfff…17115a
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams346d ago0x1a9633…b99b96
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams346d ago0x9f1f08…01a196
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams346d ago0xeab187…79d1ba
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams346d ago0x92c65a…c33389
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams346d ago0x110900…f10071
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams346d ago0xf4e123…b9f074
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams346d ago0xc638fe…455f06

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.