AgentReport

0x897a…295f

0x897ae481d1c871d3a0b700fa5bc7ead0cdab295fExplorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
253
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3067.84M Roundhouse has indexed across 1,402,228 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (253)

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

$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 276d ago
    $0.03
    253 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.00253276d 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 253 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams349d ago0x6ded07…5a22aa
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams349d ago0xbd319f…25e99f
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams350d ago0x31ed78…06e103
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams350d ago0xfce85b…50d99c
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams350d ago0x3f4649…74b8ae
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams350d ago0xfb87c8…76e8f3
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams350d ago0xf87b5e…7a551c
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams350d ago0x70446f…dc10a7
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams350d ago0xa615e4…000564
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams351d ago0x17cc48…991b7b
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams351d ago0x095fa7…40288f
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams351d ago0x2b3cee…300349
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams351d ago0xfd0367…ead229
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams351d ago0x0416dc…1e7f73
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams351d ago0xda30fc…bfc768
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams352d ago0x76bf6e…6a38dd
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams352d ago0xdb5ddf…8831e1
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams352d ago0xb5dda5…f9f0f2
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams352d ago0xf88bc2…203d67
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams352d ago0x10b539…289e39
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams352d ago0xaeee69…402149
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams352d ago0x8091f7…47d76e
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams352d ago0x9ec19f…540f4e
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams352d ago0x57f878…ecd03e
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams352d ago0xd66f0c…8c2b28

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

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

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: 0x897a…295f

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