ERC-8004 identity
#54971Agent #54971QmWcDpqedH4cmm2CKLUhsMowCQm4RZbnYVv9bkVbBReXnJ
AgentReport

0x6f7a…e38f

0x6f7ae9dfc394082f773d18b74818dccb0e59e38fExplorer
$0.02
Paid out
$0.00
Received
4
Settlements
3
Distinct counterparties
Over the whole indexed history

Paid $0.02 of the $3060.21M Roundhouse has indexed across 1,397,717 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 catalogue88%$0.0222
Crypto Markets12%$0.00221

$0.01 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 2 of 3 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…

Activity

MayJunJulAugSepOctNov
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
godiscrypto.eth$0.01$0.00126d agoGraph
0x2932…4f60$0.005$0.00126d agoGraph
0x0e84…b808$0.002$0.00226d agoGraph

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

Data quality

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

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x6f7a…e38f0x0e84…b808BaseBase$0.001100%coinbase26d ago0x0c9ebf…df5e08
0x6f7a…e38fgodiscrypto.ethBaseBase$0.01100%payAI26d ago0x92ec02…192c2d
0x6f7a…e38f0x2932…4f60BaseBase$0.005100%coinbase26d ago0x255ea7…23d9c5
0x6f7a…e38f0x0e84…b808BaseBase$0.001100%coinbase26d ago0xad90ea…7ec025

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

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

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: 0x6f7a…e38f

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