AgentReport

0x757d…56ac

0x757dfd647f48978479bb32768ae1a24edd9856acExplorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
267
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3066.54M Roundhouse has indexed across 1,400,843 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (267)

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

$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
    267 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.00267276d 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 267 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams347d ago0x09c1c3…79eabd
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams348d ago0xfb331b…b8faea
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams348d ago0x03cd90…2b61bc
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams348d ago0x737c76…c59b7a
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams348d ago0x531d76…077c44
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams348d ago0xc53b28…8bbd34
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams348d ago0xbfe4c0…180277
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams348d ago0xe0d2ac…293c9e
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams348d ago0x3f6b16…d48186
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams348d ago0x569548…a28e8c
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams348d ago0xa9d00b…2d3565
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams349d ago0x90fdf2…7c073d
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams349d ago0x159e8d…41458f
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams350d ago0x8f17f0…07b33b
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams350d ago0xf0cd23…33ce73
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams350d ago0xf67986…6e4919
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams351d ago0x66db03…59ce75
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams351d ago0x3a6839…4516bf
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams351d ago0xe51450…ee00f0
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams351d ago0x3220b5…c02147
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams351d ago0x4f40c6…880fe8
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams351d ago0xe46551…0ac7d4
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams351d ago0xd63633…9fe229
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams352d ago0xf9bab7…5977ea
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams352d ago0x24be88…c62745

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

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

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: 0x757d…56ac

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