AgentReport

0xf6c3…26c2

0xf6c3065ef9b4b8439fd2e4058bcfa18ddc7d26c2Explorer
Paid out
$0.21
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
3
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.21 of the $260.74M Roundhouse has indexed across 716,479 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (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%$0.2132

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

  • 0x6a1f…0a4a · last paid 299d ago
    $0.20
    2 calls

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

  • 0xef43…6c7f · last paid 249d ago
    $0.01
    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

MarAprMayJunJulAugSep
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x6a1f…0a4a$0.20$0.002299d agoGraph
0xef43…6c7f$0.01$0.001249d agoGraph

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

Data quality

95% of observed volume is with a single counterparty, in all 3 observed settlements.

Organic volume $0.21 of $0.21 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xf6c3…26c20xef43…6c7fBase$0.01100%virtuals249d ago0x849725…df3ab3
0xf6c3…26c20x6a1f…0a4aBase$0.10100%virtuals299d ago0x211350…06499c
0xf6c3…26c20x6a1f…0a4aBase$0.10100%virtuals308d ago0x46f809…310149

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

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

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: 0xf6c3…26c2

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