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.43M Roundhouse has indexed across 1,401,742 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%daydreams323d ago0xd1d5b8…de38d8
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams323d ago0x3f5cb8…ff7d15
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams323d ago0x078083…0e2fa3
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams323d ago0x06cb8d…6223e2
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams323d ago0x832f98…6875c3
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams323d ago0xee7fb4…bf760f
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams324d ago0x42f237…d40225
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams324d ago0x7e0ff0…fef030
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams324d ago0x8df60f…727db9
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams324d ago0x3b9dc5…167535
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams324d ago0xac4027…4a18ae
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams324d ago0xc150fe…47f2d5
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams324d ago0x31ac39…b28982
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams324d ago0x26cb07…8ada73
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams324d ago0x863da5…342f56
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams324d ago0x00f72f…e72d79
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams325d ago0x11b34f…67e80d
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams325d ago0x4e1ac8…18d63e
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams325d ago0x374fdc…db498b
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams325d ago0x38d9fa…4cbf6f
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams325d ago0x0ebe7b…4a7ce6
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams325d ago0x2613e7…6f0570
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams325d ago0xd563f8…aae447
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams325d ago0x0a22c0…a0c9ce
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams325d ago0xc74f08…ad7133

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.