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%daydreams344d ago0xfa4eb7…3343d5
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams344d ago0x8bc541…9ddc44
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams344d ago0xf94ed8…2fc498
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams344d ago0xe953c1…9ee140
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams344d ago0xd9eec3…266f64
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams345d ago0x23c57a…2bdf63
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams345d ago0x74f535…9df975
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams345d ago0x8c7058…a58c5d
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams345d ago0x4febe8…bb5b8c
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams345d ago0xe19cf2…324c82
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams345d ago0xec0408…8a93ac
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams345d ago0x6975af…52ea18
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams345d ago0xbce942…63235d
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams345d ago0x1be63b…097855
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams345d ago0x8238b5…c2a921
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams345d ago0x59e0ed…388383
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams345d ago0x3f1ce0…b7c215
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams346d ago0xe55ed1…a510f0
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams346d ago0xc87fb1…6b2588
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams346d ago0x522d4f…d386c7
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams346d ago0x3896d3…fca50b
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams346d ago0xdd3909…bc5c4a
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams346d ago0xf53e24…e5fb39
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams346d ago0x3e2879…4ba6fd
0x24d7…09150x6482…b779BaseBase$0.0001100%daydreams346d ago0xccca73…38405a

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.