AgentReport

0x353c…cafe

0x353c9314d42341d62b5e807bc1362d18081fcafeExplorer
Paid out
$0.34
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
344
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.34 of the $258.47M Roundhouse has indexed across 713,069 walletsless than 0.0001% of it.

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

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

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

  • 0x9c95…e299 · last paid 35d 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.

  • 0xfe80…47ee · last paid 34d ago
    $0.16
    159 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
0x9c95…e299$0.19$0.0018535d agoGraph
0xfe80…47ee$0.16$0.0015934d agoGraph

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

Data quality

54% of observed volume is with a single counterparty, in all 344 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x353c…cafe0xfe80…47eeBase$0.001100%fluxa34d ago0x2d56de…c94cb7
0x353c…cafe0xfe80…47eeBase$0.001100%fluxa34d ago0x87b66c…0b0436
0x353c…cafe0xfe80…47eeBase$0.001100%fluxa34d ago0x96da27…d9410d
0x353c…cafe0xfe80…47eeBase$0.001100%fluxa34d ago0x6fec5c…82a341
0x353c…cafe0xfe80…47eeBase$0.001100%fluxa34d ago0x3680da…f88677
0x353c…cafe0xfe80…47eeBase$0.001100%fluxa34d ago0x8f8143…8ee236
0x353c…cafe0xfe80…47eeBase$0.001100%fluxa34d ago0x46d97e…2aa4e9
0x353c…cafe0xfe80…47eeBase$0.001100%fluxa34d ago0xfd2a94…38eac5
0x353c…cafe0xfe80…47eeBase$0.001100%fluxa34d ago0x6b98a8…32fc9d
0x353c…cafe0xfe80…47eeBase$0.001100%fluxa34d ago0x95552f…80c0e5
0x353c…cafe0xfe80…47eeBase$0.001100%fluxa34d ago0x068c56…6e80c2
0x353c…cafe0xfe80…47eeBase$0.001100%fluxa34d ago0x018d3e…409049
0x353c…cafe0xfe80…47eeBase$0.001100%fluxa34d ago0x475744…f4e272
0x353c…cafe0xfe80…47eeBase$0.001100%fluxa35d ago0x92773e…f6b93d
0x353c…cafe0xfe80…47eeBase$0.001100%fluxa35d ago0x91788b…84e924
0x353c…cafe0xfe80…47eeBase$0.001100%fluxa35d ago0x6131d4…c20411
0x353c…cafe0xfe80…47eeBase$0.001100%fluxa35d ago0x12e20d…f7e262
0x353c…cafe0xfe80…47eeBase$0.001100%fluxa35d ago0xebd0b3…54b174
0x353c…cafe0xfe80…47eeBase$0.001100%fluxa35d ago0x133d0b…c0a8d8
0x353c…cafe0xfe80…47eeBase$0.001100%fluxa35d ago0x47f53a…7f01ef
0x353c…cafe0xfe80…47eeBase$0.001100%fluxa35d ago0x961d35…8a71e9
0x353c…cafe0xfe80…47eeBase$0.001100%fluxa35d ago0x3d0ca5…57e6f2
0x353c…cafe0xfe80…47eeBase$0.001100%fluxa35d ago0xc7424a…8d0a55
0x353c…cafe0xfe80…47eeBase$0.001100%fluxa35d ago0xb11a13…0c7619
0x353c…cafe0xfe80…47eeBase$0.001100%fluxa35d ago0x4e34f1…18270a

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