AgentReport

0x2204…0502

0x2204f5bcabeb4fd7a52741fc802d1a1937ec0502Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
273
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3068.58M Roundhouse has indexed across 1,402,722 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (273)

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.032731

$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 277d ago
    $0.03
    273 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.00273277d 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 273 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams326d ago0xf188ed…90e85d
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams326d ago0x7cc401…4b01fc
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams326d ago0x243498…a97515
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams326d ago0x65d644…a21bf3
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams327d ago0xb14a56…36927f
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams327d ago0x4c2949…45423b
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams327d ago0x068b31…314998
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams327d ago0x9d7574…4984ea
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams327d ago0x7f7ead…1ead1f
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams327d ago0x7373d9…b6bd8c
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams327d ago0x03544e…5a6ada
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams327d ago0xa37413…4110a7
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams327d ago0xb19794…1d3239
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams328d ago0x9740df…0c60e6
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams328d ago0xe518cb…873707
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams328d ago0x58f9e5…125dda
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams328d ago0x3009a6…15b4ab
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams328d ago0x3b36fb…fd68d7
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams328d ago0x47893c…ef7d1f
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams336d ago0x9ff008…2dbd38
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams337d ago0x73a424…7fe5ae
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams337d ago0x61698e…c85f11
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams337d ago0xcab069…b4d720
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams338d ago0x7168c1…1c90d4
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams338d ago0xd10320…bb1f21

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 0x2204…0502 has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0x2204f5bcabeb4fd7a52741fc802d1a1937ec0502

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: 0x2204…0502

curl -s 'https://api.roundhouseai.io/v0/agents/0x2204f5bcabeb4fd7a52741fc802d1a1937ec0502'
curl -s 'https://api.roundhouseai.io/v0/entities/0x2204f5bcabeb4fd7a52741fc802d1a1937ec0502/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.