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%daydreams325d ago0x2a822b…f46690
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams325d ago0xfc008a…377f64
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams325d ago0xb4ca5f…5190ad
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams325d ago0x10c2e8…d26384
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams325d ago0x2720b5…d2e591
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams325d ago0x19c1a6…1cd5d5
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams326d ago0x5198f4…c7fb4c
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams326d ago0x76a26f…da13e2
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams326d ago0x650cd0…eb991c
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams326d ago0x72aa1b…f429dd
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams326d ago0x78bd12…df20d7
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams326d ago0x16fc38…a080d1
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams326d ago0xecb267…ecb841
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams326d ago0xe111bd…bf5c48
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams326d ago0x662d67…62bbd0
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams327d ago0x460e39…8bfb75
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams327d ago0x66acf0…5916da
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams327d ago0xff8362…ad708b
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams327d ago0xa115cc…e3b3a4
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams327d ago0x30c642…62b606
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams327d ago0xf7f755…86d238
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams327d ago0x3b0fb3…a4db27
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams328d ago0xf86f2a…0fdf69
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams328d ago0xefc3fa…e8f489
0x757d…56ac0x6482…b779BaseBase$0.0001100%daydreams335d ago0x9a3c7b…fe6408

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.