AgentReport

0xa4d2…24b0

0xa4d2a7b94744ce4d3f9e804298d4d59d24c524b0Explorer
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 $3070.29M Roundhouse has indexed across 1,403,290 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 277d 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.00263277d 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
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams347d ago0x90a293…bd75c4
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams347d ago0xe571f2…8934cd
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams347d ago0x8d9b4d…cf87e2
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams347d ago0xd8f8c7…166b1c
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams347d ago0xf3624d…1ba9b9
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams347d ago0x7fe89c…ff280b
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams347d ago0x75b3d2…ee06d4
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams348d ago0xb7f292…a759ba
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams348d ago0xc3bbe5…5979a6
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams348d ago0x88751d…f28e5e
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams348d ago0xb6c37c…9dc916
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams348d ago0xc261a1…c05ca3
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams348d ago0xd42023…07a2d0
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams348d ago0x251eb2…b0c352
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams348d ago0x15f23d…7af42b
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams348d ago0xe55143…34e6d7
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams348d ago0xd6ae0a…7e3b1d
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams348d ago0x4be647…d805b5
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams349d ago0x48c8e4…624a2b
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams349d ago0xe59f60…b724d9
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams349d ago0xbcc72f…07aa12
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams349d ago0x669c0d…8cdaf5
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams349d ago0x1fb700…d41452
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams349d ago0x2e0870…ee2825
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams349d ago0x9d4a70…bf033e

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

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

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: 0xa4d2…24b0

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