ERC-8004 identity
#53380Agent #53380QmRZaLXihDKq9FzVsaWD25VkPLqhTRR1EPBmszyfP1xmw7
#51791Agent #51791QmUX6MED2N22WHfxxACBZ9KJrLAtK1uHfXu1BmFzVDM3Qa
AgentReport

0xf345…d2f9

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

Paid $0.03 of the $3059.84M Roundhouse has indexed across 1,397,496 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
Not in any catalogue23%$0.00622

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.

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.0028d agoGraph
0x2932…4f60$0.005$0.0018d agoGraph
0xe341…9f73$0.001$0.0018d 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 0xf345…d2f9 has actually paid for over the free read API. No key, no account.

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

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: 0xf345…d2f9

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