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.25M Roundhouse has indexed across 1,401,192 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%daydreams346d ago0xaffc2b…6c66da
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams346d ago0x683e3e…e49ad1
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams346d ago0xbd195a…26cf47
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams346d ago0x0c8c09…fc1f37
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams346d ago0xdceadb…5b102a
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams346d ago0x390e12…abf8d3
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams346d ago0xbfe490…b35ce6
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams346d ago0xd3d89c…510c33
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams346d ago0xa0ad7e…8f9898
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams346d ago0xd51c87…823f8f
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams347d ago0xd5f567…70c8f3
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams347d ago0xabb3e4…30cd49
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams347d ago0xad4400…7013fb
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams347d ago0x26b9c6…d921f2
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams347d ago0xd4fe54…bafefe
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams348d ago0x792407…62745b
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams348d ago0x64e0c0…d673d3
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams348d ago0x1abdb7…4d94d2
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams348d ago0x0e3253…22af26
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams348d ago0x280524…697123
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams348d ago0xac251d…1f54d5
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams348d ago0xede0b0…cd0f05
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams348d ago0x669e17…3f9797
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams348d ago0xf6a050…c9802d
0x0024…fd0e0x6482…b779BaseBase$0.0001100%daydreams348d ago0xe485b2…3bf6da

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.