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 $3066.54M Roundhouse has indexed across 1,400,689 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%daydreams337d ago0x81714b…474679
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams337d ago0xb04e71…1b2e41
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams337d ago0xac120e…554928
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams337d ago0x349001…8fa952
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams337d ago0x5b2f90…396a28
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams337d ago0x66c84a…ab3d83
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams338d ago0x7e58f8…cc50f3
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams338d ago0x00404a…a5ed48
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams338d ago0x914097…4db3e2
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams338d ago0x25b415…245f1d
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams339d ago0x38ae7b…7d024e
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams339d ago0xb38e7b…34b0b7
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams339d ago0x86847b…dfd532
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams339d ago0x0dcedd…7cd91c
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams339d ago0xfa6b5e…7f3688
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams340d ago0x2430a7…a50095
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams340d ago0x002fe0…dcef64
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams340d ago0xc81a77…f5f1a8
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams340d ago0xf43cf6…0da01d
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams340d ago0xd70f2e…9f6b14
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams340d ago0x406219…b43d04
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams340d ago0x8039a0…fae980
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams340d ago0xe7453f…1ec13d
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams340d ago0x681bba…16823b
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams340d ago0x98464f…1cc8b5

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.