AgentReport

0xfd89…55e4

0xfd890c4127dee4f720d648d3ae74f639a39955e4Explorer
Paid out
$0.05
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
4
Last 7d vs prior 7d
3
Distinct counterparties
Over the whole indexed history

Paid $0.05 of the $3066.54M Roundhouse has indexed across 1,400,689 wallets — less than 0.0001% of it.

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

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

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 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
0x3803…101b$0.03$0.002156d agoGraph
0xdc59…1506$0.01$0.00151d agoGraph
0x9257…2132$0.01$0.00151d agoGraph

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

Data quality

57% of observed volume is with a single counterparty, in all 4 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xfd89…55e40xdc59…1506BaseBase$0.01100%coinbase51d ago0xe92a10…da2ed5
0xfd89…55e40x9257…2132BaseBase$0.01100%payAI51d ago0xc2f4cf…569a78
0xfd89…55e40x3803…101bBaseBase$0.01100%coinbase156d ago0x1b0357…11e643
0xfd89…55e40x3803…101bBaseBase$0.02100%coinbase156d ago0x6f93cb…d731a3

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

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

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: 0xfd89…55e4

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