AgentReport

0xc0a7…5722

0xc0a728f611362bcc5dcfbb1d0967ad2395bf5722Explorer
Paid out
$0.001304
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 $0.001304 of the $260.74M Roundhouse has indexed across 716,479 wallets — less than 0.0001% of it.

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

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.00130442

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

  • 0xcb11…5101 · last paid 306d ago
    $0.000795
    2 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 306d ago
    $0.000509
    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

MarAprMayJunJulAugSep
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0xcb11…5101$0.000795$0.002306d agoGraph
0x4944…4bf3$0.000509$0.002306d 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
0xc0a7…57220xcb11…5101Base$0.000416100%questflow306d ago0x885b8a…9fc599
0xc0a7…57220x4944…4bf3Base$0.000266100%questflow306d ago0x8d8c2d…f15fc2
0xc0a7…57220xcb11…5101Base$0.000379100%questflow317d ago0x058ba8…e764f0
0xc0a7…57220x4944…4bf3Base$0.000243100%questflow317d ago0xc4efc2…29fef8

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

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

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: 0xc0a7…5722

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