AgentReport

0xca52…5417

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

Paid $0.03 of the $3067.84M Roundhouse has indexed across 1,401,919 wallets — less than 0.0001% of it.

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

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

$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
    260 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.00260276d 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 260 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams324d ago0x6050d4…4a4aea
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams324d ago0x4e0a4f…28e1db
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams324d ago0xeeb3fe…aa64f0
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams324d ago0x90f3f5…a95200
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams324d ago0x59f44e…a6fc0d
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams324d ago0xd932ce…091ee2
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams324d ago0x138b44…472b4a
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams324d ago0x5db661…f8745e
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams324d ago0xb1d696…69b661
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams325d ago0xcab5bb…03d5b3
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams325d ago0xae4968…726aae
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams325d ago0xf0511b…ab51f5
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams325d ago0x4aea06…b32985
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams325d ago0xae9898…c8f178
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams325d ago0xe80b06…b4fcaf
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams325d ago0xae506b…a6c3bd
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams325d ago0xc4cce3…2d597d
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams325d ago0xe7f02b…2e32d8
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams325d ago0xb1caca…86c40e
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams326d ago0x6a2007…1a13d7
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams326d ago0x248bb4…018d24
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams326d ago0x58d678…0038da
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams326d ago0x369f2f…719e4d
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams326d ago0xf0721e…668a8e
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams326d ago0xf78f45…d39220

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

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

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: 0xca52…5417

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