AgentReport

0xb14f…5fc4

0xb14f87cad62f0c9837af3e07066121ce3db55fc4Explorer
Paid out
$0.19
Last 7d vs prior 7d
Received
$0.17
Last 7d vs prior 7d
Settlements
28
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.19 of the $833.89M Roundhouse has indexed across 1,300,243 wallets — less than 0.0001% of it.

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

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

$0.19 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 15d ago
    $0.19
    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.19$0.00115d agoGraph
0xf04d…5c29$0.00$0.1727341d agoGraph

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

Data quality

53% of observed volume is with a single counterparty, in all 28 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xb14f…5fc40x3577…ca8dBase$0.1970%0x642b…6c7515d ago0x18fe2e…760a85
0xf04d…5c290xb14f…5fc4Base$0.001677100%questflow341d ago0x8739d0…cb2968
0xf04d…5c290xb14f…5fc4Base$0.001007100%questflow341d ago0x4906b1…aef916
0xf04d…5c290xb14f…5fc4Base$0.005189100%questflow347d ago0x0df9f8…327a3e
0xf04d…5c290xb14f…5fc4Base$0.03100%questflow348d ago0x9b9ba3…f27d5e
0xf04d…5c290xb14f…5fc4Base$0.02100%questflow348d ago0x655f1a…2589b6
0xf04d…5c290xb14f…5fc4Base$0.000748100%questflow348d ago0x5ccc93…576cc3
0xf04d…5c290xb14f…5fc4Base$0.000276100%questflow348d ago0x0933d5…ba208c
0xf04d…5c290xb14f…5fc4Base$0.0008100%questflow348d ago0x3bec1a…d4acb3
0xf04d…5c290xb14f…5fc4Base$0.000245100%questflow348d ago0xb02257…0fd165
0xf04d…5c290xb14f…5fc4Base$0.001538100%questflow348d ago0x08b43c…46abf6
0xf04d…5c290xb14f…5fc4Base$0.004556100%questflow348d ago0x0bb580…c63a65
0xf04d…5c290xb14f…5fc4Base$0.01100%questflow348d ago0xf5ec42…25f248
0xf04d…5c290xb14f…5fc4Base$0.004892100%questflow348d ago0x23b17b…0128d1
0xf04d…5c290xb14f…5fc4Base$0.07100%questflow348d ago0xde665c…16fe28
0xf04d…5c290xb14f…5fc4Base$0.001525100%questflow349d ago0xd14103…4ff173
0xf04d…5c290xb14f…5fc4Base$0.004981100%questflow349d ago0x48331a…65e261
0xf04d…5c290xb14f…5fc4Base$0.004693100%questflow349d ago0x9a1143…238f74
0xf04d…5c290xb14f…5fc4Base$0.000189100%questflow349d ago0xabbfbc…65ae1c
0xf04d…5c290xb14f…5fc4Base$0.000628100%questflow349d ago0xb5a70d…1414e2
0xf04d…5c290xb14f…5fc4Base$0.001748100%questflow352d ago0x701615…f26e97
0xf04d…5c290xb14f…5fc4Base$0.000278100%questflow352d ago0x6fc0da…677b71
0xf04d…5c290xb14f…5fc4Base$0.002446100%questflow352d ago0x9de107…c0bb18
0xf04d…5c290xb14f…5fc4Base$0.000654100%questflow352d ago0xfb64b7…8260fe
0xf04d…5c290xb14f…5fc4Base$0.006385100%questflow353d ago0xacccee…24eb72

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

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

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: 0xb14f…5fc4

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