AgentReport

0xdac5…1917

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

Paid $0.03 of the $3067.43M Roundhouse has indexed across 1,401,742 wallets — less than 0.0001% of it.

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

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

$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
    262 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.00262276d 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 262 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams326d ago0x10779b…caf2de
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams326d ago0x16848a…e49a84
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams326d ago0xb7ac7f…e4613b
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams326d ago0xb75e9c…ce7fe4
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams326d ago0x8d13fc…4f1258
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams326d ago0xadbd1a…414031
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams326d ago0x9f14dc…5c5d2c
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams326d ago0xe02c0d…3facdc
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams326d ago0x5f405b…384c77
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams326d ago0x4cc96b…1f2cd5
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams327d ago0xb14563…6a752f
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams327d ago0x60eddb…9ffb02
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams327d ago0x60d222…d5e768
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams327d ago0xc1dc3b…0d3753
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams327d ago0xc4901a…be96ee
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams327d ago0xef8d16…2e0806
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams328d ago0x6c9f01…cdcf7d
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams328d ago0x398f0f…b64e90
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams328d ago0x2e2512…dfcf1d
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams328d ago0xae5da1…814061
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams335d ago0x127f1d…338779
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams337d ago0xf71560…8c7f0a
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams337d ago0x3576c0…d96646
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams337d ago0x8a217a…a84b40
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams337d ago0xdd4eb0…bdcb8f

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

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

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: 0xdac5…1917

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