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%daydreams340d ago0xa26900…06fc83
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams340d ago0xfed9d7…3422de
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams340d ago0x72d5ec…2b050c
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams340d ago0x975247…9f31db
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams341d ago0xe0694f…056ef9
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams341d ago0x00de1c…3fe4cb
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams341d ago0x0f5add…dd076f
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams341d ago0x73d3a8…221624
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams341d ago0x806f2f…3f5492
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams341d ago0xaaf91c…9b6c5d
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams341d ago0x5b2202…65f038
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams341d ago0x435eac…f3e29b
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams341d ago0xadc0eb…0f65c3
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams342d ago0x446724…635780
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams342d ago0xccb6bc…a54636
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams342d ago0x25b656…d4f423
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams342d ago0xa16c5f…a0cf04
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams342d ago0x658bf7…89106d
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams342d ago0x41d79d…b157a7
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams342d ago0x0e4e49…eb458d
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams342d ago0x1b5d91…3f8ce6
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams342d ago0x437eb6…3d7efb
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams342d ago0x1373ec…2930de
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams343d ago0xbba3bf…ceedfe
0xe2be…b5710x6482…b779BaseBase$0.0001100%daydreams343d ago0x87c389…375ff3

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.