AgentReport

0x3d8a…06c5

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

Paid $0.03 of the $3070.29M Roundhouse has indexed across 1,403,290 wallets — less than 0.0001% of it.

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

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

$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
    267 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.00267277d 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 267 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x3d8a…06c50x6482…b779BaseBase$0.0001100%daydreams346d ago0xd13ac9…d57a14
0x3d8a…06c50x6482…b779BaseBase$0.0001100%daydreams346d ago0x3c730f…46800b
0x3d8a…06c50x6482…b779BaseBase$0.0001100%daydreams346d ago0x8897ed…c31498
0x3d8a…06c50x6482…b779BaseBase$0.0001100%daydreams346d ago0x6d6c86…88aa69
0x3d8a…06c50x6482…b779BaseBase$0.0001100%daydreams346d ago0x333471…ff51f2
0x3d8a…06c50x6482…b779BaseBase$0.0001100%daydreams347d ago0x1a1652…36673b
0x3d8a…06c50x6482…b779BaseBase$0.0001100%daydreams347d ago0xad0f7c…8d75c8
0x3d8a…06c50x6482…b779BaseBase$0.0001100%daydreams347d ago0x3bae11…7cd668
0x3d8a…06c50x6482…b779BaseBase$0.0001100%daydreams347d ago0x176aa0…a8251e
0x3d8a…06c50x6482…b779BaseBase$0.0001100%daydreams347d ago0xe5548d…f5d0ae
0x3d8a…06c50x6482…b779BaseBase$0.0001100%daydreams347d ago0xc3dbc3…123987
0x3d8a…06c50x6482…b779BaseBase$0.0001100%daydreams347d ago0xca6810…26e89a
0x3d8a…06c50x6482…b779BaseBase$0.0001100%daydreams347d ago0x394681…09c1f3
0x3d8a…06c50x6482…b779BaseBase$0.0001100%daydreams348d ago0x53dab7…685651
0x3d8a…06c50x6482…b779BaseBase$0.0001100%daydreams348d ago0x3ac45b…cd07a3
0x3d8a…06c50x6482…b779BaseBase$0.0001100%daydreams348d ago0x00693f…07d199
0x3d8a…06c50x6482…b779BaseBase$0.0001100%daydreams348d ago0xcc2069…2fd672
0x3d8a…06c50x6482…b779BaseBase$0.0001100%daydreams348d ago0xeacec0…2b71be
0x3d8a…06c50x6482…b779BaseBase$0.0001100%daydreams348d ago0x799469…9065de
0x3d8a…06c50x6482…b779BaseBase$0.0001100%daydreams348d ago0x590c12…2f8f8d
0x3d8a…06c50x6482…b779BaseBase$0.0001100%daydreams348d ago0xa19842…a56d78
0x3d8a…06c50x6482…b779BaseBase$0.0001100%daydreams348d ago0x74fb5d…b2eb2e
0x3d8a…06c50x6482…b779BaseBase$0.0001100%daydreams349d ago0xcbbdc0…55ae8b
0x3d8a…06c50x6482…b779BaseBase$0.0001100%daydreams349d ago0x92be08…c3647c
0x3d8a…06c50x6482…b779BaseBase$0.0001100%daydreams349d ago0x12d984…56e377

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

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

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: 0x3d8a…06c5

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