ERC-8004 identity
#50934Agent #50934QmUJa6XQy642qdNxhv9JWReN1FzMcacze1fawypY2Ndiwy
#47023Agent #47023bafkreige7rknajtya5w4btkeyrmxtiuqhy7nskfixbgjghd5pugtxx6gze
#55673Agent #55673bafkreicp2mjiiewz33mwj6n3a4rq6gbodwrzaip7c4cxpleqvj74rtzf7q
AgentReport

0xcdd5…1f4e

0xcdd5cb6ab2b9c5f3d2bae896ce516b65010c1f4eExplorer
Paid out
$2.00↓ 100%
Last 7d vs prior 7d
Received
$7.44↑ 11%
Last 7d vs prior 7d
Settlements
41↓ 30%
Last 7d vs prior 7d
25
Distinct counterparties
Over the whole indexed history

Paid $2.00 of the $3060.21M Roundhouse has indexed across 1,397,618 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (41)

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 catalogue100%$2.0011

$2.00 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; no listed price matches an amount this agent paid, so nothing narrows them.

  • 0xcb8e…f2ae · last paid 8d ago
    $2.00
    1 call

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

Balance now
Reading the chain…
Spending power
Reading the chain…
Burn rate
Reading the chain…
Runway
Reading the chain…

Funds flow over time

Activity

MayJunJulAugSepOctNov
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0xeb3a…cbb6$0.00$7.00267d agoGraph
0xcb8e…f2ae$2.00$0.0018d agoGraph
0x9435…6f1f$0.00$0.26571d agoGraph
0x3111…eee8$0.00$0.0321d agoGraph
0xa19f…accc$0.00$0.0355d agoGraph
0x35fe…c030$0.00$0.0235d agoGraph
0xaa34…1db3$0.00$0.0125d agoGraph
0x73cc…1ea4$0.00$0.0129d agoGraph

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

Data quality

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

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

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: 0xcdd5…1f4e

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