ERC-8004 identity
#55631Agent #55631QmNVnT9schz4masJaovq72sSw7wpSHZDCnj7XuaHq4EZ8R
AgentReport

0x9a60…b4bc

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

Paid $0.03 of the $3060.46M Roundhouse has indexed across 1,397,991 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
Crypto Markets77%$0.0221
Web & Content19%$0.00511
Not in any catalogue4%$0.00111

$0.001 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.

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.02$0.00215d agoGraph
0x51d5…f78b$0.005$0.00115d agoGraph
0x6026…efb7$0.001$0.00115d agoGraph

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

Data quality

77% of observed volume is with a single counterparty, in all 4 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 0x9a60…b4bc has actually paid for over the free read API. No key, no account.

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

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: 0x9a60…b4bc

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