AgentReport

0x2a25…66a3

0x2a25f7c8849f814f5290d82570dae89a98bd66a3Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
262
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 (262)

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.032621

$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
    262 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.00262277d 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 262 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams342d ago0xcd713b…ca5faa
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams342d ago0xde99ab…a25706
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams342d ago0x3e0136…59ebc0
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams342d ago0xf89c88…b9ee89
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams342d ago0x002c01…4aa388
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams342d ago0x735e80…371508
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams342d ago0xc5a238…dea106
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams342d ago0x52a266…dc13ff
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams342d ago0x9bda9b…f05cb5
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams343d ago0x41866b…b0defa
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams343d ago0x27d750…735cff
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams343d ago0x0b5302…bad138
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams343d ago0x657d40…940613
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams343d ago0x622c58…acb58b
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams343d ago0xa96ce2…c7ec39
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams343d ago0xab54ae…80065b
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams343d ago0x1cb5ca…09c00f
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams343d ago0x935117…d520be
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams343d ago0x06bf6e…44f5f3
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams343d ago0xbc6598…ba9e37
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams344d ago0x812cc2…e9047f
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams344d ago0xd81819…527db5
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams344d ago0x82f855…41d4c0
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams344d ago0x7c8ada…40c656
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams344d ago0x9d7d31…aad7da

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

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

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: 0x2a25…66a3

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