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,406,271 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%fluxa65d ago0x7a25ff…bc8681
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0x55a069…e30f85
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0x237eb6…e50c3c
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0x40c91e…d49cb2
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0x9fc80d…7ab3e7
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0x89aa09…c23682
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0x18cd39…77ab1e
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0x97512b…0af962
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0xe76159…657832
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0x1f9642…0edcd3
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0x9f61d0…84e158
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0x729185…6b4ba8
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0xc297ff…671abe
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0xb49ec9…0e2f68
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0xeea522…8fc0bf
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0xbe6150…b612cc
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0x687027…9abcc8
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0xfffadb…09db4e
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa66d ago0x20102a…c6f552
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa66d ago0xc3e809…c3cdd7
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa66d ago0x0b619c…a7a3a6
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa66d ago0xf13883…a86c7a
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa66d ago0xf81d9d…67fdf6
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa66d ago0xd050b4…7f2785
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa66d ago0x8602d9…f80f45

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.