AgentReport

0x24d7…0915

0x24d78fb725da99fa38d085485f437e4346380915Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
265
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 (265)

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

$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
    265 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.00265277d 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 265 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams326d ago0x77f7b3…721fa3
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams326d ago0x8987ab…79fb0e
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams326d ago0x2f56c9…75abe0
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams326d ago0x2ac5ed…fe82a3
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams327d ago0x05f97a…012b76
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams327d ago0xaebf44…db8ec7
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams327d ago0x1b9287…7c2e72
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams327d ago0x728255…ea5517
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams327d ago0xb92f35…6bb629
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams327d ago0x77beec…5af9ab
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams327d ago0xcf33fa…14f05a
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams327d ago0x05ba6b…1a9e5e
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams328d ago0x2a0744…b572d2
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams328d ago0x9048dc…bafc93
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams328d ago0x8ce2ce…fd87e8
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams328d ago0xf38804…b92b72
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams328d ago0x3c2c71…4bccee
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams328d ago0xbd2903…2a8cd4
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams336d ago0x4a1d05…5c8d0e
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams337d ago0x166918…6465eb
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams337d ago0x27d5b0…c3fdc9
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams338d ago0x8e7974…7bf5e7
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams338d ago0x8c0f9b…435eb8
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams338d ago0x4f88f9…83c9e4
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams338d ago0x51c06f…30b520

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

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

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: 0x24d7…0915

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