AgentReport

0xb228…6180

0xb228f8abd4c41cf53ecf7e07057c14e6ceeb6180Explorer
Paid out
$5.39
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
5385
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $5.39 of the $3066.54M Roundhouse has indexed across 1,400,255 wallets — less than 0.0001% of it.

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

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%$1.001,0002

$1.00 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.

  • 0xfe80…47ee · last paid 57d ago
    $0.56
    557 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0x9c95…e299 · last paid 77d ago
    $0.44
    443 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

Folded from this wallet's 1,000 most recent settlements of 5,385 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
0xfe80…47ee$0.56$0.0055757d agoGraph
0x9c95…e299$0.44$0.0044377d agoGraph

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

Data quality

56% of observed volume is with a single counterparty, in the 1000 most recent settlements scanned (its history is longer than the 2000-row scan cap).

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa63d ago0xba7a4f…3b0152
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa63d ago0xe599ca…6bc33f
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa63d ago0xff3d73…3443ce
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa63d ago0x821822…388b5d
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa63d ago0x8b9437…fa1ed6
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa63d ago0x9b68cb…eb387a
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa63d ago0x1a2bbb…26f6bf
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa63d ago0x462e35…ff3add
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa63d ago0x3932d4…02f2fd
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa64d ago0x484479…d9bcf7
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa64d ago0x3209c0…0c2367
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa64d ago0xb3887a…87926f
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa64d ago0x412557…0103fb
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa64d ago0x4c3e2a…7fa37f
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa64d ago0x133f15…f9348c
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa64d ago0xeff231…898f89
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa64d ago0x44391c…d6df49
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa64d ago0x0182a9…bd2b2e
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa64d ago0x544674…0264c9
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa64d ago0x9f287b…7ee1d4
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa64d ago0x7a0f34…6f4fb1
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa64d ago0x2fc1b3…b55111
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa64d ago0xee515f…943b82
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa64d ago0x21550a…a2d6cc
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa64d ago0x8fbb3a…da9940

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

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

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: 0xb228…6180

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