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%daydreams349d ago0xbcac4f…597f02
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams349d ago0xda0c9d…9ac9fd
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams349d ago0xdc09a8…b32d2f
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams349d ago0x772820…376678
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams349d ago0x3a0c42…581510
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams350d ago0xc11b30…eb4ddc
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams350d ago0xc2e1b9…dd2e5b
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams350d ago0x82f76e…d4700d
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams350d ago0xc381a4…42e5eb
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams350d ago0x798102…9643ae
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams351d ago0x1ef2a8…d23993
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams351d ago0x14253e…df28d2
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams351d ago0xb88f11…65dbf7
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams351d ago0x5589f6…c68abd
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams351d ago0x5a3ee1…b4d866
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams351d ago0xf9c56e…a9457f
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams351d ago0x6f49c0…9e6f01
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams351d ago0xbf6ae4…309a92
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams352d ago0x1981b6…b0f721
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams352d ago0xe8d7bb…228f1b
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams352d ago0xa18939…df3581
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams352d ago0xcb1886…546dd4
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams352d ago0x782d68…e64642
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams352d ago0x5b8a53…570265
0x7d50…35140x6482…b779BaseBase$0.0001100%daydreams352d ago0x2c192c…1cbb96

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.