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%daydreams340d ago0x9b5b3a…80b2fa
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams340d ago0xa26a00…7b9346
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams340d ago0x3ec5ed…56491f
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams340d ago0x799aae…676ed4
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams341d ago0x508a25…2ab9a5
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams341d ago0x7742f0…354fb5
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams341d ago0x6d55f9…dc9e38
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams341d ago0x809811…d82b38
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams341d ago0xc050d9…35986d
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams341d ago0x2a570a…e09121
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams341d ago0x34c135…e46b3d
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams341d ago0x609f29…b6e8eb
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams341d ago0x348a60…885e2a
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams341d ago0x04269f…aa6bca
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams342d ago0x783e6e…ac96a4
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams342d ago0xa006e1…bb378f
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams342d ago0x91b619…4e3b09
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams342d ago0x030b07…c32ecd
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams342d ago0xbeab6b…e3cf59
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams342d ago0x9da105…c260f0
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams342d ago0x938ba5…56e34d
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams342d ago0xff3ccd…dcc7a3
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams342d ago0xf827fc…8874ec
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams342d ago0x15751f…89debf
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams342d ago0x9253d2…d57502

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.