AgentReport

0x8adf…aac7

0x8adf7c1432fe71eaeb82f407288df30a8030aac7Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
250
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,742 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (250)

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.022501

$0.02 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.02
    250 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.02$0.00250276d 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 250 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams326d ago0x66d784…7ed0c9
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams326d ago0x2a356b…214105
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams326d ago0xb653d5…f428b7
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams326d ago0x95c9bd…2da67c
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams326d ago0x1c9a83…03e9b8
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams326d ago0xbd08ad…325b62
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams326d ago0x2f4222…84c8d9
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams326d ago0x95f4b2…2e0973
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams327d ago0x8dab22…7281ca
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams327d ago0x70dc1b…ab2c55
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams327d ago0x05c7b0…0cdd29
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams327d ago0xf8a6d7…708f25
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams327d ago0x3814ee…2b82f6
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams327d ago0xacf616…4e0416
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams327d ago0xadb90f…73f99b
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams327d ago0x54310f…cccc2b
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams327d ago0xd0c449…5135ed
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams328d ago0xd6a2d6…121674
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams335d ago0xe6e970…2be495
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams337d ago0xdecdaa…9f9020
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams337d ago0xad6775…f41ff9
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams337d ago0xaaa0d8…e2a593
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams338d ago0x2b7bc0…21065b
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams338d ago0x9196e3…7bf153
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams338d ago0x2a15f1…c349f8

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 0x8adf…aac7 has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0x8adf7c1432fe71eaeb82f407288df30a8030aac7

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: 0x8adf…aac7

curl -s 'https://api.roundhouseai.io/v0/agents/0x8adf7c1432fe71eaeb82f407288df30a8030aac7'
curl -s 'https://api.roundhouseai.io/v0/entities/0x8adf7c1432fe71eaeb82f407288df30a8030aac7/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.