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%daydreams345d ago0xc6c449…9f4f5f
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams345d ago0x7ead88…1a8374
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams345d ago0x5e5291…cea874
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams345d ago0xb0f61b…88b19a
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams345d ago0xfae7c9…7f8053
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams345d ago0x29246c…75517e
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams346d ago0xb13455…ddf27a
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams346d ago0xe7c7b8…86cd5d
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams346d ago0x5f86d4…893982
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams346d ago0xabfc2c…5e6e7c
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams346d ago0x04e6fd…3cce54
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams346d ago0xf4e84d…7f6e19
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams346d ago0x072a5b…7095f7
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams346d ago0xc6e61e…55a68a
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams346d ago0xffbe04…b9648a
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams346d ago0x886578…010617
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams347d ago0xe62626…4998a7
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams347d ago0x930c4d…92d800
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams347d ago0xb13cf2…1d9993
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams347d ago0xaf418f…60eb2c
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams347d ago0x5c4d11…bb5efc
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams348d ago0xd928e2…4d5978
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams348d ago0xb99b88…e08c52
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams348d ago0x1e54de…fc2fa3
0x7521…bdea0x6482…b779BaseBase$0.0001100%daydreams348d ago0x46bc03…7ad3bb

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.