AgentReport

0xd88d…ca0f

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

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

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

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

$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
    258 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.00258276d 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 258 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams348d ago0x5722ac…2f2d64
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams348d ago0x9de63e…4f05d7
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams348d ago0x802556…502388
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams348d ago0x21a0c9…068c0b
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams348d ago0xcc1490…c11c1a
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams349d ago0xa006ab…1423c6
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams349d ago0x7c3106…175bc6
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams349d ago0x9c1901…fa6f28
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams350d ago0x68b691…81acbc
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams350d ago0x255ead…751992
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams350d ago0x66c38d…a5ace2
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams350d ago0xaace46…9d26a2
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams350d ago0x55129b…4a5f50
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams351d ago0xcd1d66…589bce
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams351d ago0xf9872a…182fc0
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams351d ago0xb79994…03a859
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams351d ago0xf61ebb…f9a2bc
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams351d ago0xa6a52b…aab6ea
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams351d ago0x22aeb3…207b6a
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams351d ago0x58e3fc…44e476
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams352d ago0xe7aa41…cd0f3d
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams352d ago0x22c2a9…e55518
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams352d ago0x7958f6…f29c4d
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams352d ago0x5c1028…8e62f7
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams352d ago0x89f0b1…dbb299

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

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

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: 0xd88d…ca0f

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