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 $3067.00M Roundhouse has indexed across 1,400,982 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%daydreams343d ago0xd932f0…ba265b
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams343d ago0xf29a0a…c3da9e
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams344d ago0x3cb756…de289c
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams344d ago0xd2ab32…484545
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams344d ago0x72dcfc…7aa90a
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams344d ago0xee7e40…075d13
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams344d ago0x1930b2…32ac65
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams344d ago0x03057f…706c08
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams344d ago0x523abd…f0a943
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams344d ago0x29a106…33a24b
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams344d ago0x98aa90…a8794c
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams344d ago0x8c5402…7862d3
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams344d ago0xa8d01f…6ef2d9
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams345d ago0x10dd66…55beb2
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams345d ago0x509732…730734
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams345d ago0x983c74…0d468e
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams345d ago0xbf4477…9bdd66
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams345d ago0x049ae6…f2bb5b
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams345d ago0x19c9d7…5e7865
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams345d ago0xb4effa…e98e1c
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams345d ago0x8402f4…a18e88
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams345d ago0x49ecf1…11d6c2
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams345d ago0x483ae6…4b04ac
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams345d ago0x3e32b3…866fb6
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams346d ago0x8dc3af…277a70

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.