AgentReport

0xf7b7…a427

0xf7b7c153da287b41d8067565fd5592a96077a427Explorer
Paid out
$27.83
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
53
Last 7d vs prior 7d
4
Distinct counterparties
Over the whole indexed history

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

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

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%$27.78443
Company & People<1%$0.0591

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 3 of 4 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
0xd219…6801$22.68$0.004286d agoGraph
0xe903…1abf$5.00$0.00187d agoGraph
0xf4b8…084c$0.10$0.00182d agoGraph
0x3c5c…d5fa$0.05$0.00987d agoGraph

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

Data quality

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

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xf7b7…a4270x3c5c…d5faBaseBase$0.005100%coinbase87d ago0x493e6f…eea7ea
0xf7b7…a4270xd219…6801BaseBase$0.54100%coinbase87d ago0x1f7366…1428bf
0xf7b7…a4270xd219…6801BaseBase$0.54100%coinbase87d ago0x326422…51b5ba

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

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

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: 0xf7b7…a427

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