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.17M Roundhouse has indexed across 1,400,092 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%daydreams323d ago0x987bbb…0449a2
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams323d ago0xb7f89f…bb0ea3
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams323d ago0x071fdd…e48607
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams323d ago0x60091a…719c17
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams323d ago0x5bca2c…7aa04f
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams323d ago0xd16d49…05ad18
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams323d ago0x798b5f…4fa0da
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams323d ago0xb7973b…980390
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams324d ago0x0cb549…f2cdda
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams324d ago0xfefce9…9d12c6
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams324d ago0x748d3d…67af98
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams324d ago0x89523e…856fd5
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams324d ago0xe2a5d0…6239e2
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams324d ago0xaf34d3…f1d496
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams324d ago0xbff986…893771
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams324d ago0x0e319f…dafc33
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams324d ago0xa37a38…3c6c67
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams324d ago0x559411…a9a982
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams324d ago0xe5851a…7d1614
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams324d ago0xbdf275…08f5d3
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams325d ago0x192d47…3d0caa
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams325d ago0x92b4e9…ea654d
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams325d ago0xd54317…8bedec
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams325d ago0x43df6c…70e838
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams325d ago0x634f6d…b558f2

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.