AgentReport

0xe5b7…eeeb

0xe5b79a67c2c4701290bc3660b0fa7f2fc85aeeebExplorer
Paid out
$0.02
Last 7d vs prior 7d
Received
$0.01
Last 7d vs prior 7d
Settlements
21
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.02 of the $844.07M Roundhouse has indexed across 1,325,104 wallets — less than 0.0001% of it.

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

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

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

  • 0x3577…ca8d · last paid 21d ago
    $0.02
    1 call

    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

AprMayJunJulAugSepOct
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x3577…ca8d$0.02$0.00121d agoGraph
0x820a…cb3b$0.00$0.0120325d agoGraph

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

Data quality

51% of observed volume is with a single counterparty, in all 21 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xe5b7…eeeb0x3577…ca8dBase$0.0270%0x642b…6c7521d ago0x98da9e…6a84ff
0x820a…cb3b0xe5b7…eeebBase$0.000306100%questflow325d ago0xd038c8…96130f
0x820a…cb3b0xe5b7…eeebBase$0.000312100%questflow326d ago0xa7d8ad…5cf770
0x820a…cb3b0xe5b7…eeebBase$0.008993100%questflow327d ago0x49ad9a…f70b7e
0x820a…cb3b0xe5b7…eeebBase$0.000114100%questflow329d ago0x5b5850…3b44ca
0x820a…cb3b0xe5b7…eeebBase$0.000061100%questflow331d ago0x6ff7dc…078d00
0x820a…cb3b0xe5b7…eeebBase$0.000073100%questflow332d ago0x5baf59…2f4e41
0x820a…cb3b0xe5b7…eeebBase$0.000054100%questflow334d ago0x852ac2…b758d6
0x820a…cb3b0xe5b7…eeebBase$0.000056100%questflow335d ago0xa106b8…8accf6
0x820a…cb3b0xe5b7…eeebBase$0.000474100%questflow340d ago0xc5d42c…b39522
0x820a…cb3b0xe5b7…eeebBase$0.000431100%questflow340d ago0x700889…52f373
0x820a…cb3b0xe5b7…eeebBase$0.000391100%questflow342d ago0x92fac7…7be643
0x820a…cb3b0xe5b7…eeebBase$0.000361100%questflow342d ago0xc8ebac…ce8199
0x820a…cb3b0xe5b7…eeebBase$0.000304100%questflow344d ago0x753a16…8f4a32
0x820a…cb3b0xe5b7…eeebBase$0.000245100%questflow344d ago0x397444…1c714e
0x820a…cb3b0xe5b7…eeebBase$0.000268100%questflow347d ago0x794761…fc8545
0x820a…cb3b0xe5b7…eeebBase$0.000285100%questflow348d ago0x691b58…8e723f
0x820a…cb3b0xe5b7…eeebBase$0.000278100%questflow349d ago0x0d5f41…ef3d6f
0x820a…cb3b0xe5b7…eeebBase$0.000282100%questflow350d ago0x75498b…8f5893
0x820a…cb3b0xe5b7…eeebBase$0.000461100%questflow352d ago0xdb9a4f…9530b9
0x820a…cb3b0xe5b7…eeebBase$0.000499100%questflow352d ago0x880e9a…ea1148

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

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

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: 0xe5b7…eeeb

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