AgentReport

0x1609f27e6288609389e4379b9f7dd85de8654dbe

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

Paid $0.10 of the $260.32M Roundhouse has indexed across 716,001 wallets — less 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.1011

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

  • 0xb2cd…f214 · last paid 107d ago
    $0.10
    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
0xb2cd…f214$0.10$0.001107d agoGraph
0xd1ae…8133$0.00$0.101115d 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
0x1609…4dbe0xb2cd…f214Base$0.10100%fluxa107d ago0xef0732…ce11cd
0xd1ae…81330x1609…4dbeBase$0.10100%fluxa115d ago0x31cd06…9c9def

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

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

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

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