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%fluxa66d ago0xcb7b0f…b80d7c
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa66d ago0xe46405…0d5c59
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa66d ago0xfee4c1…4c84d8
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa66d ago0x53943e…2640ef
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa66d ago0x7aff5f…325c1a
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa66d ago0x10512d…bc8d94
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa66d ago0x296b65…c3d895
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa66d ago0x15dd59…19a044
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa66d ago0x5f8c10…d7f481
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa66d ago0x4181e0…86cf4e
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa66d ago0x23e21a…d12a26
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa66d ago0x9e004a…8cafb9
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa66d ago0x168e6e…992d18
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa66d ago0xd5d506…42f1ab
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa66d ago0xb7b492…996609
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa66d ago0x00ce58…c97a33
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa66d ago0x75a2f3…812515
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa66d ago0x6daf08…99965f
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa82d ago0xdfcb64…4ed332
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa82d ago0x5e0ce4…d32609
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa82d ago0x1a934d…863acd
0xffec…fc020x9c95…e299BaseBase$0.001100%fluxa82d ago0xe7e726…a73bec
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa82d ago0x59395b…94d88d
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa82d ago0x43f7d9…37f912
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa82d ago0xa00459…3e0430

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.