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,689 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%daydreams335d ago0x4bbc1f…4a9585
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams337d ago0x407252…2a7d04
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams337d ago0x3b1025…a386fd
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams337d ago0x3984fc…8ab201
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams337d ago0xaf9f40…3b4822
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams337d ago0xc2c376…c3f9af
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams337d ago0x8304e7…4bd8a3
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams337d ago0x311bac…e9c8a4
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams337d ago0x9c8710…282dd0
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams337d ago0x62de69…9ed53b
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams338d ago0x240a16…b30b2a
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams338d ago0xb75b07…67de4a
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams338d ago0xb5a32b…90ffb2
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams339d ago0xcf3bc5…f892d5
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams339d ago0x7377d2…503c64
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams339d ago0xdae7ab…6c64d0
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams339d ago0x638118…bb1596
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams339d ago0xb5b6ef…d6ebcc
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams339d ago0x372678…575f95
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams340d ago0x4a9157…1331f3
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams340d ago0x1b8b53…7c7a21
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams340d ago0xa37243…039155
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams340d ago0x8dbb61…584134
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams340d ago0x24a3a7…bdd6f8
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams340d ago0x69edc5…e0600d

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.