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 $3068.58M Roundhouse has indexed across 1,402,722 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%daydreams324d ago0x12f68d…8f866d
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams324d ago0x9e5630…b78d29
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams324d ago0x067255…d1653d
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams324d ago0xff80ce…994737
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams325d ago0x606e51…da1710
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams325d ago0x330bc3…20de9c
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams325d ago0xbc941d…0bc5ea
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams325d ago0x65a38b…84c56e
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams325d ago0xd4135a…6b2dc6
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams325d ago0xbecef5…8d6dcf
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams325d ago0xcc3157…5b732d
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams325d ago0xeed417…99cda2
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams325d ago0x6598f8…b8c2a9
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams325d ago0xfe0ebc…294355
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams325d ago0x813253…ae9c12
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams325d ago0x6901c1…0301d5
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams326d ago0x097646…3fcf2b
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams326d ago0xde9ee3…f25ed7
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams326d ago0x8cbcb6…859386
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams326d ago0xc8a145…50f815
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams326d ago0x3c414f…75aac1
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams326d ago0x466d0a…3cf17d
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams326d ago0x77c25c…723782
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams326d ago0x4843db…f4233c
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams327d ago0x592b65…75152d

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.