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%daydreams337d ago0x6bd9bc…8fbf83
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams338d ago0x8e087f…307a0e
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams338d ago0x357c1f…99f602
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams338d ago0xa94200…103f4c
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams338d ago0x86a921…835f84
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams338d ago0x8f53f9…53cf12
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams338d ago0xd1f438…d22760
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams338d ago0xc1d205…c4e1ed
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams339d ago0x9bfab8…ba76e9
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams339d ago0x76af11…b04de7
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams339d ago0x298b93…2f71c1
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams340d ago0xdffebe…9315b6
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams340d ago0x3c63d3…dcc760
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams340d ago0xb89832…f1cb8e
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams340d ago0x82745e…9fee53
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams340d ago0xa3861f…b20d16
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams340d ago0x50ed98…da6fd7
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams340d ago0x4b4193…1d9bce
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams340d ago0x788f30…9b1523
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams340d ago0x7f0edc…ad726c
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams340d ago0x9997d2…f9649a
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams340d ago0x8d1c75…1ed37b
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams341d ago0xc96bfb…1c4430
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams341d ago0xfe22e3…509d71
0xdac5…19170x6482…b779BaseBase$0.0001100%daydreams341d ago0x330d00…bbb2aa

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.