ERC-8004 identity
#55058Agent #55058Qmb5mVtBE37v5Fz2zGdbwTnEM225TYkztSeRP3ERPZ9jdW
AgentReport

0xadb2…43c7

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

Paid $0.01 of the $3053.48M Roundhouse has indexed across 1,395,044 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 catalogue50%$0.00511
Crypto Markets40%$0.00421
Onchain Data10%$0.00111

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
0x2932…4f60$0.005$0.00123d agoGraph
0x0e84…b808$0.004$0.00223d agoGraph
0x5bb4…9f68$0.001$0.00123d agoGraph

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

Data quality

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

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xadb2…43c70x2932…4f60BaseBase$0.005100%coinbase23d ago0x12018a…f582d0
0xadb2…43c70x5bb4…9f68BaseBase$0.001100%coinbase23d ago0xe848bf…418d7d
0xadb2…43c70x0e84…b808BaseBase$0.001100%coinbase23d ago0x1f15f1…266b92
0xadb2…43c70x0e84…b808BaseBase$0.003100%coinbase23d ago0x9d85fe…46068c

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

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

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: 0xadb2…43c7

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