AgentReport

0x240c…d71c

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

Paid $0.03 of the $3068.58M Roundhouse has indexed across 1,402,722 wallets — less than 0.0001% of it.

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

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

$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
    267 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.00267277d 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 267 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams326d ago0xeac9fd…592f9a
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams326d ago0xd7a7a7…1f82b9
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams326d ago0x2ffee0…74cbdd
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams326d ago0xb57bc3…0b611c
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams326d ago0xa3c3d9…9e392d
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams326d ago0x1450b8…47fddd
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams326d ago0xc30082…bd44bf
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams326d ago0xe12d64…932275
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams327d ago0x027c52…12d2f7
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams327d ago0xd70f30…b675fe
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams327d ago0x627752…6f3e60
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams327d ago0xc0c695…6eb1be
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams327d ago0xcf92f9…3d9ad1
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams327d ago0x3bf03f…b7043b
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams327d ago0xfcc57f…bfc856
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams328d ago0x728970…4f2463
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams328d ago0xc3c5a3…f97dfe
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams328d ago0x978912…6483bf
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams328d ago0x0b4fa1…bd1c3a
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams328d ago0xaf3538…a417f6
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams336d ago0xa66d6c…4587e3
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams337d ago0x6beeba…1a3d45
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams337d ago0x74ee50…1bc725
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams337d ago0xda002d…127075
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams338d ago0x56eb41…a6b0f5

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

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

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: 0x240c…d71c

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