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%daydreams346d ago0x72cc19…3fb7bc
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams346d ago0xfea755…6faa44
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams346d ago0xfef9f7…ce149f
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams347d ago0x68e710…a554a2
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams347d ago0xc0ba9d…7a6511
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams347d ago0xc304ce…5ba2d8
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams347d ago0xa82319…bf7ee9
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams347d ago0xf9a232…08a0c0
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams348d ago0xa0f4ca…b26e46
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams348d ago0xeb2a78…486953
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams348d ago0xb74258…f32561
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams348d ago0xcbfc52…1bbf61
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams348d ago0xdc7e46…b300b7
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams348d ago0x80598f…3be15b
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams348d ago0x44e080…5d5262
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams348d ago0x1d4bd0…f8e1a6
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams348d ago0x3ed5b1…79a4c8
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams348d ago0xd99cc9…c852a1
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams348d ago0x1c0646…e4e0a7
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams349d ago0x5748ef…72d8bf
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams349d ago0x22674f…f94ad0
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams349d ago0xfaafd1…af0128
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams349d ago0xce6295…6804b7
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams349d ago0xdefa6c…f05da3
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams350d ago0xf1884d…54799e

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.