AgentReport

0x8ba6…722c

0x8ba68900235cabce1ded7f2a6ab3fe3de838722cExplorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
264
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3067.84M Roundhouse has indexed across 1,401,919 wallets — less than 0.0001% of it.

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

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

$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
    264 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.00264276d 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 264 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x8ba6…722c0x6482…b779BaseBase$0.0001100%daydreams353d ago0x28fd69…8776b9
0x8ba6…722c0x6482…b779BaseBase$0.0001100%daydreams353d ago0xf9cc46…0f09a0
0x8ba6…722c0x6482…b779BaseBase$0.0001100%daydreams353d ago0x0a86fa…f16cf1
0x8ba6…722c0x6482…b779BaseBase$0.0001100%daydreams354d ago0x880451…5d3b37
0x8ba6…722c0x6482…b779BaseBase$0.0001100%daydreams354d ago0x49f18f…bd2456
0x8ba6…722c0x6482…b779BaseBase$0.0001100%daydreams355d ago0x0d5a8d…b6a26a
0x8ba6…722c0x6482…b779BaseBase$0.0001100%daydreams355d ago0xda2afe…b9aba8
0x8ba6…722c0x6482…b779BaseBase$0.0001100%daydreams355d ago0xa1cb51…eebe42
0x8ba6…722c0x6482…b779BaseBase$0.0001100%daydreams355d ago0x318b76…545a60
0x8ba6…722c0x6482…b779BaseBase$0.0001100%daydreams356d ago0x289512…700c22
0x8ba6…722c0x6482…b779BaseBase$0.0001100%daydreams356d ago0x255058…1d452c
0x8ba6…722c0x6482…b779BaseBase$0.0001100%daydreams357d ago0x724614…7e3135
0x8ba6…722c0x6482…b779BaseBase$0.0001100%daydreams357d ago0x3971a6…5f3269
0x8ba6…722c0x6482…b779BaseBase$0.0001100%daydreams357d ago0x0c6571…d287b1
0x8ba6…722c0x6482…b779BaseBase$0.0001100%daydreams357d ago0xe0f076…3be882
0x8ba6…722c0x6482…b779BaseBase$0.0001100%daydreams357d ago0x6b5850…7af69c
0x8ba6…722c0x6482…b779BaseBase$0.0001100%daydreams357d ago0x29dd7e…4479e5
0x8ba6…722c0x6482…b779BaseBase$0.0001100%daydreams358d ago0x512a68…28a8ec
0x8ba6…722c0x6482…b779BaseBase$0.0001100%daydreams358d ago0xe8c5ea…4fb6f9
0x8ba6…722c0x6482…b779BaseBase$0.0001100%daydreams358d ago0x0c70e0…63ca1d
0x8ba6…722c0x6482…b779BaseBase$0.0001100%daydreams358d ago0x54bbe6…51ad8d
0x8ba6…722c0x6482…b779BaseBase$0.0001100%daydreams358d ago0xa9bdc2…bf68e7
0x8ba6…722c0x6482…b779BaseBase$0.0001100%daydreams359d ago0x27108c…62b457
0x8ba6…722c0x6482…b779BaseBase$0.0001100%daydreams359d ago0xa88de0…04e0bc
0x8ba6…722c0x6482…b779BaseBase$0.0001100%daydreams359d ago0x2e27d2…68ab04

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

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

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: 0x8ba6…722c

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