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,401,091 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%daydreams352d ago0x7a93db…8ef9b3
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams352d ago0x062753…c07a09
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams352d ago0xc255e5…21524f
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams353d ago0xf0dd3d…a45b2d
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams353d ago0x23f763…54ed43
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams353d ago0x856d06…feb79b
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams354d ago0xddb960…c60db3
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams354d ago0xd237c2…3e42fb
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams355d ago0xaa81c9…e6490c
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams355d ago0x826894…da6694
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams355d ago0x36042d…d47f00
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams355d ago0x21b115…076acc
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams356d ago0xc10851…5a2621
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams356d ago0xb49931…9b592e
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams356d ago0x265f01…1637e0
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams356d ago0x0780be…b329de
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams357d ago0xfcaf8c…8f88e2
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams357d ago0xcc944a…f581f8
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams357d ago0xcb437b…b725e2
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams357d ago0xce7048…f392f9
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams358d ago0x3a5c0c…740d17
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams358d ago0x53a2c7…137551
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams358d ago0xd2ba65…339175
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams359d ago0x5a9a1d…fed567
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams359d ago0x03ff08…92c247

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.