AgentReport

0xffec…fc02

0xffec969811c684f9de3acf3b3f4d9b93a604fc02Explorer
Paid out
$0.67
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
671
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.67 of the $3105.41M Roundhouse has indexed across 1,405,967 wallets — less than 0.0001% of it.

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

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

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

  • 0xfe80…47ee · last paid 37d ago
    $0.44
    441 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0x9c95…e299 · last paid 82d ago
    $0.23
    230 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
0xfe80…47ee$0.44$0.0044137d agoGraph
0x9c95…e299$0.23$0.0023082d agoGraph

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

Data quality

66% of observed volume is with a single counterparty, in all 671 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa62d ago0xb73921…a68ea5
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa62d ago0x035f99…977c42
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa62d ago0xbb3349…784090
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa62d ago0x9a6212…e2f1c3
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa62d ago0x2e6632…f792cf
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa62d ago0xb91b82…47ef7b
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa62d ago0xb200f1…42530f
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa62d ago0x3194a4…fd8d60
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa62d ago0x7b582e…ccb2d5
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa62d ago0x458a54…1bfbdb
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa62d ago0x99b3ae…b62830
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa62d ago0x2468c2…a41543
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa62d ago0x659d08…8eeeb6
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa63d ago0x9e390b…89e793
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa63d ago0x9e74e6…d3ada9
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa63d ago0x8de09a…d08be2
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa63d ago0x55a3fa…6a449e
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa63d ago0xbf6f43…234e1a
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa63d ago0x6c110e…038185
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa63d ago0xa62bef…d4536d
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa63d ago0x15992b…4a7704
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa63d ago0xed6227…de5055
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa63d ago0xe5c15d…7a701d
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa63d ago0xe9904e…e1649f
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa63d ago0xf513ca…6e63af

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

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

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: 0xffec…fc02

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