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%daydreams352d ago0xa29eae…85b6c0
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams352d ago0x534db7…aa8f4e
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams352d ago0xac7934…cc6a9f
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams352d ago0xf3b869…8fd686
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams352d ago0x8539d1…406bc6
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams353d ago0x94b3ad…76a661
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams353d ago0xa1043b…29d43c
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams353d ago0xdb485e…711052
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams353d ago0x2d8915…0a95ca
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams353d ago0xe29163…03a1cc
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams353d ago0x515851…aa3099
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams353d ago0xb53e25…ccb0bb
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams355d ago0x201db0…fca63b
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams355d ago0x49606b…d1f1d8
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams355d ago0x19f7dd…fbabd6
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams356d ago0xd9e28e…7f1c05
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams356d ago0xeb26e7…64b1a2
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams356d ago0x5cb520…36f767
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams356d ago0xceb67a…a33f95
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams357d ago0x8dd7c3…9db933
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams357d ago0x270645…5b169b
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams357d ago0xeb9dcf…396dd2
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams357d ago0x3f1a63…6e01e1
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams357d ago0xff199c…d445ce
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams358d ago0xd59d30…c9370c

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.