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%daydreams324d ago0x663902…aa2f84
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams324d ago0x3ee96b…10e068
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams324d ago0xf6cc89…128a7f
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams324d ago0x280f03…e29d60
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams324d ago0x140aaa…05e87b
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams324d ago0x23ef2f…de2dbd
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams324d ago0x1fe0b9…f70053
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams324d ago0x6cace8…90948f
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams324d ago0x514042…04daf5
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams325d ago0xb12b70…bc2473
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams325d ago0xb9ee6d…57f362
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams325d ago0x6b3310…7b7456
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams325d ago0x6284df…dfc2bd
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams325d ago0x9f41f9…8c55bb
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams325d ago0xea357c…c70873
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams325d ago0xf9742c…092c49
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams325d ago0x87db78…1a953d
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams325d ago0xdab4f1…7f43ee
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams325d ago0xf3fe95…874bfa
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams326d ago0xef0ebd…b25f98
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams326d ago0x2e62ec…a744ad
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams326d ago0xf35a1e…766842
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams326d ago0x8ca4b0…85a822
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams326d ago0x82b54e…5e5bfc
0xaa8a…a1800x6482…b779BaseBase$0.0001100%daydreams326d ago0xe69c4c…b43e87

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.