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 $3068.58M Roundhouse has indexed across 1,402,396 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%daydreams346d ago0x203144…00f1a6
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams346d ago0xa3559e…84c689
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams346d ago0x70df56…b6c393
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams347d ago0xfb853b…aa6f0a
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams347d ago0x782d49…dd940a
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams347d ago0x12946b…e13254
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams347d ago0xb62e52…21cc57
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams347d ago0x29e666…daa3dd
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams347d ago0xee493f…12453d
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams347d ago0xfcff80…fb693a
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams348d ago0xac4750…ce46eb
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams348d ago0xda7f7a…ae7638
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams348d ago0x35edc5…e0ac5a
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams348d ago0xc5d7cd…a5397e
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams348d ago0xdef9e0…ce9e41
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams348d ago0xcd8002…872b66
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams348d ago0xb15ab8…781e2e
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams348d ago0xac4bbc…171aba
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams348d ago0x073069…3d1628
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams348d ago0xaffaf9…320ce2
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams348d ago0x5c4d87…f70e71
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams349d ago0x684dd7…310c09
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams349d ago0x28eb67…821d82
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams349d ago0xebfd99…b593e7
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams349d ago0x890aff…c2083d

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.