AgentReport

0xfe08b2eb7922a95e79896ef58e58cb97576c59b5

0xfe08b2eb7922a95e79896ef58e58cb97576c59b5Explorer
Paid out
$3.33
Last 7d vs prior 7d
Received
$0.30
Last 7d vs prior 7d
Settlements
4
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $3.33 of the $3217.31M Roundhouse has indexed across 1,445,645 wallets — less than 0.0001% of it.

Whole-history totals from the index rollup, which can be up to 30 minutes behind.

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

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%$3.3331

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

  • 0xb447…f7d0 · last paid 163d ago
    $3.33
    3 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
0xb447…f7d0$3.33$0.003163d agoGraph
0xd1ae…8133$0.00$0.301168d agoGraph

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

Data quality

92% of observed volume is with a single counterparty, in all 4 observed settlements.

Organic volume $3.63 of $3.63 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xfe08…59b50xb447…f7d0BaseBase$1.03100%fluxa163d ago0xaf4f82…c25051
0xfe08…59b50xb447…f7d0BaseBase$2.00100%fluxa163d ago0xe0446e…82f9fe
0xfe08…59b50xb447…f7d0BaseBase$0.30100%fluxa168d ago0xb8baf3…4b6487
0xd1ae…81330xfe08…59b5BaseBase$0.30100%fluxa168d ago0xf48030…4799d4

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

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

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

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