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 $3069.68M Roundhouse has indexed across 1,403,034 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%daydreams342d ago0xa364f3…19377d
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams342d ago0xdbcb38…596f7f
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams342d ago0x11c3d2…ee10bf
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams342d ago0xf3e6fd…2d5f59
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams342d ago0x362d8c…af4176
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams342d ago0xbcc765…f8724b
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams342d ago0x7e4cf5…6d4f69
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams342d ago0xbbffa2…0f1069
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams342d ago0x4f7f7c…764b24
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams343d ago0x4e1fa6…f8eb4d
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams343d ago0x063fd3…0b901b
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams343d ago0x7c0066…2652ff
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams343d ago0x0b439b…3eee86
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams343d ago0xf58952…6a6c18
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams343d ago0x752e9b…2a726a
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams343d ago0xbe3b84…9a5491
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams343d ago0x8f8ef9…82adcf
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams343d ago0x6aecc9…b1b597
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams343d ago0x47c9ff…96909f
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams344d ago0xc1f2db…9c48bf
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams344d ago0x950c0a…0e7de0
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams344d ago0x136dbb…83f6c2
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams344d ago0x7a68ea…6468ec
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams344d ago0x98b47f…cc6f51
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams344d ago0x108c49…67bf21

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.