AgentReport

0xedd2…921c

0xedd26ec2a23ba2b6fb9ace401259135afeca921cExplorer
Paid out
$384.22
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
3
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $384.22 of the $3060.46M Roundhouse has indexed across 1,397,991 wallets — less than 0.0001% of it.

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

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%$384.2232

$384.22 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.

  • 0x849d…eba4 · last paid 127d ago
    $381.94
    2 calls

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

  • 0xeb1f…2bd6 · last paid 124d ago
    $2.29
    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
0x849d…eba4$381.94$0.002127d agoGraph
0xeb1f…2bd6$2.29$0.001124d agoGraph

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

Data quality

99% of observed volume is with a single counterparty, in all 3 observed settlements.

Organic volume $384.22 of $384.22 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xedd2…921c0xeb1f…2bd6BaseBase$2.2970%0x4661…93fd124d ago0x90fd7c…a334c8
0xedd2…921c0x849d…eba4BaseBase$162.2870%0x4661…93fd127d ago0xfe0e87…4bb9ad
0xedd2…921c0x849d…eba4BaseBase$219.6670%0x4661…93fd128d ago0x68a3cf…f633a5

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

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

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: 0xedd2…921c

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