AgentReport

0x7d50…3514

0x7d50900c4bf32d348598342e877eea554e323514Explorer
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
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams352d ago0xc1c99e…c9fabe
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams352d ago0x1f0d40…bf6d0f
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams353d ago0xa5e050…a6804f
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams353d ago0x8d007d…145701
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams353d ago0xbfa67c…1f9e62
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams353d ago0x3f80af…daea0a
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams353d ago0x7a9f95…4d33ec
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams353d ago0x738b8a…e7781b
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams355d ago0x12fcb6…4e5d33
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams355d ago0x3daba9…2ae98b
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams355d ago0xfe8ffb…25243c
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams356d ago0x68ec48…129189
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams356d ago0xe823fa…d5f484
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams357d ago0x885ff1…01e57b
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams357d ago0x53bd56…223508
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams357d ago0xf973d6…6d66c8
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams358d ago0x0782bc…998fd8
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams358d ago0xbb710e…d41c4f
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams358d ago0x0bcf0d…abad0d
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams358d ago0x927143…ee547f
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams358d ago0xa21e46…34b5b5
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams358d ago0x895d28…722b84
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams359d ago0x290c5f…050669
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams359d ago0x1d65a5…f040fb
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams359d ago0xae1931…6f70c1

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

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

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: 0x7d50…3514

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