AgentReport

0x8bea…3325

0x8beae44a1007bab5c9228d9c8a1ad4a504033325Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
260
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 (260)

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

$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
    260 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.00260276d 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 260 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x8bea…33250x6482…b779BaseBase$0.0001100%daydreams326d ago0x0152da…aa9f31
0x8bea…33250x6482…b779BaseBase$0.0001100%daydreams326d ago0x280ce6…7fe2fc
0x8bea…33250x6482…b779BaseBase$0.0001100%daydreams326d ago0x7a2ea8…29e5b3
0x8bea…33250x6482…b779BaseBase$0.0001100%daydreams326d ago0x41a473…187310
0x8bea…33250x6482…b779BaseBase$0.0001100%daydreams326d ago0x985af9…08d020
0x8bea…33250x6482…b779BaseBase$0.0001100%daydreams326d ago0x568411…4cbd29
0x8bea…33250x6482…b779BaseBase$0.0001100%daydreams326d ago0x7d9e69…e9f355
0x8bea…33250x6482…b779BaseBase$0.0001100%daydreams326d ago0x2352bf…9588fa
0x8bea…33250x6482…b779BaseBase$0.0001100%daydreams326d ago0xcb7333…908415
0x8bea…33250x6482…b779BaseBase$0.0001100%daydreams326d ago0x473dee…d2508b
0x8bea…33250x6482…b779BaseBase$0.0001100%daydreams327d ago0xa71dea…024477
0x8bea…33250x6482…b779BaseBase$0.0001100%daydreams327d ago0x964532…8253a7
0x8bea…33250x6482…b779BaseBase$0.0001100%daydreams327d ago0x93a850…856b0f
0x8bea…33250x6482…b779BaseBase$0.0001100%daydreams327d ago0x171ae1…695e13
0x8bea…33250x6482…b779BaseBase$0.0001100%daydreams327d ago0x6065ce…46e13b
0x8bea…33250x6482…b779BaseBase$0.0001100%daydreams327d ago0xb82c84…473ee5
0x8bea…33250x6482…b779BaseBase$0.0001100%daydreams327d ago0xed2faf…7ea791
0x8bea…33250x6482…b779BaseBase$0.0001100%daydreams327d ago0x35e6c5…42aad4
0x8bea…33250x6482…b779BaseBase$0.0001100%daydreams335d ago0xc04b8e…236be8
0x8bea…33250x6482…b779BaseBase$0.0001100%daydreams337d ago0xca12b2…07f289
0x8bea…33250x6482…b779BaseBase$0.0001100%daydreams337d ago0x2f7bc5…e37182
0x8bea…33250x6482…b779BaseBase$0.0001100%daydreams337d ago0x84ec8b…810588
0x8bea…33250x6482…b779BaseBase$0.0001100%daydreams337d ago0x3fa5ae…6e065e
0x8bea…33250x6482…b779BaseBase$0.0001100%daydreams337d ago0xf1c28c…3374fa
0x8bea…33250x6482…b779BaseBase$0.0001100%daydreams337d ago0xe10b80…653e42

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

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

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: 0x8bea…3325

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