ERC-8004 identity
#55630Agent #55630Qmc7dxV2cf5qUuJVK2DduAFC6KB7VVS9gUBdQG46dZNqLG
AgentReport

0xf7ab…772d

0xf7abdd163f9f817fb05edc8bed9970bc2fbc772dExplorer
$0.009
Paid out
$0.00
Received
4
Settlements
4
Distinct counterparties
Over the whole indexed history

Paid $0.009 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
Not in any catalogue67%$0.00622
Location & Weather22%$0.00211
Crypto Markets11%$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 4 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
0x110c…b784$0.005$0.00117d agoGraph
0x38c0…44c8$0.002$0.00117d agoGraph
0xf567…cb98$0.001$0.00117d agoGraph
0x1274…d0b6$0.001$0.00117d agoGraph

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

Data quality

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

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xf7ab…772d0x38c0…44c8BaseBase$0.002100%coinbase17d ago0x0f1c39…b5579f
0xf7ab…772d0xf567…cb98BaseBase$0.001100%coinbase17d ago0x9ee925…c25dbb
0xf7ab…772d0x1274…d0b6BaseBase$0.001100%coinbase17d ago0x745205…b49237
0xf7ab…772d0x110c…b784BaseBase$0.005100%coinbase17d ago0x5342d1…519653

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

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

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: 0xf7ab…772d

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