AgentReport

0x6ca3…1af4

0x6ca326cfb429d524f82643f9d76cad809e491af4Explorer
Paid out
$0.00065
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.00065 of the $261.62M Roundhouse has indexed across 717,750 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.0006532

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

  • 0x4944…4bf3 · last paid 307d ago
    $0.000383
    2 calls

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

  • 0x0ab9…0cd5 · last paid 307d ago
    $0.000267
    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
0x4944…4bf3$0.000383$0.002307d agoGraph
0x0ab9…0cd5$0.000267$0.001307d agoGraph

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

Data quality

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

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x6ca3…1af40x4944…4bf3Base$0.000171100%questflow307d ago0x532edb…47337a
0x6ca3…1af40x0ab9…0cd5Base$0.000267100%questflow307d ago0x663816…2b1b56
0x6ca3…1af40x4944…4bf3Base$0.000212100%questflow318d ago0x2db8d6…667ec1

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

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

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: 0x6ca3…1af4

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