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%daydreams344d ago0x665eb8…b9e819
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams344d ago0xb7a90e…892408
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams344d ago0xd10e53…9e7dbc
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams345d ago0x7876f6…eb5561
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams345d ago0xba96c3…ffd698
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams345d ago0x0cdab7…760052
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams345d ago0x8853e3…3f87cb
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams345d ago0x0be2d3…b4c130
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams345d ago0x7bbcb4…e70c69
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams345d ago0x2f3031…04b9a3
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams345d ago0x7ab729…2c02c5
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams345d ago0x807f8c…da60c4
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams345d ago0x831656…d1b3a3
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams345d ago0xa06d3c…b09121
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams345d ago0x5e6bd7…188d30
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams346d ago0xba573a…891dc9
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams346d ago0xec3a79…ce48ac
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams346d ago0xe92124…3c2496
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams346d ago0x6021d6…d47b03
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams346d ago0x0cab75…afb536
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams346d ago0xb0a97d…1d9b9f
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams346d ago0xdee4fd…398a46
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams346d ago0x307061…cf06ab
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams346d ago0x57d433…1752c6
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams346d ago0x6dbbdf…25a481

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.