AgentReport

0x6160…a1b3

0x61608f4437992d6ba9c19e6ba4724d95ea1aa1b3Explorer
Paid out
$0.53
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
29
Last 7d vs prior 7d
5
Distinct counterparties
Over the whole indexed history

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

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

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.51252
AI & Media4%$0.0221
Location & Weather<1%$0.00111
Crypto Markets<1%$0.00111

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 4 of 5 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
margar3t.eth$0.43$0.002163d agoGraph
0xdd25…2ec0$0.08$0.004188d agoGraph
0xe903…1abf$0.02$0.002174d agoGraph
Navi Weather$0.001$0.00161d agoGraph
0x0e84…b808$0.001$0.001188d agoGraph

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

Data quality

81% of observed volume is with a single counterparty, in all 29 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x6160…a1b30xdd25…2ec0BaseBase$0.02100%coinbase188d ago0xa0f938…8c46c6
0x6160…a1b30xdd25…2ec0BaseBase$0.02100%coinbase188d ago0x78aff3…6612a0
0x6160…a1b30xdd25…2ec0BaseBase$0.02100%coinbase188d ago0x3d3550…1c3735
0x6160…a1b30xdd25…2ec0BaseBase$0.02100%coinbase188d ago0xbd9bad…dd00a7

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

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

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: 0x6160…a1b3

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