AgentReport

0x0837…0112

0x0837eb9da45cef7fa5cc368110ce12d8671b0112Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
265
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,402,228 wallets — less than 0.0001% of it.

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

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

$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
    265 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.00265276d 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 265 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams348d ago0x430be8…b9fcd7
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams348d ago0xa7588f…3e14e9
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams348d ago0x3b919f…825436
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams348d ago0xacaa54…424dbc
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams348d ago0x0dea16…216549
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams349d ago0x2318df…64f9e9
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams349d ago0xa62e95…b546d3
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams349d ago0x1399aa…82647f
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams349d ago0xfee578…279452
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams349d ago0x067756…fcbc35
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams349d ago0xe45501…659142
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams349d ago0xb7caa2…728539
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams350d ago0x501531…c2750a
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams350d ago0xeef12b…b9380b
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams350d ago0xcee1e0…c59c84
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams350d ago0xc60165…cda581
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams351d ago0x4f054c…47e606
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams351d ago0xe5df28…7b2f44
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams351d ago0x01f814…aa713f
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams351d ago0x65c8f0…9144fa
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams351d ago0xd02542…a97486
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams352d ago0xf47cfa…fc23b3
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams352d ago0x93394a…ddfea5
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams352d ago0xf40780…d6af4b
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams352d ago0x6e78f9…7f4119

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

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

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: 0x0837…0112

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