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%daydreams323d ago0x54c602…176df0
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams323d ago0xa82826…8513a7
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams323d ago0x66ce23…d39e20
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams324d ago0x61c95d…b3cea9
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams324d ago0xa3f4fd…ac8646
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams324d ago0xa20d4e…264dbd
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams324d ago0xcdbc13…e726f0
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams324d ago0x354ce3…d02467
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams324d ago0x0f05af…a62054
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams324d ago0x1df832…bce52a
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams324d ago0x7a2b0f…80cf1b
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams324d ago0x7d31c5…95f443
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams324d ago0x4c067a…737351
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams325d ago0x4d1962…99d383
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams325d ago0x8b9956…0bedf7
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams325d ago0xef181e…53b8bc
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams325d ago0x219025…1f895f
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams325d ago0x9e608d…4f75dc
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams325d ago0x188aae…988c38
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams325d ago0xff327d…e606df
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams325d ago0x1cbf6f…638204
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams325d ago0x3a69e5…eac0e4
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams325d ago0x89826e…0a80f8
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams325d ago0x13c857…30fedf
0x240c…d71c0x6482…b779BaseBase$0.0001100%daydreams326d ago0x29be5a…7a1129

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.