AgentReport

0x8389…93ff

0x8389b685b79cd5a7aa16677715f8ec49c07393ffExplorer
Paid out
$11.02
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
139
Last 7d vs prior 7d
13
Distinct counterparties
Over the whole indexed history

Paid $11.02 of the $3064.22M Roundhouse has indexed across 1,399,483 wallets — less than 0.0001% of it.

Whole-history totals from the index rollup, which can be up to 30 minutes behind.

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

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 catalogue61%$6.68158
Web & Content32%$3.581193
Crypto Markets7%$0.7511

$6.51 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 7 of 12 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…

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
0xd17d…4e47$6.46$0.00261d agoGraph
0xdd25…2ec0$3.19$0.0059122d agoGraph
0x3070…fa85$0.75$0.00146d agoGraph
0x6d6e…9192$0.24$0.005793d agoGraph
0x8c12…f1b2$0.15$0.00346d agoGraph
0x54d6…4afa$0.10$0.00246d agoGraph
0x03d7…584c$0.04$0.001104d agoGraph
0x3803…101b$0.03$0.002150d agoGraph

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

Data quality

59% of observed volume is with a single counterparty, in all 139 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 0x8389…93ff has actually paid for over the free read API. No key, no account.

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

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: 0x8389…93ff

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