AgentReport

0x6dcc…654f

0x6dccec00d22276d00c72a0b6a91f73fc15e8654fExplorer
Paid out
$6.17
Last 7d vs prior 7d
Received
$0.78
Last 7d vs prior 7d
Settlements
165
Last 7d vs prior 7d
16
Distinct counterparties
Over the whole indexed history

Paid $6.17 of the $3060.46M Roundhouse has indexed across 1,397,991 wallets — less than 0.0001% of it.

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

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 catalogue94%$5.771246
Web & Content3%$0.2153
Company & People2%$0.1522
Crypto Markets<1%$0.0221

$3.09 went to wallets that publish no endpoint in any catalogue we crawl — spend we can see and cannot describe.

Services it paid

A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; for 9 of 12 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
0xcd51…46a9$3.09$0.7813890d agoGraph
0x6e31…b687$2.04$0.005110d agoGraph
0xe903…1abf$0.42$0.003111d agoGraph
0x325b…d430$0.18$0.003104d agoGraph
0x2b6d…32c5$0.15$0.003111d agoGraph
0xade0…89ab$0.10$0.001104d agoGraph
0x40b6…72eb$0.05$0.001104d agoGraph
0xe740…cf46$0.05$0.001110d agoGraph

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

Data quality

56% of observed volume is with a single counterparty, in all 165 observed settlements.

Recent activity

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

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

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: 0x6dcc…654f

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