AgentReport

0xe2be…b571

0xe2befa4a4d02d732491884568a76d2e361d1b571Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
266
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3066.54M Roundhouse has indexed across 1,400,255 wallets — less than 0.0001% of it.

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

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

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

  • 0x6482…b779 · last paid 276d ago
    $0.03
    266 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
0x6482…b779$0.03$0.00266276d agoGraph

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

Data quality

100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 266 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams337d ago0x082c59…b93a61
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams337d ago0xf019a3…198dd7
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams337d ago0x4ea9e4…0ef5e7
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams337d ago0x1ac091…4df014
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams337d ago0xa9c4e5…45a7c4
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams337d ago0xc73b07…42cde4
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams337d ago0x32ec4a…d57ad4
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams337d ago0x442a07…90b7cf
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams337d ago0x5c144d…cb4c30
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams338d ago0x3a42bc…034aa8
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams338d ago0x640eb6…d176f4
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams339d ago0x25abd9…19c1f5
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams339d ago0x6e1c08…1b4d7f
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams339d ago0x97fd21…b0eb2b
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams339d ago0xc40265…fe947f
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams339d ago0x7eacf1…56becc
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams339d ago0xea6630…8b4d07
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams339d ago0x7db47b…2cfa4b
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams339d ago0x959b17…c32f4e
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams340d ago0x157a4b…b3378a
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams340d ago0xdae9db…da355d
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams340d ago0x67e50d…1cfdce
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams340d ago0xe05d95…ebcefc
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams340d ago0xffd9a0…f0c78b
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams340d ago0x1f0f8b…da1961

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

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

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: 0xe2be…b571

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