ERC-8004 identity
#55056Agent #55056QmWPA94ybRjLKZt6vjoAiwD9Bc3UghZzqD1zpuDgALuPPy
AgentReport

0xed5b…da69

0xed5b745fb49b847e397d0dfcfc91c4763de7da69Explorer
$0.02
Paid out
$0.00
Received
4
Settlements
4
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 catalogue80%$0.0122
Location & Weather13%$0.00211
AI & Media7%$0.00111

$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 3 of 4 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
godiscrypto.eth$0.01$0.00124d agoGraph
0x38c0…44c8$0.002$0.00124d agoGraph
0xcf92…42fb$0.002$0.00124d agoGraph
0x3da4…4664$0.001$0.00124d agoGraph

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

Data quality

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

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xed5b…da69godiscrypto.ethBaseBase$0.01100%payAI24d ago0x30ef31…300fae
0xed5b…da690x38c0…44c8BaseBase$0.002100%coinbase24d ago0xd0bd58…9c1a01
0xed5b…da690xcf92…42fbBaseBase$0.002100%coinbase24d ago0xabc1fe…a18a4b
0xed5b…da690x3da4…4664BaseBase$0.001100%coinbase24d ago0xb38892…2583d5

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

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

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: 0xed5b…da69

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