ERC-8004 identity
#53191Agent #53191QmSVa7Rek1cWW6ZBKjNS7D6s121xBxR4gF5FPmHEYMgFVh
#53927Agent #53927QmekTodBsJyqQXytS54UNX6fzi9qUJvq5bj5oSyHvRzDFt
AgentReport

0x6e5e…9057

0x6e5e343a363440f488b5533e74f954e533389057Explorer
$0.04
Paid out
$0.00
Received
5
Settlements
3
Distinct counterparties
Over the whole indexed history

Paid $0.043 of $3.26B indexed (less than 0.0001%).

Chains (from the recent scan): Base (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
Crypto Markets100%$0.0453

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 3 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
0x9305…f13f$0.03$0.0034d agoGraph
0x6e00…b04c$0.0085$0.0014d agoGraph
0x52e2…f3ea$0.005$0.0014d agoGraph

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

Data quality

69% of volume with one counterparty.

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

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

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: 0x6e5e…9057

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