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,443 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%fluxa38d ago0xee6fc1…8a1319
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa38d ago0xdece22…f3f32e
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa38d ago0x8217ab…2e5af1
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa38d ago0x41b718…898482
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa38d ago0x438ebf…1e206d
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa38d ago0x42ac12…af906e
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa38d ago0x4f0ebc…e806ae
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa38d ago0x989fc7…619ff2
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa38d ago0x76313f…6eff80
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa38d ago0x63b6a0…794ce5
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa38d ago0x442e2f…d5b556
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa38d ago0x33234a…299374
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa38d ago0x6f17f5…7fd399
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa38d ago0x679e58…abd8da
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa38d ago0x650166…5ffe97
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa38d ago0x2fa2fb…b4b388
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa40d ago0x1ac874…acd522
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa41d ago0x67eff0…8fa03e
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa42d ago0x9c9ac0…eb369b
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa42d ago0x38553b…c39ac4
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa42d ago0x9fa4e7…7da60b
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa42d ago0x2dac41…6a3745
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa42d ago0xacb949…b3af8b
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa42d ago0x58dc9b…f4e757
0xffec…fc020xfe80…47eeBaseBase$0.001100%fluxa42d ago0x98c1e3…118236

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.