AgentReport

0xb7bf…c53b

0xb7bff648d3933c1643034d12e237fe80cf5cc53bExplorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
262
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3067.84M Roundhouse has indexed across 1,401,919 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (262)

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

$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
    262 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.00262276d 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 262 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xb7bf…c53b0x6482…b779BaseBase$0.0001100%daydreams338d ago0x320b35…bccbd6
0xb7bf…c53b0x6482…b779BaseBase$0.0001100%daydreams338d ago0x76a098…ab4ac1
0xb7bf…c53b0x6482…b779BaseBase$0.0001100%daydreams338d ago0x888503…31858b
0xb7bf…c53b0x6482…b779BaseBase$0.0001100%daydreams338d ago0xc59172…6af2cd
0xb7bf…c53b0x6482…b779BaseBase$0.0001100%daydreams338d ago0x761b61…422278
0xb7bf…c53b0x6482…b779BaseBase$0.0001100%daydreams339d ago0x8c52b3…bde9ef
0xb7bf…c53b0x6482…b779BaseBase$0.0001100%daydreams339d ago0xecab48…f96433
0xb7bf…c53b0x6482…b779BaseBase$0.0001100%daydreams340d ago0x90cf0d…a09d10
0xb7bf…c53b0x6482…b779BaseBase$0.0001100%daydreams340d ago0x9207a1…29fb12
0xb7bf…c53b0x6482…b779BaseBase$0.0001100%daydreams340d ago0x3e7e15…e45051
0xb7bf…c53b0x6482…b779BaseBase$0.0001100%daydreams340d ago0x4fbaaa…7473a2
0xb7bf…c53b0x6482…b779BaseBase$0.0001100%daydreams340d ago0x2843d3…053c4f
0xb7bf…c53b0x6482…b779BaseBase$0.0001100%daydreams340d ago0x4457c7…070312
0xb7bf…c53b0x6482…b779BaseBase$0.0001100%daydreams340d ago0x45c2da…b6ddc5
0xb7bf…c53b0x6482…b779BaseBase$0.0001100%daydreams340d ago0x54b238…3309f0
0xb7bf…c53b0x6482…b779BaseBase$0.0001100%daydreams340d ago0xb9100f…eb794b
0xb7bf…c53b0x6482…b779BaseBase$0.0001100%daydreams340d ago0xa194ee…0bfbf1
0xb7bf…c53b0x6482…b779BaseBase$0.0001100%daydreams340d ago0xf24500…428e6b
0xb7bf…c53b0x6482…b779BaseBase$0.0001100%daydreams340d ago0x243fd3…b4e15d
0xb7bf…c53b0x6482…b779BaseBase$0.0001100%daydreams341d ago0xaedf1b…a822ec
0xb7bf…c53b0x6482…b779BaseBase$0.0001100%daydreams341d ago0xeeec24…54665e
0xb7bf…c53b0x6482…b779BaseBase$0.0001100%daydreams341d ago0x943d7e…87ee5f
0xb7bf…c53b0x6482…b779BaseBase$0.0001100%daydreams341d ago0x123857…0c115e
0xb7bf…c53b0x6482…b779BaseBase$0.0001100%daydreams341d ago0x97dd82…b78770
0xb7bf…c53b0x6482…b779BaseBase$0.0001100%daydreams341d ago0xdd3d20…224162

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

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

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: 0xb7bf…c53b

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