AgentReport

0x5bf9…06d3

0x5bf94d2f3de2b994c3aa02a788cfeb757d6e06d3Explorer
Paid out
$2.91
Last 7d vs prior 7d
Received
$0.47
Last 7d vs prior 7d
Settlements
78
Last 7d vs prior 7d
4
Distinct counterparties
Over the whole indexed history

Paid $2.91 of the $3061.41M Roundhouse has indexed across 1,398,256 wallets — less than 0.0001% of it.

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

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%$2.91773

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

One merchant publishes more endpoints than a single catalogue read returns; its list is partial.

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

Funds flow over time

Activity

MayJunJulAugSepOctNov
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x5c5f…4702$2.00$0.00142d agoGraph
0x94f7…4873$0.90$0.007542d agoGraph
0xf9e3…6e53$0.00$0.47145d agoGraph
0xd34e…05b1$0.001$0.00143d agoGraph

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

Data quality

59% of observed volume is with a single counterparty, in all 78 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x5bf9…06d30x94f7…4873BaseBase$0.01100%payAI45d ago0xe768fa…3172d9
0x5bf9…06d30x94f7…4873BaseBase$0.01100%payAI45d ago0xb10773…84dad2
0xf9e3…6e530x5bf9…06d3BaseBase$0.47100%payAI45d ago0x7bd3a8…6e7425

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

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

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: 0x5bf9…06d3

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