AgentReport

0xfc2e…db2d

0xfc2ef48f89101db872ae0b179fe06fdcb538db2dExplorer
Paid out
$4,953.91↓ 8.2%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
3973↓ 8.2%
Last 7d vs prior 7d
3965
Distinct counterparties
Over the whole indexed history

Paid $4,953.91 of the $3061.41M Roundhouse has indexed across 1,398,667 wallets — 0.0002% of it.

Chains (from the recent scan): Ethereum (190) · Base (810)

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%$15.001212

$15.00 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.

  • 0x62f1…b587 · last paid 9m ago
    $1.25
    1 call

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0x8a02…41c5 · last paid 10m ago
    $1.25
    1 call

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0xbed3…8bc1 · last paid 10m ago
    $1.25
    1 call

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0x9643…a1a3 · last paid 16m ago
    $1.25
    1 call

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0x3b41…0b24 · last paid 16m ago
    $1.25
    1 call

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0xeb01…216a · last paid 26m ago
    $1.25
    1 call

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0x4f02…4164 · last paid 26m ago
    $1.25
    1 call

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0x4180…4904 · last paid 27m ago
    $1.25
    1 call

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0xce1e…e095 · last paid 34m ago
    $1.25
    1 call

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0xe3e1…f742 · last paid 34m ago
    $1.25
    1 call

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0x8bac…cac2 · last paid 1h ago
    $1.25
    1 call

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0x318a…fe2a · last paid 1h ago
    $1.25
    1 call

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

Folded from this wallet's 1,000 most recent settlements of 3,973 lifetime, which is as far back as one scan reaches — so every figure in this section is a floor, and the totals above are not.

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
0x62f1…b587$1.25$0.0019m agoGraph
0x8a02…41c5$1.25$0.00110m agoGraph
0xbed3…8bc1$1.25$0.00110m agoGraph
0x9643…a1a3$1.25$0.00116m agoGraph
0x3b41…0b24$1.25$0.00116m agoGraph
0xeb01…216a$1.25$0.00126m agoGraph
0x4f02…4164$1.25$0.00126m agoGraph
0x4180…4904$1.25$0.00127m agoGraph

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

Data quality

Not enough of this address's history was examined to assess it: self_dealing and counterparty_concentration and single_counterparty were computed over the 1000 most recent settlements scanned (its history is longer than the 2000-row scan cap), so nothing found there rules anything out. This is an incomplete check, not a clean record.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xfc2e…db2d0xfdf5…642aBaseBase$1.2570%0x7e99…09884d ago0x775b63…e5aa03
0xfc2e…db2d0xdf92…4b9aBaseBase$1.2570%0x7e99…09884d ago0x948199…4ea9aa
0xfc2e…db2d0xff6b…804fBaseBase$1.2570%0x7e99…09884d ago0x418c52…6fb5a4
0xfc2e…db2d0xe05f…3dcdEthereumEthereum$1.2570%0x7e99…09884d ago0xb85e3e…d8f00d
0xfc2e…db2d0xbb0c…cecbBaseBase$1.2570%0x7e99…09884d ago0x230e60…39f525
0xfc2e…db2d0xbb01…cccfBaseBase$1.2570%0x7e99…09884d ago0x3f501a…9082ce
0xfc2e…db2d0x446c…5c48BaseBase$1.2570%0x7e99…09884d ago0x900ef2…546d96
0xfc2e…db2d0xea44…011dBaseBase$1.2570%0x7e99…09884d ago0x2b7e81…515003
0xfc2e…db2d0x63bc…e1d4EthereumEthereum$1.2570%0x7e99…09884d ago0x90d0c1…6cc29b
0xfc2e…db2d0x7a10…474dBaseBase$1.2570%0x7e99…09884d ago0x4b80e5…ec3cbd
0xfc2e…db2d0x07e9…11a4BaseBase$1.2570%0x7e99…09884d ago0xda6330…342c98
0xfc2e…db2d0xe9b4…6c95BaseBase$1.2570%0x7e99…09884d ago0x9db7c6…08e434
0xfc2e…db2d0x6e3e…751aBaseBase$1.2570%0x7e99…09884d ago0xc0f996…94f670
0xfc2e…db2d0x3cbc…8aaaEthereumEthereum$1.2570%0x7e99…09884d ago0x0badc6…da677d
0xfc2e…db2d0xec32…07c4BaseBase$1.2570%0x7e99…09884d ago0x79486d…50a371
0xfc2e…db2d0x2e79…7cc5BaseBase$1.2570%0x7e99…09884d ago0xf6f093…bb45b5
0xfc2e…db2d0xb10c…30bcBaseBase$1.2570%0x7e99…09884d ago0x72a275…503422
0xfc2e…db2d0x2173…1f24BaseBase$1.2570%0x7e99…09884d ago0xf293da…8354cb
0xfc2e…db2d0xda59…758dEthereumEthereum$1.2570%0x7e99…09884d ago0x1e2ad1…fd56ed
0xfc2e…db2d0xfc0f…7ceaBaseBase$1.2570%0x7e99…09884d ago0x565f8d…837b63
0xfc2e…db2d0x0b45…f87fBaseBase$1.2570%0x7e99…09884d ago0x22217d…d4255e
0xfc2e…db2d0x8d6a…c85bBaseBase$1.2570%0x7e99…09884d ago0xb4c29c…65132c
0xfc2e…db2d0x535d…a126BaseBase$1.2570%0x7e99…09884d ago0x74741b…414525
0xfc2e…db2d0xb5af…8f12BaseBase$1.2570%0x7e99…09884d ago0x52d649…9605f8
0xfc2e…db2d0x92f0…20a1BaseBase$1.2570%0x7e99…09884d ago0x9653a2…30c761

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

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

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: 0xfc2e…db2d

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