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,510 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%daydreams352d ago0x25be6f…86f5ea
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams352d ago0x0e5965…6c8ddb
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams352d ago0x2d77d6…eb184a
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams352d ago0x5dd826…ca553d
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams352d ago0x47ef5f…68a4b0
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams352d ago0x144e0d…234caa
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams353d ago0x9ea693…14f53c
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams353d ago0x15eb96…c2c71c
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams353d ago0x371bca…2290d1
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams354d ago0xc30827…b028db
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams354d ago0x668aa9…cf94f7
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams354d ago0xd28a38…747cc6
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams355d ago0x6eb619…e7db2f
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams355d ago0x4d6503…bf99f3
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams355d ago0x6ab94a…10b93b
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams355d ago0xda1866…eb984f
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams355d ago0x99e7b0…944675
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams355d ago0xc24170…0b0600
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams355d ago0xe0912c…96f3a9
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams356d ago0xd0f133…b48a58
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams356d ago0x2ed494…2fd2a5
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams356d ago0xbd7fb3…7ec626
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams356d ago0xd8e2ac…63d407
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams356d ago0x02c675…5cfee2
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams356d ago0x879c67…71add2

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.