AgentReport

0xfcdf…c987

0xfcdf94b20cfa8887e371d0e3bf3f9a65a80ec987Explorer
Paid out
$33.55
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
21161
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $33.55 of the $260.88M Roundhouse has indexed across 716,644 wallets — less than 0.0001% of it.

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

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.851,0002

Every merchant paid publishes at least one catalogued endpoint.

Services it paid

A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; for 2 of 2 the amount paid narrows the list to the ones listed at that price.

Folded from this wallet's 1,000 most recent settlements of 21,161 lifetime, which is as far back as one scan reaches — so every figure in this section is a floor, and the totals above are not.

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
0x0495…eed9$2.38$0.00853225d agoGraph
0x8324…fd0e$1.47$0.00147238d agoGraph

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

Data quality

62% of observed volume is with a single counterparty, in the 1000 most recent settlements scanned (its history is longer than the 2000-row scan cap).

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xfcdf…c9870x0495…eed9Base$0.10100%payAI225d ago0x8a9955…aa51b0
0xfcdf…c9870x0495…eed9Base$0.10100%payAI225d ago0xc01a16…45c788
0xfcdf…c9870x0495…eed9Base$0.10100%payAI225d ago0x8c1776…0e99b9
0xfcdf…c9870x0495…eed9Base$0.10100%payAI225d ago0x20a104…fe0b85
0xfcdf…c9870x0495…eed9Base$0.10100%payAI225d ago0x012d18…ae58e3
0xfcdf…c9870x0495…eed9Base$0.10100%payAI225d ago0x4e21c1…184af5
0xfcdf…c9870x0495…eed9Base$0.10100%payAI225d ago0x33afd0…2aa98b
0xfcdf…c9870x0495…eed9Base$0.10100%payAI225d ago0x8a98db…eb64b2
0xfcdf…c9870x0495…eed9Base$0.10100%payAI225d ago0xf248fa…da90c4
0xfcdf…c9870x0495…eed9Base$0.10100%payAI225d ago0x78d66d…8fe4e5
0xfcdf…c9870x0495…eed9Base$0.10100%payAI225d ago0xb82750…90a238
0xfcdf…c9870x0495…eed9Base$0.10100%payAI225d ago0x71de41…8d07df
0xfcdf…c9870x0495…eed9Base$0.10100%payAI225d ago0xd0708a…9b8200
0xfcdf…c9870x0495…eed9Base$0.10100%payAI225d ago0x560a76…1854bf
0xfcdf…c9870x0495…eed9Base$0.10100%payAI225d ago0xf71a22…0b851b
0xfcdf…c9870x0495…eed9Base$0.10100%payAI225d ago0xd192aa…e8a683
0xfcdf…c9870x0495…eed9Base$0.10100%payAI225d ago0xc8b0a6…f38abc
0xfcdf…c9870x0495…eed9Base$0.10100%payAI225d ago0x4da551…856db0
0xfcdf…c9870x0495…eed9Base$0.10100%payAI225d ago0xfb14d2…e494ca
0xfcdf…c9870x0495…eed9Base$0.10100%payAI225d ago0x4915c4…6c3f88
0xfcdf…c9870x0495…eed9Base$0.10100%payAI225d ago0xb77abc…6f4718
0xfcdf…c9870x0495…eed9Base$0.10100%payAI225d ago0xbf3d47…de7c84
0xfcdf…c9870x0495…eed9Base$0.10100%payAI225d ago0xb847ef…4fc0be
0xfcdf…c9870x0495…eed9Base$0.0001100%payAI238d ago0x3c4284…92da2c
0xfcdf…c9870x0495…eed9Base$0.0001100%payAI238d ago0x18fd5b…9ffb00

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

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

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: 0xfcdf…c987

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