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%daydreams346d ago0x3d5c58…d09526
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams346d ago0xf22b96…1b4f5f
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams346d ago0x2f46b9…bf6037
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams346d ago0x935aba…6a4a15
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams346d ago0x1c9a8e…02a73b
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams346d ago0xb2216f…9446aa
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams346d ago0x164849…dac65d
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams346d ago0x315a21…d35b1e
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams346d ago0xcbcc90…3836d5
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams346d ago0x47c0b0…0ea7c9
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams347d ago0xdc268e…55c091
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams347d ago0x6bc979…e257a2
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams347d ago0x83ade8…56b556
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams347d ago0x538de3…bf163d
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams347d ago0xd1df11…b73094
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams347d ago0x136e7a…091c88
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams348d ago0xc60634…6208d7
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams348d ago0x68c17b…7dbf98
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams348d ago0xd7f269…4c9830
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams348d ago0x17c145…d316c0
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams348d ago0x651466…8c9065
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams348d ago0xb01a9c…ea1730
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams348d ago0xfe27a2…1336d4
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams348d ago0x607c10…99c147
0x7288…cc600x6482…b779BaseBase$0.0001100%daydreams348d ago0x6828bd…86a769

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.