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 $3069.68M Roundhouse has indexed across 1,403,034 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%daydreams342d ago0x199b57…7ed6b8
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams342d ago0x8185e1…30d67d
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams342d ago0x2877a8…32b0cd
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams342d ago0xe24587…3136f6
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams342d ago0xd3192f…a41933
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams342d ago0xba0e3e…247b2d
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams342d ago0xff5ec0…a5f0dd
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams342d ago0xa734ea…e01fc7
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams343d ago0x976afe…2acd92
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams343d ago0xba019d…89e458
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams343d ago0xdc57ad…fe65dd
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams343d ago0xf8cc2d…5449aa
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams343d ago0xac516e…b373a5
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams343d ago0x2b49d3…146015
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams343d ago0x40de36…10f4ca
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams343d ago0xda18d0…36a8d5
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams343d ago0x8648d5…cbd201
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams343d ago0x9b3c0d…d7e31e
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams344d ago0x1557a1…cc7e4f
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams344d ago0x02e24b…f0eb3a
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams344d ago0xb08d5c…9a8a0d
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams344d ago0xe47943…ed179f
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams344d ago0xc6f82d…89c2a1
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams344d ago0xf0a9d4…852bc1
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams344d ago0x4b0382…ff0a31

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.