AgentReport

0xbc22…0f5b

0xbc2223f15840e5c8855a552d423a0dfb3a800f5bExplorer
Paid out
$0.02
Last 7d vs prior 7d
Received
$0.02
Last 7d vs prior 7d
Settlements
21
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.02 of the $843.80M Roundhouse has indexed across 1,324,156 wallets — less than 0.0001% of it.

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

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

$0.02 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.

  • 0x3577…ca8d · last paid 21d ago
    $0.02
    1 call

    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

AprMayJunJulAugSepOct
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x3577…ca8d$0.02$0.00121d agoGraph
0xafc6…a22d$0.00$0.0220324d agoGraph

Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.

Data quality

51% of observed volume is with a single counterparty, in all 21 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xbc22…0f5b0x3577…ca8dBase$0.0270%0x642b…6c7521d ago0xa0be08…07c120
0xafc6…a22d0xbc22…0f5bBase$0.00654100%questflow324d ago0xd85c94…6fcb1a
0xafc6…a22d0xbc22…0f5bBase$0.003252100%questflow325d ago0x78a70a…58928c
0xafc6…a22d0xbc22…0f5bBase$0.000325100%questflow326d ago0xe87da4…34f73f
0xafc6…a22d0xbc22…0f5bBase$0.000073100%questflow328d ago0x03d2fb…f7065b
0xafc6…a22d0xbc22…0f5bBase$0.000056100%questflow331d ago0x58f034…2a74a3
0xafc6…a22d0xbc22…0f5bBase$0.002292100%questflow331d ago0x765c0d…7f2bd1
0xafc6…a22d0xbc22…0f5bBase$0.000057100%questflow332d ago0x22f4de…d3f18d
0xafc6…a22d0xbc22…0f5bBase$0.000055100%questflow336d ago0xe34cbd…ef87b4
0xafc6…a22d0xbc22…0f5bBase$0.000397100%questflow339d ago0x5e35ac…8e5294
0xafc6…a22d0xbc22…0f5bBase$0.00036100%questflow340d ago0x1974cc…655dd3
0xafc6…a22d0xbc22…0f5bBase$0.000341100%questflow341d ago0x65bddb…69fe52
0xafc6…a22d0xbc22…0f5bBase$0.000309100%questflow342d ago0xf835e8…d86697
0xafc6…a22d0xbc22…0f5bBase$0.000277100%questflow343d ago0xffcefc…32b9e0
0xafc6…a22d0xbc22…0f5bBase$0.000201100%questflow344d ago0x9ecb78…25d1a8
0xafc6…a22d0xbc22…0f5bBase$0.00061100%questflow346d ago0x5d7238…b7b5bb
0xafc6…a22d0xbc22…0f5bBase$0.000272100%questflow347d ago0x953879…eb6ff7
0xafc6…a22d0xbc22…0f5bBase$0.000269100%questflow349d ago0x9152ff…2a0a8f
0xafc6…a22d0xbc22…0f5bBase$0.000287100%questflow350d ago0x90fadd…b9d756
0xafc6…a22d0xbc22…0f5bBase$0.000317100%questflow351d ago0x913cc9…c11e28
0xafc6…a22d0xbc22…0f5bBase$0.003134100%questflow352d ago0x1555ac…8b2328

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

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

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: 0xbc22…0f5b

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