AgentReport

0xc9b3…4987

0xc9b3bb7cc6c52cd1cf7c7345d403c70ffe9a4987Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
261
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3070.29M Roundhouse has indexed across 1,403,290 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (261)

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.032611

$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 277d ago
    $0.03
    261 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.00261277d 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 261 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams349d ago0xd8f8ae…f339db
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams349d ago0xace320…c4369b
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams349d ago0xe4bda3…e942a1
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams349d ago0x3ff3b9…d0887e
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams349d ago0x995d5e…d982e1
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams349d ago0x20232b…12dcd8
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams349d ago0x6f17a3…10e81f
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams349d ago0x49aedc…d4d15b
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams350d ago0xa852ba…831b8a
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams350d ago0xde02d1…8727b3
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams350d ago0x6bebdf…f07516
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams350d ago0xefac36…23ba6b
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams351d ago0xd8871d…4b97a0
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams351d ago0x3d4495…80e782
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams351d ago0x41e2e1…9ecdb5
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams351d ago0x4f180c…5787ef
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams351d ago0x0daf99…26953b
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams351d ago0xccf291…fdbdad
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams352d ago0x238f16…32bb27
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams352d ago0xc49d8a…c51fa0
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams352d ago0x154319…53aee4
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams352d ago0xeea37e…be4b05
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams352d ago0x91dc0b…490977
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams352d ago0x6a6e2b…a9ed25
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams352d ago0x9f838f…0cf2ee

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 0xc9b3…4987 has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0xc9b3bb7cc6c52cd1cf7c7345d403c70ffe9a4987

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: 0xc9b3…4987

curl -s 'https://api.roundhouseai.io/v0/agents/0xc9b3bb7cc6c52cd1cf7c7345d403c70ffe9a4987'
curl -s 'https://api.roundhouseai.io/v0/entities/0xc9b3bb7cc6c52cd1cf7c7345d403c70ffe9a4987/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.