AgentReport

0x5f5c…a347

0x5f5ca9df69c856bf247621e31eb281d0646ea347Explorer
Paid out
$35.14
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
22021
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $35.14 of the $260.74M Roundhouse has indexed across 716,479 wallets — less than 0.0001% of it.

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

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%$3.911,0002

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 2 of 2 the amount paid narrows the list to the ones listed at that price.

Folded from this wallet's 1,000 most recent settlements of 22,021 lifetime, which is as far back as one scan reaches — so every figure in this section is a floor, and the totals above are not.

Balance now
Reading the chain…
Spending power
Reading the chain…
Burn rate
Reading the chain…
Runway
Reading the chain…

Funds flow over time

Activity

MarAprMayJunJulAugSep
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x0495…eed9$2.38$0.00847225d agoGraph
0x8324…fd0e$1.53$0.00153238d agoGraph

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

Data quality

61% of observed volume is with a single counterparty, in the 1000 most recent settlements scanned (its history is longer than the 2000-row scan cap).

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x5f5c…a3470x0495…eed9Base$0.10100%payAI225d ago0x9cb5fa…bb7c66
0x5f5c…a3470x0495…eed9Base$0.10100%payAI225d ago0x5132e4…47301a
0x5f5c…a3470x0495…eed9Base$0.10100%payAI225d ago0x9d9233…315afb
0x5f5c…a3470x0495…eed9Base$0.10100%payAI225d ago0x5292b5…a640f3
0x5f5c…a3470x0495…eed9Base$0.10100%payAI225d ago0xeafbf3…cc3d3a
0x5f5c…a3470x0495…eed9Base$0.10100%payAI225d ago0x5fade5…c89e69
0x5f5c…a3470x0495…eed9Base$0.10100%payAI225d ago0x6ad061…4caa16
0x5f5c…a3470x0495…eed9Base$0.10100%payAI225d ago0x3bcb06…63a4e9
0x5f5c…a3470x0495…eed9Base$0.10100%payAI225d ago0x62e52d…db0a6f
0x5f5c…a3470x0495…eed9Base$0.10100%payAI225d ago0x8ddee0…dce406
0x5f5c…a3470x0495…eed9Base$0.10100%payAI225d ago0x15fdc9…7df555
0x5f5c…a3470x0495…eed9Base$0.10100%payAI225d ago0x2425cb…4c48a3
0x5f5c…a3470x0495…eed9Base$0.10100%payAI225d ago0xb8ecc2…21a21f
0x5f5c…a3470x0495…eed9Base$0.10100%payAI225d ago0xa0d18b…1c924e
0x5f5c…a3470x0495…eed9Base$0.10100%payAI225d ago0xe41b3d…f9b81f
0x5f5c…a3470x0495…eed9Base$0.10100%payAI225d ago0xade180…e8b2db
0x5f5c…a3470x0495…eed9Base$0.10100%payAI225d ago0xeeef2e…72369b
0x5f5c…a3470x0495…eed9Base$0.10100%payAI225d ago0x6b5ec5…938f26
0x5f5c…a3470x0495…eed9Base$0.10100%payAI225d ago0x5a5936…280606
0x5f5c…a3470x0495…eed9Base$0.10100%payAI225d ago0x698b5a…6cc56f
0x5f5c…a3470x0495…eed9Base$0.10100%payAI225d ago0x1e693e…9c5606
0x5f5c…a3470x0495…eed9Base$0.10100%payAI225d ago0xe29058…71d8e7
0x5f5c…a3470x0495…eed9Base$0.10100%payAI225d ago0xe671b1…55ab0f
0x5f5c…a3470x8324…fd0eBase$0.01100%payAI238d ago0x954f77…a0a507
0x5f5c…a3470x0495…eed9Base$0.0001100%payAI238d ago0x5016f4…ff6a56

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

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

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: 0x5f5c…a347

curl -s 'https://api.roundhouseai.io/v0/agents/0x5f5ca9df69c856bf247621e31eb281d0646ea347'
curl -s 'https://api.roundhouseai.io/v0/entities/0x5f5ca9df69c856bf247621e31eb281d0646ea347/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. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402,
or use an organization key from https://roundhouseai.io/dashboard/team.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.