AgentReport

0xb08e…c8d3

0xb08e38b75e34e5365bad52b1d01c260af4edc8d3Explorer
Paid out
$0.003216
Last 7d vs prior 7d
Received
$0.000648
Last 7d vs prior 7d
Settlements
3
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.003216 of the $835.35M Roundhouse has indexed across 1,305,110 wallets — less than 0.0001% of it.

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

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

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

  • 0x3577…ca8d · last paid 16d ago
    $0.003216
    1 call

    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

AprMayJunJulAugSepOct
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x3577…ca8d$0.003216$0.00116d agoGraph
0xef63…4acc$0.00$0.0006482342d agoGraph

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

Data quality

83% of observed volume is with a single counterparty, in all 3 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xb08e…c8d30x3577…ca8dBase$0.00321670%0x642b…6c7516d ago0x6f7498…4674e6
0xef63…4acc0xb08e…c8d3Base$0.000335100%questflow342d ago0x66bc31…1e69fd
0xef63…4acc0xb08e…c8d3Base$0.000313100%questflow345d ago0xb76780…4307bd

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

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

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: 0xb08e…c8d3

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