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,843 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%daydreams343d ago0xf0c24c…bf68ae
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams343d ago0xead2c6…2cfac5
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams343d ago0x7cd701…9a3263
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams343d ago0xf8d3fd…36d3cd
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams343d ago0xd58866…66df04
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams344d ago0xad6695…82dd0b
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams344d ago0x0f937a…c606e6
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams344d ago0x33fb08…4559fc
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams344d ago0x567e4f…ed9057
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams344d ago0xfe05ae…8cc992
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams344d ago0x819334…42f578
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams344d ago0x075e63…b3577c
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams344d ago0x8adbe9…44112d
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams344d ago0xa2e080…7f9dc8
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams344d ago0x0e1286…11c1ee
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams344d ago0x296a1f…25eb7a
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams344d ago0x51e44f…5d83ec
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams345d ago0x2b5cbe…e0b460
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams345d ago0x40fd10…bdf2c1
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams345d ago0x2d5c03…5398ca
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams345d ago0xf64f58…dfe0c4
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams345d ago0xabdc06…285509
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams345d ago0x5e97db…0cf0b8
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams345d ago0x704904…6ccb72
0xd88d…ca0f0x6482…b779BaseBase$0.0001100%daydreams345d ago0xbf2451…e24b6f

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.