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 $3069.68M Roundhouse has indexed across 1,403,034 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%daydreams341d ago0x47122f…72cbd3
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams341d ago0x49c6bd…2a5900
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams342d ago0xd4ab91…64d08b
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams342d ago0xbf67d8…ce39db
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams342d ago0xa8d726…199a08
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams342d ago0x06c000…2ae7ee
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams342d ago0xbcc4f7…f3fc83
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams342d ago0x6f8e72…4fe8f6
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams342d ago0x78f673…5c7dce
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams342d ago0xcf1e57…bebb67
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams342d ago0xf732c3…0bc93c
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams342d ago0x12a74e…3b38af
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams342d ago0x23df6c…b53864
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams343d ago0x78a569…dc4e03
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams343d ago0x95aae6…a0fd02
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams343d ago0xceb3fa…353fed
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams343d ago0x31f023…8b856b
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams343d ago0x52b577…7ab81f
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams343d ago0x3f276a…a70ac8
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams343d ago0x1130de…be3f19
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams343d ago0x55b669…088f40
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams343d ago0x7af1a7…b005dd
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams343d ago0x6789d4…f56aac
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams343d ago0xdc29c4…63f6ca
0x2204…05020x6482…b779BaseBase$0.0001100%daydreams343d ago0xab4e80…2d877d

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.