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 $3061.41M Roundhouse has indexed across 1,398,667 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 150d 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 321d 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 112d 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 321d 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 112d 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 322d 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 322d 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 322d 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.005283d agoGraph
0xccc8…15be$84.95$0.003150d agoGraph
0x94d0…f73c$18.15$0.00378321d agoGraph
0x9c3f…5fb7$7.92$0.001112d agoGraph
0x40fd…e4f5$0.00$5.001475d agoGraph
0xef98…ac29$2.82$0.00237321d agoGraph
0x4944…4bf3$0.81$0.00376112d agoGraph
0x4776…6e1b$0.12$0.002322d 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…d14d0x94d0…f73cBaseBase$0.03100%questflow321d ago0x7aeb86…7affa0
0xe5fb…d14d0x94d0…f73cBaseBase$0.01100%questflow321d ago0x5a39a8…e5c648
0xe5fb…d14d0x4944…4bf3BaseBase$0.001336100%questflow321d ago0x51ac76…935e5d
0xe5fb…d14d0x94d0…f73cBaseBase$0.03100%questflow321d ago0x85efda…6ab8a4
0xe5fb…d14d0xef98…ac29BaseBase$0.02100%questflow321d ago0x7a9cb2…07c304
0xe5fb…d14d0xef98…ac29BaseBase$0.00985100%questflow321d ago0x80a20b…7c1113
0xe5fb…d14d0x4944…4bf3BaseBase$0.001627100%questflow321d ago0x20b58e…59d0d2
0xe5fb…d14d0x94d0…f73cBaseBase$0.03100%questflow321d ago0xdea907…10909b
0xe5fb…d14d0x4944…4bf3BaseBase$0.001327100%questflow321d ago0x37bafc…1d89c7
0xe5fb…d14d0x94d0…f73cBaseBase$0.01100%questflow321d ago0xb1e251…5f850a
0xe5fb…d14d0x4944…4bf3BaseBase$0.00037100%questflow321d ago0x387fca…ec79a7
0xe5fb…d14d0x94d0…f73cBaseBase$0.01100%questflow321d ago0xa0ea72…cdcfb6
0xe5fb…d14d0x4944…4bf3BaseBase$0.002503100%questflow321d ago0x2e7bc3…f3524a
0xe5fb…d14d0x94d0…f73cBaseBase$0.03100%questflow321d ago0xc0b837…1b162d
0xe5fb…d14d0x4944…4bf3BaseBase$0.001347100%questflow321d ago0x35a17c…f65e80
0xe5fb…d14d0x94d0…f73cBaseBase$0.03100%questflow321d ago0x2c5b00…cd5d59
0xe5fb…d14d0x4944…4bf3BaseBase$0.001357100%questflow321d ago0x652ae3…4ac972
0xe5fb…d14d0x4944…4bf3BaseBase$0.001328100%questflow321d ago0x591352…ad5b76
0xe5fb…d14d0xef98…ac29BaseBase$0.00985100%questflow321d ago0x79291d…86bbea
0xe5fb…d14d0x94d0…f73cBaseBase$0.03100%questflow321d ago0x2b541c…c4c726
0xe5fb…d14d0xef98…ac29BaseBase$0.00985100%questflow321d ago0x2c0602…0fb476
0xe5fb…d14d0x4944…4bf3BaseBase$0.001333100%questflow321d ago0xde40bf…22d7b6
0xe5fb…d14d0xef98…ac29BaseBase$0.00985100%questflow321d ago0xd6dc4c…76e553
0xe5fb…d14d0x94d0…f73cBaseBase$0.03100%questflow321d ago0x523757…5c841f
0xe5fb…d14d0x94d0…f73cBaseBase$0.01100%questflow321d ago0x79eddc…290f99

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.