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%daydreams338d ago0x16d9c6…a453ab
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams338d ago0xc22b56…0e244b
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams338d ago0x7eca3a…a49050
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams340d ago0x4de3a6…f14372
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams340d ago0xe6cea3…313dfb
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams340d ago0x5f870f…01398e
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams340d ago0x43a357…258607
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams340d ago0x7f1be5…b9fd32
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams340d ago0xf090b4…40522a
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams340d ago0x3a825e…050539
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams340d ago0x2b71b6…c880b0
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams340d ago0xe6712d…e7e81d
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams340d ago0xa5548a…87072e
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams340d ago0xf6198f…8d1818
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams341d ago0x8b6d7e…46837b
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams341d ago0x15419b…5b0550
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams341d ago0xa561b7…a66941
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams341d ago0x3fe31e…5fdd8a
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams341d ago0x5bcf9a…a3e4a4
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams341d ago0x1b572a…c175ba
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams341d ago0x5ea42c…f627e1
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams341d ago0xd596cc…d31f0b
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams341d ago0xe9752a…fa05a7
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams341d ago0x484aad…9c52ce
0x2a25…66a30x6482…b779BaseBase$0.0001100%daydreams342d ago0x738ec9…fb52ff

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.