AgentReport

0x3d1f…5522

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

Paid $0.28 of the $3105.41M Roundhouse has indexed across 1,406,271 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 catalogue96%$0.2733
Web & Content4%$0.0111

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 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
0x07f0…a045$0.24$0.001125d agoGraph
0xabf4…a9d0$0.02$0.001125d agoGraph
0x7dd5…2629$0.02$0.001128d agoGraph
0x325b…d430$0.01$0.001126d agoGraph

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

Data quality

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

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x3d1f…55220xabf4…a9d0BaseBase$0.02100%coinbase125d ago0x91798b…5c1f34
0x3d1f…55220x07f0…a045BaseBase$0.24100%coinbase125d ago0xb14e3f…eb8a7d
0x3d1f…55220x325b…d430BaseBase$0.01100%coinbase126d ago0x52e7b0…1c944c
0x3d1f…55220x7dd5…2629BaseBase$0.02100%coinbase128d ago0x452c93…b33087

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

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

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: 0x3d1f…5522

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