AgentReport

0x353c…cafe

0x353c9314d42341d62b5e807bc1362d18081fcafeExplorer
Paid out
$0.99↑ 36%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
992↑ 36%
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.99 of the $3067.00M Roundhouse has indexed across 1,401,091 wallets — less than 0.0001% of it.

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

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

$0.99 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 4m ago
    $0.81
    807 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 82d 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.81$0.008074m agoGraph
0x9c95…e299$0.19$0.0018582d 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 992 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa2d ago0x567131…cab1ef
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa2d ago0xe4e4d3…2d7cb7
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa2d ago0x2435b4…82be3e
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa2d ago0xf4ce17…b1528d
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa2d ago0xececf2…dcff9e
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa2d ago0xcdd8bf…30f2b2
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa2d ago0x2a71ee…d98fc4
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa2d ago0x6a25cf…f4059e
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa2d ago0x3fbd6d…c8f147
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa2d ago0xe5ebea…10e96c
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa2d ago0x5c8352…6b00cb
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa2d ago0x71392e…cc103a
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa2d ago0xcc33f3…663034
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa3d ago0xde12a6…a869f7
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa3d ago0x036093…e1ee13
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa3d ago0x36c695…e04cc5
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa3d ago0xfbd8e1…c3f462
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa3d ago0xbb8599…b64eea
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa3d ago0x8568f0…17f5f7
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa3d ago0xdcb912…55591d
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa3d ago0x4186c4…58b363
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa3d ago0x0725e9…afa224
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa3d ago0xb8929e…30ccb7
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa3d ago0x1ed510…3a0094
0x353c…cafe0xfe80…47eeBaseBase$0.001100%fluxa3d ago0xfed6fb…e44f41

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.