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 $3068.58M Roundhouse has indexed across 1,402,722 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 277d 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.00262277d 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%daydreams348d ago0x93f81b…bb5d06
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams349d ago0xfd73d2…10b78f
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams349d ago0xae0f3b…5eadd9
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams349d ago0xc74fb3…d1ebcc
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams349d ago0xb109b5…024d6d
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams349d ago0x099165…ddbf30
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams349d ago0x565e2e…fe26e9
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams350d ago0x16068e…52b41a
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams350d ago0xfcd95e…9356e8
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams350d ago0x0470ae…d011af
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams351d ago0x88a877…d523ce
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams351d ago0xa7c7e6…1f0d10
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams351d ago0xa1b2bb…4414db
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams352d ago0xa65ea3…11f6c5
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams352d ago0x49b064…57faad
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams352d ago0x51f92f…50d46d
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams352d ago0x4c21ed…2bcb46
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams352d ago0x95f036…a477bb
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams352d ago0x599960…9b3305
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams352d ago0x94ed8c…3699fb
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams352d ago0x2759ed…df7132
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams353d ago0x2f2847…5e2be5
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams353d ago0xf767df…92870c
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams353d ago0x679d0c…8bfb12
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams353d ago0x323f89…fed5d8

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.