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%fluxa64d ago0x0c947f…b886df
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa64d ago0xe9053e…b2a15b
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa64d ago0x754379…1eaffc
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa64d ago0xf974c0…15b454
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0x9ab7c6…b4cecd
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0xda8364…7626bb
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0xfeb075…b83fe6
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0x18ee4c…64468e
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0xa0d18f…8055db
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0xd0a360…073dc2
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0xbc5a71…e4649f
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0x625cfd…5589d7
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0xd23d89…13ce6c
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0x024d27…20b71b
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0x47ca24…2a4066
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0x392643…fe5377
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0x06a79a…69f094
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0x394543…48f472
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0x2c3c54…f35c0b
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0x839660…685124
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0x0ba6dd…0463a3
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0x5c6d23…99877f
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0x38c188…07a7c0
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0xc3255c…dac1ea
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa65d ago0x03f69a…8c179a

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.