AgentReport

0x353c…cafe

0x353c9314d42341d62b5e807bc1362d18081fcafeExplorer
Paid out
$0.97↑ 45%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
967↑ 45%
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.97 of the $3061.41M Roundhouse has indexed across 1,398,667 wallets — less than 0.0001% of it.

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

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

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

  • 0xfe80…47ee · last paid 9m ago
    $0.78
    782 calls

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

  • 0x9c95…e299 · last paid 81d ago
    $0.19
    185 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
0xfe80…47ee$0.78$0.007829m agoGraph
0x9c95…e299$0.19$0.0018581d agoGraph

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

Data quality

81% of observed volume is with a single counterparty, in all 967 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa15h ago0x80ec26…59a8bd
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa15h ago0xd799f4…856fec
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa16h ago0xaf97de…48b626
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa16h ago0x031472…92dff6
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa17h ago0x70bf60…b22fe7
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa18h ago0x1fa7a9…3daaa0
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa18h ago0x2ce1e2…ac13f9
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa19h ago0x7243a6…72e2a0
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa19h ago0xc41ada…398a3d
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa20h ago0xa0cec6…6accb0
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa21h ago0x1c2281…7fa333
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa21h ago0xeb7738…80b23e
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa22h ago0x05c1b4…001680
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa22h ago0xdea506…661ee7
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa23h ago0x1ef4a1…1aee61
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa1d ago0xda05e7…45a5a9
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa1d ago0xcbbfb2…711c51
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa1d ago0x720e40…0e725b
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa1d ago0x98ae9a…30c5b7
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa1d ago0x32446d…9a3f2b
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa1d ago0x4a0e43…822e8b
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa1d ago0x9e6064…c75983
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa1d ago0x365aca…dbc318
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa1d ago0x80c43b…183a8a
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa1d ago0xaef103…023216

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

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

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: 0x353c…cafe

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