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%daydreams341d ago0x71bd9f…4a573e
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams341d ago0xc0cebd…dafd2c
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams341d ago0x3bfee8…e26842
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams341d ago0x9dab11…0ab77d
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams341d ago0xf872ff…b1e820
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams341d ago0x0e2037…5df7cd
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams342d ago0xed7235…342e19
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams342d ago0xd68d64…0895dd
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams342d ago0x8112b1…15b7d6
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams342d ago0xa7da9d…e53dff
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams342d ago0xdab37e…1567e9
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams342d ago0x5ad19f…da5624
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams342d ago0x0c0c6f…d8f875
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams342d ago0x4cbef6…2b129f
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams342d ago0x62b535…f1b296
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams342d ago0xcfe051…3b8867
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams342d ago0x3a53aa…d027b6
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams343d ago0x915e0d…2fb276
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams343d ago0x1c60ed…c264b7
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams343d ago0x09c149…a3510e
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams343d ago0x106105…a2d341
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams343d ago0x568b58…80be0e
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams343d ago0x43ae9f…d112bf
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams343d ago0xf47962…4a0421
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams343d ago0x08d2e8…701fe9

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.