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,401,091 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%daydreams344d ago0x34c07d…47fb45
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams344d ago0x0d4552…67d62d
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams344d ago0xf3f205…75088c
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams344d ago0xa824ea…4826a4
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams344d ago0x49aca5…e27f39
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams344d ago0x6d3f36…f2dcec
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams345d ago0x75ae1c…57ff1f
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams345d ago0x9aa162…0a2e33
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams345d ago0x2d6a29…064c1e
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams345d ago0xb0d54e…30bd27
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams345d ago0x483eca…c7511c
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams345d ago0x5d7b41…45d920
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams345d ago0xaa7095…715813
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams345d ago0x0d46c7…b461d7
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams345d ago0x6cc0e5…cc903b
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams345d ago0x5c2d52…443d05
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams345d ago0x73dcd2…d9bc6e
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams345d ago0x978475…5a1e32
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams346d ago0xa79533…d1e752
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams346d ago0x76a4a0…25e1bb
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams346d ago0x7756d6…1af127
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams346d ago0x1a5c90…195075
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams346d ago0x1010df…911ba6
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams346d ago0x542b55…9ae8b6
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams346d ago0x1450ae…10b23c

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.