AgentReport

0xa878…8e8a

0xa878a31c583c0cab5cfa55959a9d4b14ba2c8e8aExplorer
Paid out
$1.00
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
28
Last 7d vs prior 7d
3
Distinct counterparties
Over the whole indexed history

Paid $1.00 of the $3064.22M Roundhouse has indexed across 1,399,289 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 (28)

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
Risk & Compliance90%$0.90161
Web & Content10%$0.10101
Crypto Markets<1%$0.00221

Every merchant paid publishes at least one catalogued endpoint.

Services it paid

A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; for 3 of 3 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
0x52ab…6c06$0.90$0.001696d agoGraph
0x9bb9…9dc4$0.10$0.001096d agoGraph
0x0e84…b808$0.002$0.00261d agoGraph

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

Data quality

90% of observed volume is with a single counterparty, in all 28 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xa878…8e8a0x9bb9…9dc4BaseBase$0.01100%coinbase96d ago0x002275…ab23df
0xa878…8e8a0x52ab…6c06BaseBase$0.05100%coinbase96d ago0x3c1157…fe2e01
0xa878…8e8a0x9bb9…9dc4BaseBase$0.01100%coinbase96d ago0xdb46a6…241d46

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

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

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: 0xa878…8e8a

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