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%daydreams341d ago0x929abb…55604d
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams341d ago0x91e939…6ef037
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams341d ago0xad968e…d43b73
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams341d ago0xb48078…1a41f9
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams341d ago0xa1132c…af2a69
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams341d ago0x2aafd7…63eb15
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams342d ago0x814861…b0adab
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams342d ago0x88a8e2…67579e
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams342d ago0x37cec1…a1841a
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams342d ago0xa97ea5…8775a8
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams342d ago0xee6301…9e7dca
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams342d ago0x1a1e03…b60c7a
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams342d ago0xae139b…d5252e
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams342d ago0xd4926a…126d1e
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams342d ago0xa31e0a…5d7deb
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams342d ago0x1afe6a…4d7315
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams342d ago0xceaa63…ef6d46
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams343d ago0x22ec82…871422
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams343d ago0x36d71b…d45882
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams343d ago0xfdd308…25256a
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams343d ago0x71c6d5…10c8d9
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams343d ago0x4340d0…df4fce
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams343d ago0x72b235…ac5746
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams343d ago0xec6ae7…ee9d32
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams343d ago0xdf39bf…7571ff

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.