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%daydreams327d ago0x19bfb2…a014d9
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams327d ago0x907c87…981f7e
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams327d ago0x32e0a0…87851c
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams327d ago0x63e4f9…6eeb65
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams327d ago0x43ca7f…77a45b
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams327d ago0xca13c6…527af4
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams327d ago0xc34ade…e8dc48
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams327d ago0xef64a6…a4dac0
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams328d ago0xd1c177…3b799a
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams328d ago0xc8b97f…47ab1e
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams328d ago0xaaa43f…d85566
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams328d ago0x2c2ffa…e20a6e
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams328d ago0x7e3bc6…f1d38a
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams336d ago0xff659f…619004
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams337d ago0x22ce04…6c8409
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams337d ago0x0e0a15…efa4c2
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams337d ago0xb6d316…f154a2
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams337d ago0xec3049…61eb2e
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams338d ago0x582fb4…eb7bac
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams338d ago0x7ee079…9e24a6
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams338d ago0xcf5c13…f5d751
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams338d ago0xc022fa…fa0d6a
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams338d ago0xca3dc8…759cff
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams338d ago0x95d9d3…168271
0xa4d2…24b00x6482…b779BaseBase$0.0001100%daydreams338d ago0x9f8ba2…cea63b

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.