AgentReport

0x76e1…3581

0x76e1b023aaa5379ec45a3d046d7a83a89c173581Explorer
Paid out
$25.50
Last 7d vs prior 7d
Received
$6.72
Last 7d vs prior 7d
Settlements
107
Last 7d vs prior 7d
9
Distinct counterparties
Over the whole indexed history

Paid $25.50 of the $3061.41M Roundhouse has indexed across 1,398,667 wallets — less than 0.0001% of it.

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

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 catalogue95%$24.20354
Web & Content5%$1.29643
Crypto Markets<1%$0.0111

$18.02 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 8 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
0x0617…b3ff$18.02$0.001145d agoGraph
0x26eb…bcea$0.00$6.727132d agoGraph
0x8755…c62e$5.48$0.0010139d agoGraph
0xdd25…2ec0$1.25$0.0060136d agoGraph
0x9acf…2abf$0.69$0.0020156d agoGraph
0x6d6e…9192$0.02$0.003158d agoGraph
0x325b…d430$0.02$0.001165d agoGraph
0x124f…4478$0.01$0.001158d 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 107 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 0x76e1…3581 has actually paid for over the free read API. No key, no account.

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

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: 0x76e1…3581

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