AgentReport

0x1d68…fcdc

0x1d685613c8b652c5bc46f82509e8e84de842fcdcExplorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
255
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 (255)

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

$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
    255 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.00255276d 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 255 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x1d68…fcdc0x6482…b779BaseBase$0.0001100%daydreams337d ago0xd560f2…05e368
0x1d68…fcdc0x6482…b779BaseBase$0.0001100%daydreams337d ago0x10b9bc…7bd034
0x1d68…fcdc0x6482…b779BaseBase$0.0001100%daydreams337d ago0x720952…77311f
0x1d68…fcdc0x6482…b779BaseBase$0.0001100%daydreams337d ago0xaf7e98…86d765
0x1d68…fcdc0x6482…b779BaseBase$0.0001100%daydreams338d ago0x6b3313…347d88
0x1d68…fcdc0x6482…b779BaseBase$0.0001100%daydreams338d ago0x775d9f…17e4a1
0x1d68…fcdc0x6482…b779BaseBase$0.0001100%daydreams338d ago0x47b438…2962f5
0x1d68…fcdc0x6482…b779BaseBase$0.0001100%daydreams338d ago0x8ab915…0bc707
0x1d68…fcdc0x6482…b779BaseBase$0.0001100%daydreams339d ago0x0bc3f6…84f779
0x1d68…fcdc0x6482…b779BaseBase$0.0001100%daydreams339d ago0x7ad6f5…050030
0x1d68…fcdc0x6482…b779BaseBase$0.0001100%daydreams339d ago0x305f04…c4685c
0x1d68…fcdc0x6482…b779BaseBase$0.0001100%daydreams339d ago0x79ea1a…6546cf
0x1d68…fcdc0x6482…b779BaseBase$0.0001100%daydreams339d ago0x090ac7…935d16
0x1d68…fcdc0x6482…b779BaseBase$0.0001100%daydreams339d ago0x89938d…388e80
0x1d68…fcdc0x6482…b779BaseBase$0.0001100%daydreams340d ago0x2753ae…13f381
0x1d68…fcdc0x6482…b779BaseBase$0.0001100%daydreams340d ago0xaa77ec…241dc0
0x1d68…fcdc0x6482…b779BaseBase$0.0001100%daydreams340d ago0x6676ad…9155f3
0x1d68…fcdc0x6482…b779BaseBase$0.0001100%daydreams340d ago0x0781a6…71b313
0x1d68…fcdc0x6482…b779BaseBase$0.0001100%daydreams340d ago0x59dfe4…278ad6
0x1d68…fcdc0x6482…b779BaseBase$0.0001100%daydreams340d ago0xd6f3c5…8cb4b2
0x1d68…fcdc0x6482…b779BaseBase$0.0001100%daydreams340d ago0xffb7f1…af54b6
0x1d68…fcdc0x6482…b779BaseBase$0.0001100%daydreams340d ago0xbd2ca7…1712d4
0x1d68…fcdc0x6482…b779BaseBase$0.0001100%daydreams340d ago0x326236…cf4b6c
0x1d68…fcdc0x6482…b779BaseBase$0.0001100%daydreams340d ago0xc95edf…1386aa
0x1d68…fcdc0x6482…b779BaseBase$0.0001100%daydreams341d ago0x526dce…fb8158

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

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

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: 0x1d68…fcdc

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