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,563 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%daydreams352d ago0xeb2778…e352dc
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams353d ago0x95cac0…72e2d5
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams353d ago0x2738d8…f90bcf
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams353d ago0x3d7bd6…f40b81
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams353d ago0x6c8720…457798
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams353d ago0x8e2ec9…0cabbc
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams353d ago0xd44d76…c46ded
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams355d ago0x54ae7d…a1355d
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams355d ago0x35a7f2…a37d32
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams355d ago0x04d3bd…b78f82
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams355d ago0x139a2b…3a03ae
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams356d ago0xb92012…ed74ba
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams356d ago0x08f35c…751737
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams357d ago0x6d347c…1bb683
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams357d ago0x7ec49c…d2de75
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams357d ago0x24d2e1…a96484
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams357d ago0xdfe9a1…7263b2
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams357d ago0x0a86aa…525bfa
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams357d ago0xb65f25…9e9f41
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams358d ago0x7e4816…b1b9a6
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams358d ago0x305787…bc8054
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams358d ago0x82fc13…05c9ee
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams358d ago0x924e37…7da58d
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams358d ago0x3e8e66…ac9c47
0xca52…54170x6482…b779BaseBase$0.0001100%daydreams359d ago0xc8362e…6e9fee

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.