AgentReport

0xbc8a…de42

0xbc8a49d08a7ae738d62eb51fbd3609b7c51fde42Explorer
Paid out
$353.85
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
4
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

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

Chains (from the recent scan): Base (1) · Ethereum (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%$353.8542

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

  • 0x5c7b…35c5 · last paid 215d ago
    $217.35
    3 calls

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

  • 0x0e3d…7757 · last paid 146d ago
    $136.50
    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
0x5c7b…35c5$217.35$0.003215d agoGraph
0x0e3d…7757$136.50$0.001146d agoGraph

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

Data quality

61% of observed volume is with a single counterparty, in all 4 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xbc8a…de420x0e3d…7757BaseBase$136.5070%0x406c…cda3146d ago0x30a28e…f6aeea
0xbc8a…de420x5c7b…35c5EthereumEthereum$77.7070%0xe0df…59a1215d ago0x0e02ac…72ac13
0xbc8a…de420x5c7b…35c5EthereumEthereum$70.3570%0xc10a…ae5d217d ago0xc9a592…3f340d
0xbc8a…de420x5c7b…35c5EthereumEthereum$69.3070%0xd016…b67a221d ago0xcdfdd6…d65333

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

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

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: 0xbc8a…de42

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