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 $3067.00M Roundhouse has indexed across 1,400,982 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%daydreams352d ago0xadb322…722dc7
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams352d ago0xb07efa…3e1e48
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams352d ago0x25e7a6…cb6605
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams352d ago0x81952e…5cc31b
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams352d ago0xc17f64…550e95
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams352d ago0xc68efe…259f7f
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams352d ago0x360d95…e66118
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams353d ago0x9f8a37…c587cd
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams353d ago0x5510ea…675247
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams353d ago0xa2bafc…575f85
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams353d ago0xde9151…93d246
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams353d ago0x97b339…e5ec63
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams353d ago0x9da553…31b3d7
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams354d ago0xe32097…69968d
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams354d ago0x6e46ff…cf544e
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams355d ago0x7992e9…850b8f
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams355d ago0x7db3d0…c5190a
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams355d ago0xa546a7…cc9ec7
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams355d ago0x74998e…0f5760
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams355d ago0x117762…f2c3ac
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams355d ago0x70ad9c…2d63ee
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams356d ago0xd41a06…4405e4
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams356d ago0x7acfc2…2d0669
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams356d ago0xe9dc5d…c6fb7f
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams356d ago0xb32107…799169

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.