AgentReport

0xf52a…9f21

0xf52ab0d4b36014f685dbb0b8c7bd86124ece9f21Explorer
Paid out
$0.005↓ 75%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
3↓ 50%
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.005 of the $833.92M Roundhouse has indexed across 1,300,305 wallets — less than 0.0001% of it.

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

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

Every merchant paid publishes at least one catalogued endpoint.

Services it paid

A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; for 1 of 1 the amount paid narrows the list to the ones listed at that price.

  • JSON Repaircanary.digitalworkerapi.comEndpoint up
    0x13fe…d27e · last paid 4d ago
    $0.005
    3 calls
    ▸2 of 2 catalogued endpoints list a price this agent paid
Balance now
Reading the chain…
Spending power
Reading the chain…
Burn rate
Reading the chain…
Runway
Reading the chain…

Funds flow over time

Activity

AprMayJunJulAugSepOct
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x13fe…d27e$0.005$0.0034d 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 3 observed settlements.

Organic volume $0.005 of $0.005 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xf52a…9f210x13fe…d27eBase$0.001100%coinbase4d ago0x7c208c…7b0a25
0xf52a…9f210x13fe…d27eBase$0.002100%coinbase11d ago0x9b9595…a41f88
0xf52a…9f210x13fe…d27eBase$0.002100%coinbase11d ago0xdb738c…159bc7

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

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

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: 0xf52a…9f21

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