AgentReport

0xb2f1…0e54

0xb2f1c3beb9c4c4bb7fe8e55a9751603c2a3c0e54Explorer
Paid out
$26.63
Last 7d vs prior 7d
Received
$23.10
Last 7d vs prior 7d
Settlements
4753
Last 7d vs prior 7d
38
Distinct counterparties
Over the whole indexed history

Paid $26.63 of the $3059.45M Roundhouse has indexed across 1,397,037 wallets — less than 0.0001% of it.

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

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
Web & Content80%$6.417084
Not in any catalogue20%$1.622718

$1.62 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; for 4 of 12 the amount paid narrows the list to the ones listed at that price.

Folded from this wallet's 2,000 most recent settlements of 4,753 lifetime, which is as far back as one scan reaches — so every figure in this section is a floor, and the totals above are not.

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
0xbd34…9992$3.76$0.00376254d agoGraph
0xcce0…af8e$0.00$2.98287262d agoGraph
0x6779…9e35$0.01$2.66257258d agoGraph
0xe217…7a26$0.02$2.51243254d agoGraph
0xeb1d…abef$0.04$1.57130280d agoGraph
0xca12…cd0c$0.96$0.0032254d agoGraph
0x43a2…f758$0.91$0.00222248d agoGraph
0x7d9d…405d$0.78$0.0078248d agoGraph

Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.

Data quality

Not enough of this address's history was examined to assess it: self_dealing and counterparty_concentration and single_counterparty were computed over the 2000 most recent settlements scanned (its history is longer than the 2000-row scan cap), so nothing found there rules anything out. This is an incomplete check, not a clean record.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xb2f1…0e540x58a4…f0f0BaseBase$0.001100%payAI253d ago0x3d97ce…75e788
0xb2f1…0e540xf762…9ac0BaseBase$0.00103100%corbits253d ago0xaf5e14…bff20c
0xf762…9ac00xb2f1…0e54BaseBase$0.00103100%corbits253d ago0x9d0012…e7d533
0xb2f1…0e540x58a4…f0f0BaseBase$0.001100%payAI253d ago0x644685…2de819
0xb2f1…0e540x58a4…f0f0BaseBase$0.001100%payAI253d ago0x6d1a0b…aba839
0xb2f1…0e540x58a4…f0f0BaseBase$0.001100%payAI253d ago0x43a4b3…7a05b3
0xf762…9ac00xb2f1…0e54BaseBase$0.00103100%ultravioletadao253d ago0x1b52f7…d99e5c
0xb2f1…0e540xf762…9ac0BaseBase$0.00103100%ultravioletadao253d ago0x3ec465…b35a46
0xf762…9ac00xb2f1…0e54BaseBase$0.00103100%ultravioletadao253d ago0x407397…1a9ec3
0xb2f1…0e540x58a4…f0f0BaseBase$0.001100%payAI253d ago0xd6face…6b69fd
0xb2f1…0e540x58a4…f0f0BaseBase$0.001100%payAI253d ago0x8eda53…64588d
0xb2f1…0e540x58a4…f0f0BaseBase$0.001100%payAI253d ago0x3300fb…ae9165
0xb2f1…0e540x58a4…f0f0BaseBase$0.001100%payAI253d ago0x787c76…f14ad2
0xb2f1…0e540x58a4…f0f0BaseBase$0.001100%payAI253d ago0xfe519c…d5e00d
0xb2f1…0e540x58a4…f0f0BaseBase$0.001100%payAI253d ago0x7b13be…e16dad
0xb2f1…0e540x58a4…f0f0BaseBase$0.001100%payAI253d ago0x46367b…946a87
0xb2f1…0e540x58a4…f0f0BaseBase$0.001100%payAI253d ago0x10bab2…e51eaa
0xb2f1…0e540x58a4…f0f0BaseBase$0.001100%payAI253d ago0xf48f89…cbe8f8
0xb2f1…0e540x58a4…f0f0BaseBase$0.001100%payAI253d ago0x172d02…e5b5b7
0xb2f1…0e540x58a4…f0f0BaseBase$0.001100%payAI253d ago0x86fdfb…e95996
0xb2f1…0e540x58a4…f0f0BaseBase$0.001100%payAI253d ago0xc14c40…45974c
0xb2f1…0e540x58a4…f0f0BaseBase$0.001100%payAI253d ago0xc5dee0…f9423a
0xb2f1…0e540x58a4…f0f0BaseBase$0.001100%payAI253d ago0x658126…e03573
0xb2f1…0e540x58a4…f0f0BaseBase$0.001100%payAI253d ago0x5dbafc…bbe09a
0xb2f1…0e540x58a4…f0f0BaseBase$0.001100%payAI253d ago0xed8b1a…271a7f

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

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

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: 0xb2f1…0e54

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