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%daydreams346d ago0xefb03e…cdd05e
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams346d ago0x3f48cd…272067
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams346d ago0x0ba98c…209ca8
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams347d ago0x659350…09b1bf
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams347d ago0x41dab5…85d43f
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams347d ago0xc81622…1ccf26
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams347d ago0x44d706…50f0df
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams347d ago0x28c940…803e4e
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams347d ago0x29ce14…07324d
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams348d ago0x249eef…4b0c4b
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams348d ago0x7863b0…c48cdd
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams348d ago0x7a7020…1ab7f7
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams348d ago0xa90eeb…ef37e2
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams348d ago0x13c72b…f9f157
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams348d ago0x168fcf…1ca401
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams348d ago0xcccf66…b9e5c4
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams348d ago0xbafc57…c021b3
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams348d ago0x3c5b6f…9c5e93
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams348d ago0x3b67ea…b583a3
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams348d ago0x3ea65b…44c214
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams348d ago0xb81498…be0d50
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams349d ago0x168385…24233d
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams349d ago0x931874…dee7fe
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams349d ago0xe1864c…ec35c3
0x897a…295f0x6482…b779BaseBase$0.0001100%daydreams349d ago0x0c86fc…0dde52

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.