AgentReport

0x0f32…cd89

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

Paid $0.03 of the $3066.54M Roundhouse has indexed across 1,400,255 wallets — less than 0.0001% of it.

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

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

$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
    263 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.00263276d 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 263 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams343d ago0xd006c3…edef99
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams343d ago0x0e8d74…09f506
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams343d ago0x89c5e3…a69a99
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams343d ago0xcc7c66…deb454
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams343d ago0x646394…22e5d7
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams343d ago0xb541dc…4d15d2
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams343d ago0x1ea2b7…841bfb
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams343d ago0xbc49fa…1643e3
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams343d ago0x07bf82…3a1616
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams344d ago0x441857…e89c2f
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams344d ago0xc3c38f…201050
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams344d ago0xecc5da…33678e
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams344d ago0xfd4546…994879
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams344d ago0x3dbb31…757d1e
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams344d ago0xe375c8…47fff8
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams344d ago0x04c193…bd9daf
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams344d ago0x99cb4a…44f93d
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams344d ago0xf32b03…e5e500
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams344d ago0x36755c…43c677
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams344d ago0x293db4…fdab00
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams345d ago0xd6f58a…3e9555
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams345d ago0x052d15…a6a4c9
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams345d ago0x5ec07f…0f7764
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams345d ago0x090b7a…ae85ef
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams345d ago0x37b1d8…b7c42f

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

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

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: 0x0f32…cd89

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