AgentReport

0x7521…bdea

0x7521576cd9bfa7efa2f3c99518f5d9ea9cfabdeaExplorer
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.54M Roundhouse has indexed across 1,400,255 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
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams352d ago0x358621…719e49
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams352d ago0x6cdc47…1704ee
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams352d ago0xa515de…5b3704
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams352d ago0xa26ddf…0d09be
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams352d ago0x9d6a29…e5e3a5
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams352d ago0x798971…fdda96
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams352d ago0x2beef2…8e56f9
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams352d ago0x681a60…16cb51
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams353d ago0x46953d…35e99e
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams353d ago0x5c9c64…c350a1
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams353d ago0x33b8d0…546508
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams354d ago0x44427d…c348b6
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams354d ago0xa2cec3…d50a89
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams355d ago0xc2c50f…0633b0
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams355d ago0xfd0723…6bf3c5
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams355d ago0xa0f1c9…f9e66a
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams355d ago0xb4d3ae…6137f8
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams355d ago0xd0ee8e…b22a97
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams356d ago0x01fd73…6f61f7
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams356d ago0xb3d6f7…ad70cd
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams356d ago0xdbf443…063003
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams356d ago0xf834e3…042293
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams356d ago0xa6c2a9…83741f
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams356d ago0xbfc5fa…518ea2
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams357d ago0xd47a96…f03652

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

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

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: 0x7521…bdea

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