AgentReport

0x0024…fd0e

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

Paid $0.03 of the $3067.43M Roundhouse has indexed across 1,401,575 wallets — less than 0.0001% of it.

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

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

$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
    264 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.00264276d 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 264 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams348d ago0x14ffa2…daa0c9
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams349d ago0x4ec6ec…3c7155
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams349d ago0x199295…cec760
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams349d ago0x3af25e…f68c28
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams350d ago0x755d12…fe555e
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams350d ago0xf9b11e…62397a
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams350d ago0x1d0695…ee55b3
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams350d ago0x6a3582…23a925
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams351d ago0x0643d1…42f110
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams351d ago0x12c48f…3d70c1
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams351d ago0x4ce50f…b36b81
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams351d ago0xdd7ad1…f38d72
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams351d ago0xcbe9e8…2525c2
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams351d ago0x35f75f…ed90a1
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams351d ago0x8ecd31…c1854a
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams352d ago0x37b79c…1e1a33
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams352d ago0x8d0cc7…11d088
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams352d ago0x524a2e…470810
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams352d ago0xa53e61…906989
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams352d ago0x3fdc78…140053
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams352d ago0x757538…2a20ba
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams352d ago0xf6d3c0…8f1362
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams352d ago0x94a0fa…b50ba2
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams352d ago0x78a657…95be75
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams352d ago0x90a9cd…e17dd9

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

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

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: 0x0024…fd0e

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