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%daydreams323d ago0xef8e77…348200
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams323d ago0x317d6c…539fdc
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams323d ago0x496f27…f7c74c
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams323d ago0x344667…ad7103
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams324d ago0xb58cec…ccbb71
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams324d ago0x9e22fc…353965
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams324d ago0xa19cb3…e08303
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams324d ago0xbc5e0a…69d721
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams324d ago0xc8dfcd…9b88b1
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams324d ago0x5b5ffe…d51dad
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams324d ago0xc1bd8b…4e7357
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams324d ago0x0aeb99…b5e226
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams324d ago0x99a3f1…0f51c6
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams324d ago0x265d8f…549666
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams325d ago0xe47cab…045ad6
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams325d ago0x8e2821…fb9f77
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams325d ago0x9a6c09…7a05b8
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams325d ago0x2028a1…a35fdf
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams325d ago0x627fa9…418d85
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams325d ago0x5be69a…bb5753
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams325d ago0x4ee1b5…34fd50
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams325d ago0x8367e3…0aa0a1
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams325d ago0x8d6527…a78c52
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams325d ago0x5b81af…03f516
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams326d ago0xcecce9…1be782

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.