AgentReport

0x33b2…fd8c

0x33b26e111fc756887edcc2c85862056378dcfd8cExplorer
Paid out
$1.59
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
227
Last 7d vs prior 7d
4
Distinct counterparties
Over the whole indexed history

Paid $1.59 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 (227)

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
Crypto Markets75%$1.202111
Not in any catalogue24%$0.39152
Web & Content<1%$0.0111

$0.38 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 3 of 4 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
0x52e2…f3ea$1.20$0.0021151d agoGraph
0x4020…0004$0.38$0.0014109d agoGraph
0x3803…101b$0.01$0.001166d agoGraph
0x325b…d430$0.01$0.00188d agoGraph

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

Data quality

75% of observed volume is with a single counterparty, in all 227 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x33b2…fd8c0x4020…0004BaseBase$0.005100%coinbase160d ago0xc52b79…44a4a1
0x33b2…fd8c0x3803…101bBaseBase$0.01100%coinbase166d ago0x54e306…ae79bd

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

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

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: 0x33b2…fd8c

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