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.43M Roundhouse has indexed across 1,401,575 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%daydreams349d ago0x935c7a…a05be4
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams349d ago0x7bffcb…9bb02e
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams349d ago0x7cebb3…6a1442
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams349d ago0x4f425e…e70487
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams350d ago0xa86a97…98e3c5
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams350d ago0x7bfc37…44f620
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams350d ago0xa874e3…bb5149
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams351d ago0xf07fa6…ff5c23
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams351d ago0x5a75e2…d3c7b2
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams351d ago0x798741…2c6f9d
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams351d ago0x009c53…cfd3cc
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams351d ago0xda638a…b52ca2
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams351d ago0x9a2b81…250640
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams352d ago0xd321a9…dfce64
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams352d ago0xd5f065…5b2662
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams352d ago0xdbe694…e89006
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams352d ago0x60a850…c3f594
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams352d ago0x545d4a…4d78f0
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams352d ago0xfcc8ce…aad6e6
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams352d ago0xfeb6a2…45ab92
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams352d ago0xd3e70a…83b399
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams352d ago0x7ba004…380d64
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams353d ago0xb43527…f2d540
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams353d ago0xe69000…969616
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams353d ago0x6ff1f4…610c17

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.