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%daydreams325d ago0x14861a…23e12f
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams325d ago0x457ca9…2730e3
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams325d ago0xa037b9…ef62e3
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams325d ago0x16f02f…296457
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams326d ago0x0a9add…afac4e
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams326d ago0x621144…a263fb
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams326d ago0x82147f…fceeba
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams326d ago0x7cbb9d…3a1cdc
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams326d ago0x101d80…be07e5
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams326d ago0xc894cd…9595c8
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams326d ago0x2172b1…bbbc49
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams326d ago0x400530…3b0140
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams326d ago0x79ba6d…fb6b88
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams326d ago0x8d1172…4a2d1f
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams327d ago0x7ff132…8bdb40
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams327d ago0x55cbdf…78bfac
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams327d ago0x96098d…84c721
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams327d ago0xbeb755…d73bcc
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams327d ago0xdd3805…9b5978
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams327d ago0x926d1a…d5048b
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams327d ago0x15dc44…f637ef
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams327d ago0x647b83…9d0b64
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams328d ago0xebfba8…15a7e3
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams328d ago0x0af0ec…14b08c
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams335d ago0xdc56b8…cf5cdd

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.