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%daydreams346d ago0x33d542…d4090b
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams346d ago0x442510…d1de14
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams346d ago0xdefc14…7e562b
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams346d ago0x05c9bd…55af46
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams346d ago0x1dea6f…f7ea0c
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams347d ago0x6e3c61…dff5a3
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams347d ago0x5f2ad4…3ee312
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams347d ago0x87666b…d94f6c
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams347d ago0x45b358…1308ba
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams347d ago0x77051d…626c3b
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams347d ago0x4d929f…453889
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams347d ago0xc703d6…aebfc7
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams348d ago0x809d65…74e118
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams348d ago0xd32c59…603798
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams348d ago0xa8e675…d7cc0d
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams348d ago0xec5773…6ab23c
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams348d ago0xe18862…6a531d
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams348d ago0x0c4d4a…525fed
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams348d ago0x9eff68…9ebce8
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams348d ago0xc024a5…31232b
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams348d ago0x12bcf1…a4836d
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams348d ago0x93ee73…e2f6f0
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams348d ago0xba89ca…451269
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams348d ago0xcfc448…738496
0x8adf…aac70x6482…b779BaseBase$0.0001100%daydreams349d ago0xafb47e…18dce2

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.