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%daydreams345d ago0x9649d0…b14f91
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams345d ago0x9dc05a…d841cc
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams346d ago0x6214ea…9a8542
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams346d ago0xacf1b8…c58bbf
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams346d ago0x85afab…18b8a2
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams346d ago0xefeb9b…b79182
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams346d ago0x9461f5…baf1b8
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams346d ago0x4a3433…a7abe6
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams346d ago0x23c57b…5e005b
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams346d ago0x741f05…332378
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams346d ago0xc9fcc3…b70b18
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams346d ago0x184876…f79622
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams347d ago0x23b596…8fa02d
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams347d ago0x21d2b2…d46ae1
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams347d ago0x5295d1…256cc1
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams347d ago0xbc2532…0da307
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams347d ago0x0492d8…e17df7
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams347d ago0x603833…9db200
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams348d ago0xb0692a…b2587d
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams348d ago0x431f0a…aad336
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams348d ago0x35fbd9…51be95
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams348d ago0x2d0c95…7f57f1
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams348d ago0x68a155…2d8302
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams348d ago0x1aded4…589aff
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams348d ago0x1f9836…59e0d8

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.