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,401,919 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%daydreams343d ago0x4260f6…b58120
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams343d ago0x4b231f…a45c09
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams343d ago0xe1779a…a8ad36
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams343d ago0xb0a1e6…fc6170
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams343d ago0xb22504…6a7daa
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams344d ago0x088b45…4b6171
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams344d ago0x286fab…d91aa9
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams344d ago0x5b8487…2cf909
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams344d ago0x2b6a56…442675
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams344d ago0x26c346…301d8c
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams344d ago0xcf2907…da486c
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams344d ago0xb77d68…458a3f
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams344d ago0x245092…b338b3
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams344d ago0x8d9bdf…e93d65
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams344d ago0xf0e425…4b33d7
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams345d ago0xdebf11…dc31a4
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams345d ago0x2dab0f…d2206b
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams345d ago0xcf69d7…e7bf2b
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams345d ago0x1cfdd4…51bcfb
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams345d ago0xc2162b…dea734
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams345d ago0xe508b3…db646c
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams345d ago0xb9e5b8…5bb1aa
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams345d ago0x79b58d…379f30
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams345d ago0xfdb8fb…3c4fa6
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams345d ago0x6ec7c5…34e737

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.