AgentReport

0xfe54…ed68

0xfe54880d6bc6a51ff34de18aaaa14dd44a06ed68Explorer
Paid out
$0.91
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
912
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.91 of the $3196.35M Roundhouse has indexed across 1,436,376 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (912)

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.919122

$0.91 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 25d ago
    $0.82
    817 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 80d ago
    $0.10
    95 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.82$0.0081725d agoGraph
0x9c95…e299$0.10$0.009580d agoGraph

Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.

Data quality

90% of observed volume is with a single counterparty, in all 912 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xfe54…ed680xfe80…47eeBaseBase$0.001100%fluxa27d ago0xad173c…ab443b
0xfe54…ed680xfe80…47eeBaseBase$0.001100%fluxa27d ago0x694d67…0fec55
0xfe54…ed680xfe80…47eeBaseBase$0.001100%fluxa27d ago0xfaca22…1ee676
0xfe54…ed680xfe80…47eeBaseBase$0.001100%fluxa28d ago0xe4a911…bb4333
0xfe54…ed680xfe80…47eeBaseBase$0.001100%fluxa28d ago0xc8d329…d2b336
0xfe54…ed680xfe80…47eeBaseBase$0.001100%fluxa28d ago0x6d6b5d…5c4025
0xfe54…ed680xfe80…47eeBaseBase$0.001100%fluxa28d ago0xd0f2f4…fb07e3
0xfe54…ed680xfe80…47eeBaseBase$0.001100%fluxa28d ago0xc781f7…76015c
0xfe54…ed680xfe80…47eeBaseBase$0.001100%fluxa28d ago0x98e2a8…69e082
0xfe54…ed680xfe80…47eeBaseBase$0.001100%fluxa28d ago0xa57de2…ce3958
0xfe54…ed680xfe80…47eeBaseBase$0.001100%fluxa28d ago0x55a67c…74d3c9
0xfe54…ed680xfe80…47eeBaseBase$0.001100%fluxa28d ago0x8bc5fe…cceaa5
0xfe54…ed680xfe80…47eeBaseBase$0.001100%fluxa28d ago0x886124…633f5e
0xfe54…ed680xfe80…47eeBaseBase$0.001100%fluxa28d ago0x0d1821…cadcda
0xfe54…ed680xfe80…47eeBaseBase$0.001100%fluxa28d ago0xd5a260…ddee07
0xfe54…ed680xfe80…47eeBaseBase$0.001100%fluxa28d ago0xdbcb30…c04776
0xfe54…ed680xfe80…47eeBaseBase$0.001100%fluxa29d ago0x9f06c7…772a2a
0xfe54…ed680xfe80…47eeBaseBase$0.001100%fluxa29d ago0xbdd0ef…c13bb5
0xfe54…ed680xfe80…47eeBaseBase$0.001100%fluxa29d ago0x6ada99…a4f280
0xfe54…ed680xfe80…47eeBaseBase$0.001100%fluxa29d ago0x1e89e1…eca6db
0xfe54…ed680xfe80…47eeBaseBase$0.001100%fluxa29d ago0xb22ff2…84e1d7
0xfe54…ed680xfe80…47eeBaseBase$0.001100%fluxa29d ago0x9f0a60…3b95a5
0xfe54…ed680xfe80…47eeBaseBase$0.001100%fluxa29d ago0x3b2408…a01613
0xfe54…ed680xfe80…47eeBaseBase$0.001100%fluxa29d ago0xdb1982…6b4c1d
0xfe54…ed680xfe80…47eeBaseBase$0.001100%fluxa29d ago0xd42b1a…0c7840

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 0xfe54…ed68 has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0xfe54880d6bc6a51ff34de18aaaa14dd44a06ed68

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: 0xfe54…ed68

curl -s 'https://api.roundhouseai.io/v0/agents/0xfe54880d6bc6a51ff34de18aaaa14dd44a06ed68'
curl -s 'https://api.roundhouseai.io/v0/entities/0xfe54880d6bc6a51ff34de18aaaa14dd44a06ed68/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.