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.10M Roundhouse has indexed across 1,405,259 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%fluxa37d ago0xa67588…64f33e
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa37d ago0x31f779…836c6e
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa37d ago0x7048e3…0ef77b
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa37d ago0xd88331…dae366
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa37d ago0x1cf234…67b2e7
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa37d ago0xa5b9c9…9500a9
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa37d ago0x10f31b…f22247
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa37d ago0x2b6471…668ead
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa37d ago0xdd657d…747639
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa37d ago0x0491ec…9adfc9
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa37d ago0x7708c6…6b573b
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa37d ago0x5df0cd…d1fbdb
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa37d ago0x4218e2…6a7a79
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa37d ago0x7c5c04…461204
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa38d ago0x11ab57…36b385
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa38d ago0x1d354c…6a8ba1
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa38d ago0x29c77c…afeba6
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa38d ago0x8640d3…1cd442
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa38d ago0xfddc59…0c58a0
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa38d ago0x5d8cf0…00948f
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa38d ago0x1dafdb…05a69f
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa38d ago0x2b7511…2dedb0
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa38d ago0xce7243…f95ac8
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa38d ago0xb29e53…8ef522
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa38d ago0xc57c97…e64d44

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.