AgentReport

0x8f56…932a

0x8f56bc8fb3047e43908c5744a93474253c44932aExplorer
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 $3068.58M Roundhouse has indexed across 1,402,722 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 277d 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.00264277d 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
0x8f56…932a0x6482…b779BaseBase$0.0001100%daydreams349d ago0x92b275…853080
0x8f56…932a0x6482…b779BaseBase$0.0001100%daydreams349d ago0xd54c74…2a35ae
0x8f56…932a0x6482…b779BaseBase$0.0001100%daydreams349d ago0x633204…810424
0x8f56…932a0x6482…b779BaseBase$0.0001100%daydreams349d ago0xc90720…1c466f
0x8f56…932a0x6482…b779BaseBase$0.0001100%daydreams350d ago0xec1c92…235248
0x8f56…932a0x6482…b779BaseBase$0.0001100%daydreams350d ago0x1b956a…e2b87d
0x8f56…932a0x6482…b779BaseBase$0.0001100%daydreams350d ago0x41374c…686baa
0x8f56…932a0x6482…b779BaseBase$0.0001100%daydreams350d ago0xdb08c7…6a6e46
0x8f56…932a0x6482…b779BaseBase$0.0001100%daydreams350d ago0x760a72…86e989
0x8f56…932a0x6482…b779BaseBase$0.0001100%daydreams350d ago0xcf1657…3a7235
0x8f56…932a0x6482…b779BaseBase$0.0001100%daydreams351d ago0x1e1ff0…b77eba
0x8f56…932a0x6482…b779BaseBase$0.0001100%daydreams351d ago0x0237f5…93735d
0x8f56…932a0x6482…b779BaseBase$0.0001100%daydreams351d ago0xe9d08f…ebbcc5
0x8f56…932a0x6482…b779BaseBase$0.0001100%daydreams351d ago0xd76bb0…390537
0x8f56…932a0x6482…b779BaseBase$0.0001100%daydreams351d ago0x55ef4f…a1a696
0x8f56…932a0x6482…b779BaseBase$0.0001100%daydreams352d ago0xff97ab…eaee4e
0x8f56…932a0x6482…b779BaseBase$0.0001100%daydreams352d ago0xc9bc62…9bcadd
0x8f56…932a0x6482…b779BaseBase$0.0001100%daydreams352d ago0x46df4a…5248ae
0x8f56…932a0x6482…b779BaseBase$0.0001100%daydreams352d ago0x1a93cc…b2d2eb
0x8f56…932a0x6482…b779BaseBase$0.0001100%daydreams352d ago0xbed53b…d28e6a
0x8f56…932a0x6482…b779BaseBase$0.0001100%daydreams352d ago0x024f05…976dcb
0x8f56…932a0x6482…b779BaseBase$0.0001100%daydreams352d ago0xacbbb6…a68a69
0x8f56…932a0x6482…b779BaseBase$0.0001100%daydreams352d ago0xbd6417…22e3f0
0x8f56…932a0x6482…b779BaseBase$0.0001100%daydreams352d ago0x1a1e65…cb50a7
0x8f56…932a0x6482…b779BaseBase$0.0001100%daydreams352d ago0x6bd977…3ed98f

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

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

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: 0x8f56…932a

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