AgentReport

0xdc2a…bc73

0xdc2a66b851448e942ea43a940701debdd404bc73Explorer
Paid out
$0.03
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.03 of the $842.65M Roundhouse has indexed across 1,320,224 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.0311

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

  • 0x3577…ca8d · last paid 20d ago
    $0.03
    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.03$0.00120d agoGraph
0xb84c…5c30$0.00$0.0220325d agoGraph

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

Data quality

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

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xdc2a…bc730x3577…ca8dBase$0.0370%0x642b…6c7520d ago0x4d119b…787756
0xb84c…5c300xdc2a…bc73Base$0.000325100%questflow325d ago0x30ec20…6ef0e1
0xb84c…5c300xdc2a…bc73Base$0.009451100%questflow326d ago0x744b42…76a06a
0xb84c…5c300xdc2a…bc73Base$0.000078100%questflow330d ago0xfb5a9e…8299f7
0xb84c…5c300xdc2a…bc73Base$0.000062100%questflow330d ago0x0c01ab…83a32d
0xb84c…5c300xdc2a…bc73Base$0.001088100%questflow332d ago0xab185a…ad7322
0xb84c…5c300xdc2a…bc73Base$0.000067100%questflow333d ago0x235837…1d3b99
0xb84c…5c300xdc2a…bc73Base$0.000052100%questflow334d ago0xd97f4b…ca329c
0xb84c…5c300xdc2a…bc73Base$0.000061100%questflow336d ago0xac5c6a…665b2e
0xb84c…5c300xdc2a…bc73Base$0.000431100%questflow339d ago0xc72233…8fe6e2
0xb84c…5c300xdc2a…bc73Base$0.000391100%questflow341d ago0xc5f067…5e5479
0xb84c…5c300xdc2a…bc73Base$0.000347100%questflow341d ago0xcd02eb…888fd3
0xb84c…5c300xdc2a…bc73Base$0.000285100%questflow343d ago0x240d40…048b61
0xb84c…5c300xdc2a…bc73Base$0.000235100%questflow343d ago0x5c209b…a3f213
0xb84c…5c300xdc2a…bc73Base$0.000243100%questflow345d ago0x49f608…5f194a
0xb84c…5c300xdc2a…bc73Base$0.000256100%questflow347d ago0x913a6c…0564c7
0xb84c…5c300xdc2a…bc73Base$0.000355100%questflow348d ago0xa88145…f72893
0xb84c…5c300xdc2a…bc73Base$0.000229100%questflow349d ago0xd4e11f…f00150
0xb84c…5c300xdc2a…bc73Base$0.000384100%questflow350d ago0xc56d05…7794d2
0xb84c…5c300xdc2a…bc73Base$0.000406100%questflow351d ago0xdf4807…cb41d1
0xb84c…5c300xdc2a…bc73Base$0.000282100%questflow351d ago0x71a2ae…3d7d77

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

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

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: 0xdc2a…bc73

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