AgentReport

0xe5fb…d14d

0xe5fb8378c1e3ba2d9375653f80b62ff709bfd14dExplorer
Paid out
$2,786.52
Last 7d vs prior 7d
Received
$95.00
Last 7d vs prior 7d
Settlements
102431
Last 7d vs prior 7d
39
Distinct counterparties
Over the whole indexed history

Paid $2,786.52 of the $3058.83M Roundhouse has indexed across 1,396,904 wallets — less than 0.0001% of it.

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

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%$114.921,0008

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

  • 0xccc8…15be · last paid 149d ago
    $84.95
    3 calls

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

  • 0x94d0…f73c · last paid 320d ago
    $18.15
    378 calls

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

  • 0x9c3f…5fb7 · last paid 111d ago
    $7.92
    1 call

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

  • 0xef98…ac29 · last paid 320d ago
    $2.82
    237 calls

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

  • 0x4944…4bf3 · last paid 111d ago
    $0.81
    376 calls

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

  • 0x4776…6e1b · last paid 321d ago
    $0.12
    2 calls

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

  • 0x4a7c…59f9 · last paid 321d ago
    $0.12
    1 call

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

  • 0x008e…f607 · last paid 321d ago
    $0.04
    2 calls

    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,006 most recent settlements of 102,431 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
0xfd44…431c$0.00$90.005282d agoGraph
0xccc8…15be$84.95$0.003149d agoGraph
0x94d0…f73c$18.15$0.00378320d agoGraph
0x9c3f…5fb7$7.92$0.001111d agoGraph
0x40fd…e4f5$0.00$5.001474d agoGraph
0xef98…ac29$2.82$0.00237320d agoGraph
0x4944…4bf3$0.81$0.00376111d agoGraph
0x4776…6e1b$0.12$0.002321d 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 1006 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
0xe5fb…d14d0x4944…4bf3BaseBase$0.0970%0x8ad5…80d4111d ago0x4f2aa7…9f27a2
0xe5fb…d14d0x9c3f…5fb7BaseBase$7.92100%questflow111d ago0xc31c89…128537
0xe5fb…d14d0xccc8…15beBaseBase$18.0070%0xf70d…dbef149d ago0x59528c…0cd8b1
0xe5fb…d14d0xccc8…15beBaseBase$65.0070%0xf70d…dbef149d ago0xa363a9…5a3a44
0xe5fb…d14d0xccc8…15beBaseBase$1.9570%0xf70d…dbef149d ago0x890b8e…23d3df
0xfd44…431c0xe5fb…d14dBaseBase$10.00100%questflow282d ago0x8cca5e…75c373
0xfd44…431c0xe5fb…d14dBaseBase$20.00100%questflow282d ago0xe3ead7…f0e035
0xfd44…431c0xe5fb…d14dBaseBase$20.00100%questflow286d ago0x9c4d91…93b115
0xfd44…431c0xe5fb…d14dBaseBase$20.00100%questflow288d ago0x1323dd…6318d1
0xfd44…431c0xe5fb…d14dBaseBase$20.00100%questflow288d ago0x6412b2…7cfcd4
0xe5fb…d14d0x94d0…f73cBaseBase$0.41100%questflow320d ago0x32cd2e…1e9d66
0xe5fb…d14d0x94d0…f73cBaseBase$0.27100%questflow320d ago0x6be144…81e2d2
0xe5fb…d14d0x94d0…f73cBaseBase$0.52100%questflow320d ago0x033ac1…dafd25
0xe5fb…d14d0x4944…4bf3BaseBase$0.02100%questflow320d ago0xd60a69…fa6948
0xe5fb…d14d0x94d0…f73cBaseBase$0.03100%questflow320d ago0xf3a562…f77fc9
0xe5fb…d14d0x94d0…f73cBaseBase$0.03100%questflow320d ago0xfde308…21eece
0xe5fb…d14d0x4944…4bf3BaseBase$0.001225100%questflow320d ago0xf170f4…bca3b2
0xe5fb…d14d0x4944…4bf3BaseBase$0.00135100%questflow320d ago0x0f2c6b…0b2891
0xe5fb…d14d0xef98…ac29BaseBase$0.00985100%questflow320d ago0x8e7dfc…ad9334
0xe5fb…d14d0x4944…4bf3BaseBase$0.001214100%questflow320d ago0x810106…6437b5
0xe5fb…d14d0x4944…4bf3BaseBase$0.001233100%questflow320d ago0x0fe6c5…5d620a
0xe5fb…d14d0x94d0…f73cBaseBase$0.03100%questflow320d ago0x9e8247…9e2b55
0xe5fb…d14d0xef98…ac29BaseBase$0.00985100%questflow320d ago0x843637…c61710
0xe5fb…d14d0x4944…4bf3BaseBase$0.06100%questflow320d ago0x73a564…bcb9bb
0xe5fb…d14d0x4944…4bf3BaseBase$0.05100%questflow320d ago0x19886b…2039d1

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

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

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: 0xe5fb…d14d

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