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,843 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%daydreams337d ago0xa9522d…68dd8a
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams337d ago0x7edcbe…8ccbc2
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams337d ago0x4af14a…afef48
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams338d ago0xb38b22…45703a
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams338d ago0xac61f8…5f12a0
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams338d ago0x57db12…be51b7
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams339d ago0xdf158d…bf8fbb
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams339d ago0x7a3d90…e4d2d8
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams339d ago0xdf9d93…0b5716
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams339d ago0x99f43d…98f88f
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams339d ago0xe91883…78a204
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams340d ago0x654559…cf75ba
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams340d ago0xd842f1…84c4bd
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams340d ago0x17d535…e4dd09
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams340d ago0xc66d8c…25c2f0
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams340d ago0xc37faa…af8f45
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams340d ago0x2949ba…1a95bc
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams340d ago0xce647c…b8f04f
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams340d ago0xc3797a…c8c2a0
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams340d ago0x285537…fbdedf
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams340d ago0xab86dc…53d6d7
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams341d ago0x840255…52c5df
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams341d ago0xa2e719…4033ba
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams341d ago0x6f8217…c8bbb0
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams341d ago0xc7b713…0dd638

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.