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%daydreams325d ago0xfda1b7…1ff125
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams325d ago0xdaf236…d8187e
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams326d ago0x30b207…58d7e1
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams326d ago0x7e66fa…3a64bd
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams326d ago0x7de671…3edb9c
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams326d ago0x9941db…bef226
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams326d ago0xf8c4fc…db1ccb
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams326d ago0x21d6ae…2f41fd
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams326d ago0x7cfa81…515d73
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams326d ago0x014706…80d116
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams326d ago0x8882d9…04a3f1
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams326d ago0x43a991…12577e
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams327d ago0x65ab81…382805
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams327d ago0xb249fe…2db14a
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams327d ago0xdf659d…639100
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams327d ago0xfec3bd…e2bacf
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams327d ago0x46f18f…d3ad0a
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams327d ago0x07c6b0…0d3952
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams327d ago0xe6538e…0fa549
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams328d ago0x3253d5…92b63e
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams328d ago0x196e61…531a23
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams328d ago0xeceba1…8fe012
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams328d ago0xa8af54…0c99f8
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams335d ago0x44abdd…0d6906
0x0837…01120x6482…b779BaseBase$0.0001100%daydreams336d ago0xabc6d7…4dbeca

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.