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%daydreams326d ago0x81226f…3b3cd2
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams326d ago0x36077a…884bd3
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams326d ago0xdd8b94…3c1d39
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams327d ago0x3e7486…99fc3c
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams327d ago0x2379c7…c287ae
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams327d ago0x96a336…adb8a3
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams327d ago0x73ece2…c72327
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams327d ago0x81bd7b…803473
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams327d ago0x09629e…8d6e5f
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams327d ago0xc6ad33…7ee420
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams328d ago0xb917df…e0093a
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams328d ago0xb2c0ae…1958f4
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams328d ago0x39fa29…8caac5
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams328d ago0xff16fc…c587d4
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams328d ago0xa2c93e…f9c130
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams336d ago0x7423f9…296fe4
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams337d ago0xf14249…21749f
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams337d ago0x3e9727…7b426a
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams337d ago0x044e66…f64fbb
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams337d ago0xf3cb96…241f4e
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams338d ago0x33997f…e46f0e
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams338d ago0x91174d…2f8f6c
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams338d ago0x2ba6e6…1f5490
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams338d ago0xb1e7b6…ec632e
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams338d ago0xb51cbf…c2942b

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.