AgentReport

0x0c0a…d4c0

0x0c0a9e3d128c27e13fd6170ce9bd280227f2d4c0Explorer
Paid out
$460.21
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
5
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $460.21 of the $3105.41M Roundhouse has indexed across 1,406,887 wallets — less than 0.0001% of it.

Chains (from the recent scan): Ethereum (5)

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
Web & Content100%$460.2151

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; no listed price matches an amount this agent paid, so nothing narrows them.

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
0x480c…846a$460.21$0.00545d agoGraph

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

Data quality

100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 5 observed settlements.

Organic volume $460.21 of $460.21 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x0c0a…d4c00x480c…846aEthereumEthereum$235.2970%0x480c…846a45d ago0xbc40bf…a409d5
0x0c0a…d4c00x480c…846aEthereumEthereum$113.9170%0x480c…846a45d ago0x4559a0…592d5d
0x0c0a…d4c00x480c…846aEthereumEthereum$19.7970%0x480c…846a46d ago0xa65f68…3bab70
0x0c0a…d4c00x480c…846aEthereumEthereum$66.2270%0x480c…846a46d ago0x2d50cd…fc50d9
0x0c0a…d4c00x480c…846aEthereumEthereum$25.0070%0x480c…846a46d ago0x27c2ee…ec1ef5

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

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

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: 0x0c0a…d4c0

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