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%daydreams341d ago0x6b9584…4a7336
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams341d ago0x57c883…6c2062
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams341d ago0xbb1e6d…bf1e91
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams341d ago0x7b20ca…7eeed8
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams341d ago0xf79505…426d1c
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams341d ago0xaa61e0…40e300
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams341d ago0x2dd50f…875a42
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams341d ago0x8a441f…8bb0af
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams341d ago0x7b4d72…57d03c
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams342d ago0x157676…d98ddd
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams342d ago0xe06440…b6e9f4
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams342d ago0xcdf3ed…296267
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams342d ago0xe06cff…12843d
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams342d ago0xb82638…2a888d
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams342d ago0x269de5…240785
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams342d ago0xf0657e…3dfba5
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams342d ago0xaa041f…7d277b
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams342d ago0x012d78…cd170b
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams342d ago0x9338f6…4ad4c7
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams342d ago0xac573b…a0cf58
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams343d ago0xdb8751…3aa941
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams343d ago0x2be94c…051649
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams343d ago0x8e0827…393ce4
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams343d ago0xdc759d…591c2a
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams343d ago0xcf94bb…5fa9f2

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.