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.43M Roundhouse has indexed across 1,401,367 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%daydreams354d ago0x240314…b7434b
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams354d ago0x53ca6f…d26ed2
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams354d ago0x2e89ff…3295ff
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams354d ago0x1e1008…b6d409
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams355d ago0x46eae4…2a7796
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams355d ago0xaff61a…e3ad33
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams355d ago0x657b2c…403047
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams355d ago0x7da37d…c2391b
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams355d ago0xd754c9…8d9cb5
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams355d ago0x14054f…79094b
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams356d ago0x2e5e65…cf09df
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams356d ago0x12b9b8…2ff39e
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams356d ago0x3087dd…11ef5c
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams356d ago0x0d95f4…5e4e41
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams357d ago0x71de78…81f8eb
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams357d ago0xcdf862…1c0e14
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams357d ago0x53b335…7232e7
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams357d ago0xc612f0…1fb76e
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams357d ago0x1df51b…f9b983
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams357d ago0x67d745…51283e
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams358d ago0xcab261…6e0c7a
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams358d ago0x54c807…d9f95e
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams358d ago0x970eaf…1a1409
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams358d ago0x0ac993…2452c7
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams359d ago0x39548d…eb6d8f

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.