AgentReport

0x354c…e348

0x354c7cf13980a73af5d745a4ee6a5c838118e348Explorer
Paid out
$0.43
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
434
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.43 of the $3196.35M Roundhouse has indexed across 1,436,376 wallets — less than 0.0001% of it.

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

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

$0.43 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 94d ago
    $0.37
    369 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 94d ago
    $0.07
    65 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
0x9c95…e299$0.37$0.0036994d agoGraph
0xfe80…47ee$0.07$0.006594d agoGraph

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

Data quality

85% of observed volume is with a single counterparty, in all 434 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x354c…e3480x9c95…e299BaseBase$0.001100%fluxa107d ago0xeb5d98…72a92e
0x354c…e3480x9c95…e299BaseBase$0.001100%fluxa107d ago0x8a3326…38282d
0x354c…e3480x9c95…e299BaseBase$0.001100%fluxa107d ago0xb4aab8…00bea9
0x354c…e3480x9c95…e299BaseBase$0.001100%fluxa107d ago0x7fd7f3…643ad8
0x354c…e3480x9c95…e299BaseBase$0.001100%fluxa107d ago0x95e1cc…ba0f2d
0x354c…e3480x9c95…e299BaseBase$0.001100%fluxa107d ago0x13e4a8…372f16
0x354c…e3480x9c95…e299BaseBase$0.001100%fluxa107d ago0x37c03a…c9e763
0x354c…e3480x9c95…e299BaseBase$0.001100%fluxa107d ago0x1b4a5f…d8a995
0x354c…e3480x9c95…e299BaseBase$0.001100%fluxa107d ago0xf31c22…246a26
0x354c…e3480x9c95…e299BaseBase$0.001100%fluxa107d ago0xfa2fee…b24243
0x354c…e3480x9c95…e299BaseBase$0.001100%fluxa107d ago0xe22ff0…66d8a9
0x354c…e3480x9c95…e299BaseBase$0.001100%fluxa107d ago0x16be24…9cfadf
0x354c…e3480x9c95…e299BaseBase$0.001100%fluxa107d ago0xb314e3…b92b3f
0x354c…e3480x9c95…e299BaseBase$0.001100%fluxa107d ago0x2836a6…bc8a1c
0x354c…e3480x9c95…e299BaseBase$0.001100%fluxa107d ago0xa928f7…ac0684
0x354c…e3480x9c95…e299BaseBase$0.001100%fluxa107d ago0x93fbed…b103ad
0x354c…e3480x9c95…e299BaseBase$0.001100%fluxa107d ago0xac05e2…1aafee
0x354c…e3480x9c95…e299BaseBase$0.001100%fluxa107d ago0xf1665a…8622d3
0x354c…e3480x9c95…e299BaseBase$0.001100%fluxa107d ago0x79ea4a…397437
0x354c…e3480x9c95…e299BaseBase$0.001100%fluxa107d ago0xe1392d…fe2216
0x354c…e3480x9c95…e299BaseBase$0.001100%fluxa107d ago0x42b555…164b39
0x354c…e3480x9c95…e299BaseBase$0.001100%fluxa107d ago0xa2ee99…d5e749
0x354c…e3480x9c95…e299BaseBase$0.001100%fluxa107d ago0x34cb73…82d3f0
0x354c…e3480x9c95…e299BaseBase$0.001100%fluxa107d ago0x090cac…7c7508
0x354c…e3480x9c95…e299BaseBase$0.001100%fluxa107d ago0x670689…e8e939

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

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

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: 0x354c…e348

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