AgentReport

0xc7f0…d5c7

0xc7f0759c986f20c8314c10584f55ecd69e95d5c7Explorer
Paid out
$1.31
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
26
Last 7d vs prior 7d
5
Distinct counterparties
Over the whole indexed history

Paid $1.31 of the $3067.25M Roundhouse has indexed across 1,401,192 wallets — less than 0.0001% of it.

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

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

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

  • 0x3577…ca8d · last paid 37d ago
    $0.79
    1 call

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

  • 0xf7a6…ab0d · last paid 300d ago
    $0.24
    2 calls

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

  • 0x94d0…f73c · last paid 295d ago
    $0.22
    10 calls

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

  • 0x4944…4bf3 · last paid 291d ago
    $0.05
    11 calls

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

  • 0x5fe5…5c72 · last paid 341d ago
    $0.009139
    2 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

MayJunJulAugSepOctNov
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x3577…ca8d$0.79$0.00137d agoGraph
0xf7a6…ab0d$0.24$0.002300d agoGraph
0x94d0…f73c$0.22$0.0010295d agoGraph
0x4944…4bf3$0.05$0.0011291d agoGraph
0x5fe5…5c72$0.009139$0.002341d 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 26 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xc7f0…d5c70x94d0…f73cBaseBase$0.006156100%questflow352d ago0x8fb42e…cc927b

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

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

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: 0xc7f0…d5c7

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