AgentReport

0xaa8a…a180

0xaa8acc7c3c5e94c45443abb6484e097c092ea180Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
261
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,400,982 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (261)

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.032611

$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
    261 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.00261276d 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 261 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams326d ago0x66374f…01e2ae
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams326d ago0x9365dd…854e86
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams326d ago0xc9fa10…9bed89
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams326d ago0x57c5a4…841f91
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams327d ago0xe5b98f…8a9009
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams327d ago0x391406…71c95a
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams327d ago0xe6dba7…e21574
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams327d ago0x077e23…b0da3f
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams327d ago0xdf7c36…7b046c
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams327d ago0x6cc97b…f6f71b
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams328d ago0x5bedf9…92f588
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams328d ago0xbbd879…95dd87
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams335d ago0x373192…f203c9
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams337d ago0x686fc8…492e9a
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams337d ago0x63de9d…367e0d
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams337d ago0xb2a819…cb53ef
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams337d ago0x151b8c…f0035f
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams337d ago0xff97c0…69e9fa
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams337d ago0xc280b3…019f6d
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams337d ago0xa97a2f…772184
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams338d ago0xb31100…7e9f90
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams338d ago0xd5489d…34cf68
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams338d ago0xe5e70a…65aa7d
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams338d ago0x0cf9c9…747377
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams339d ago0x2920a8…7f01e8

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 0xaa8a…a180 has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0xaa8acc7c3c5e94c45443abb6484e097c092ea180

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: 0xaa8a…a180

curl -s 'https://api.roundhouseai.io/v0/agents/0xaa8acc7c3c5e94c45443abb6484e097c092ea180'
curl -s 'https://api.roundhouseai.io/v0/entities/0xaa8acc7c3c5e94c45443abb6484e097c092ea180/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.