AgentReport

0x7f8c6db60b46f7ecba131b882fbea1fed4f5f4f5

0x7f8c6db60b46f7ecba131b882fbea1fed4f5f4f5Explorer
Paid out
$0.51
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
9
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.51 of the $260.88M Roundhouse has indexed across 716,644 wallets — less than 0.0001% of it.

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

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%$0.5191

$0.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; no listed price matches an amount this agent paid, so nothing narrows them.

  • 0xaeb9…6602 · last paid 115d ago
    $0.51
    9 calls

    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

MarAprMayJunJulAugSep
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0xaeb9…6602$0.51$0.009115d agoGraph

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

Data quality

100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 9 observed settlements.

Organic volume $0.51 of $0.51 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x7f8c…f4f50xaeb9…6602Base$0.005100%Payer-submitted115d ago0xe1bc4a…cf1035
0x7f8c…f4f50xaeb9…6602Base$0.005100%Payer-submitted115d ago0xe7d8ad…4ce3e5
0x7f8c…f4f50xaeb9…6602Base$0.20100%Payer-submitted115d ago0xcead39…8c174c
0x7f8c…f4f50xaeb9…6602Base$0.05100%Payer-submitted115d ago0xe4bbaf…5d9388
0x7f8c…f4f50xaeb9…6602Base$0.05100%Payer-submitted119d ago0xa63531…6a92d7
0x7f8c…f4f50xaeb9…6602Base$0.05100%Payer-submitted119d ago0x6ac7e2…d8f577
0x7f8c…f4f50xaeb9…6602Base$0.05100%Payer-submitted119d ago0xdf6ddb…f70f55
0x7f8c…f4f50xaeb9…6602Base$0.05100%Payer-submitted119d ago0x00f972…95ece8
0x7f8c…f4f50xaeb9…6602Base$0.05100%Payer-submitted119d ago0x321475…8e7ce8

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

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

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: 0x7f8c6db60b46f7ecba131b882fbea1fed4f5f4f5

curl -s 'https://api.roundhouseai.io/v0/agents/0x7f8c6db60b46f7ecba131b882fbea1fed4f5f4f5'
curl -s 'https://api.roundhouseai.io/v0/entities/0x7f8c6db60b46f7ecba131b882fbea1fed4f5f4f5/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. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402,
or use an organization key from https://roundhouseai.io/dashboard/team.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.