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.25M Roundhouse has indexed across 1,401,192 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%daydreams350d ago0x4df40e…48bece
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams350d ago0x7f7481…90ada1
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams350d ago0x3573f0…8a3869
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams350d ago0x573526…d64747
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams350d ago0x9ba9df…134ca6
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams351d ago0x98e8c2…19a091
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams351d ago0x1cd7f7…f1db74
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams351d ago0xf4dbc2…49776b
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams351d ago0x44eec4…52222e
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams351d ago0x98fd83…156c99
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams351d ago0x1c92bb…486842
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams352d ago0xcb14dc…0bd5dc
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams352d ago0xb91b21…65c550
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams352d ago0xa23eca…3e3d90
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams352d ago0x93bb7d…a9a29c
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams352d ago0x240fc7…eb69b9
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams352d ago0xeaa442…72b228
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams352d ago0xcaf3e8…5bd18c
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams352d ago0x35c654…53241f
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams352d ago0x362286…7711f2
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams353d ago0x80e96a…779a04
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams353d ago0x55addd…553ed6
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams353d ago0x4b8dc1…e5b0ff
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams353d ago0x09752d…513e86
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams353d ago0x4f9701…281aa7

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.