AgentReport

0x7288…cc60

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

Paid $0.03 of the $3066.54M Roundhouse has indexed across 1,400,689 wallets — less than 0.0001% of it.

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

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

$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
    259 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.00259276d 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 259 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams325d ago0x2e7f07…e069fb
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams325d ago0x0d8512…914d10
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams325d ago0xa5fe2e…aff958
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams325d ago0x22e5f9…80efb1
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams325d ago0x73d83a…03848b
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams326d ago0x77f4f5…1abaef
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams326d ago0x9263da…ceef56
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams326d ago0x35596f…808bed
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams326d ago0x1b8ed7…0c76f0
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams326d ago0x71a2c6…73d552
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams326d ago0xf28090…514149
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams326d ago0x79d2db…eff40b
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams326d ago0xe2301e…8a0ab6
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams327d ago0x13c6de…131b0b
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams327d ago0xb398ac…de4f11
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams327d ago0xf2f196…f951c3
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams327d ago0x9d1406…75d392
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams327d ago0xbb1c6e…250424
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams327d ago0xe85b65…64e704
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams328d ago0xa96ac8…643bda
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams328d ago0x7ee91f…88143a
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams335d ago0xfe433e…dd468f
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams337d ago0x778ac8…4d7ca6
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams337d ago0x835722…f05ac4
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams337d ago0x4ecbbb…d8cb42

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

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

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: 0x7288…cc60

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