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%daydreams353d ago0xdf923a…56ff28
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams353d ago0xd0dd08…ccf852
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams354d ago0x4116d8…f928f5
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams354d ago0x1c2c4a…f21c31
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams355d ago0x82872d…f0bbf7
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams355d ago0xdbca90…2f394f
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams355d ago0x784ad1…290617
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams356d ago0x7fd57d…0fadc2
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams356d ago0x9043f6…c8e960
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams356d ago0x289078…8547e2
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams356d ago0xd1abcb…ea8476
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams357d ago0x0ffade…857865
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams357d ago0x129a41…e50069
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams357d ago0x400e94…aecb56
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams357d ago0xb26c42…2ee380
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams358d ago0x5454f4…0dafd3
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams358d ago0xa7ddb6…7547a0
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams359d ago0xe9883d…493d80
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams359d ago0xccf1ac…872fd9
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams359d ago0x5a5fc9…1ab9e1
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams359d ago0x8e3237…ba7fd9
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams359d ago0x42a1c2…ee4e8b
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams360d ago0xcd3e9c…d69d92
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams360d ago0x81f3a5…c0afb3
0xa472…aa2f0x6482…b779BaseBase$0.0001100%daydreams361d ago0xa28891…2f5600

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.