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%daydreams338d ago0xb35505…c70c26
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams338d ago0x1fdf62…4b0c2c
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams339d ago0xe3cfec…4b654d
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams339d ago0x33c842…74b871
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams340d ago0x346b2f…f2d5ac
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams340d ago0xfbf07f…d294b4
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams340d ago0xabf929…ff98b9
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams340d ago0xb3ac9c…f6528b
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams340d ago0x1aca20…6a6c25
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams340d ago0xadd5c5…348da4
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams340d ago0x3fa6f8…c8b69b
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams340d ago0x848f1b…a653d3
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams340d ago0xb8346a…d97a59
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams340d ago0x8b9917…d9c003
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams340d ago0xbf9eaa…2afbb7
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams341d ago0xe05847…a723c8
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams341d ago0xbf5b68…fc6f77
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams341d ago0x1148e3…14cb11
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams341d ago0x8cd783…0a7707
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams341d ago0xde66d6…eb48ff
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams341d ago0xe56af6…b8c582
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams341d ago0x111e28…0d607c
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams341d ago0x107e3b…43e31d
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams341d ago0x0da582…df08ab
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams342d ago0xc8aec7…a17a4b

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.