AgentReport

0x162cbb7eaece2d783b15c6aa4bf7522cce4e7b32

0x162cbb7eaece2d783b15c6aa4bf7522cce4e7b32Explorer
Paid out
$0.04
Last 7d vs prior 7d
Received
$0.04
Last 7d vs prior 7d
Settlements
2
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.04 of the $258.35M Roundhouse has indexed across 712,918 walletsless than 0.0001% of it.

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

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

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

  • 0xfce5…3c66 · last paid 111d ago
    $0.04
    1 call

    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
0xfce5…3c66$0.04$0.001111d agoGraph
0xb90a…9ae4$0.00$0.041111d agoGraph

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

Data quality

50% of observed volume is with a single counterparty, in all 2 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x162c…7b320xfce5…3c66Base$0.04100%fluxa111d ago0x642064…1318d4
0xb90a…9ae40x162c…7b32Base$0.04100%fluxa111d ago0x933952…9e6b85

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

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

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: 0x162cbb7eaece2d783b15c6aa4bf7522cce4e7b32

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