AgentReport

0x6435…c2f1

0x64352f8656d39090f2c4231600f9844be559c2f1Explorer
Paid out
$0.000577
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.000577 of the $258.78M Roundhouse has indexed across 713,781 walletsless 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.00057742

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

  • 0xfbb4…3abc · last paid 308d ago
    $0.000351
    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 308d ago
    $0.000226
    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
0xfbb4…3abc$0.000351$0.002308d agoGraph
0x4944…4bf3$0.000226$0.002308d 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
0x6435…c2f10xfbb4…3abcBase$0.000099100%questflow308d ago0x35cb3e…88ba3b
0x6435…c2f10x4944…4bf3Base$0.000064100%questflow308d ago0xf27f27…261ad1
0x6435…c2f10x4944…4bf3Base$0.000162100%questflow314d ago0x9bb581…93a89b
0x6435…c2f10xfbb4…3abcBase$0.000252100%questflow314d ago0xc4b305…214492

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

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

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: 0x6435…c2f1

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