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 $3063.55M Roundhouse has indexed across 1,399,142 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%fluxa58d ago0x4efc69…f03e59
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa61d ago0x2b6a16…b6dd35
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa61d ago0xf04858…c08439
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa61d ago0x34a40f…6b0607
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa61d ago0xa1d7d2…5a3967
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa61d ago0x67c8dd…edd718
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa61d ago0xf8a46b…31671b
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa61d ago0x2b1736…ac1f99
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa61d ago0x97537e…5822c3
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa61d ago0x3e4985…809aab
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa61d ago0x173bb4…b034ac
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa61d ago0xb07996…f22bb2
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa61d ago0x53816f…17c459
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa61d ago0x85ee2d…cc3eab
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa61d ago0x3040aa…e38ed4
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa61d ago0xeb2fea…3e5df3
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa61d ago0x6fdbd7…4012f4
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa61d ago0x2bd4d4…e439ac
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa61d ago0x021e1f…f09e9b
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa61d ago0x5402ce…6b888e
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa61d ago0x8824c0…adf8bc
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa61d ago0xf69ec5…7204f4
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa61d ago0xb6f972…a5ff6e
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa61d ago0xed9ef4…4f119d
0xb228…61800xfe80…47eeBaseBase$0.001100%fluxa61d ago0xf4185e…3ff9af

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.