AgentReport

0x3660…24e5

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

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

$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
    272 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.00272277d 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 272 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x3660…24e50x6482…b779BaseBase$0.0001100%daydreams324d ago0xf65c9c…e0b91d
0x3660…24e50x6482…b779BaseBase$0.0001100%daydreams324d ago0x72618d…d0ca65
0x3660…24e50x6482…b779BaseBase$0.0001100%daydreams324d ago0x6a71a5…54d46f
0x3660…24e50x6482…b779BaseBase$0.0001100%daydreams324d ago0xe359f0…f768b1
0x3660…24e50x6482…b779BaseBase$0.0001100%daydreams324d ago0x8a636d…e68a86
0x3660…24e50x6482…b779BaseBase$0.0001100%daydreams324d ago0x9ab54f…3e7ba3
0x3660…24e50x6482…b779BaseBase$0.0001100%daydreams324d ago0x218ab9…9399bc
0x3660…24e50x6482…b779BaseBase$0.0001100%daydreams324d ago0xa031c0…35a1e9
0x3660…24e50x6482…b779BaseBase$0.0001100%daydreams325d ago0xaa36be…b151a8
0x3660…24e50x6482…b779BaseBase$0.0001100%daydreams325d ago0xf12eff…1fcc53
0x3660…24e50x6482…b779BaseBase$0.0001100%daydreams325d ago0x12ece6…6b1154
0x3660…24e50x6482…b779BaseBase$0.0001100%daydreams325d ago0x50878b…f604ad
0x3660…24e50x6482…b779BaseBase$0.0001100%daydreams325d ago0x13530c…c374e6
0x3660…24e50x6482…b779BaseBase$0.0001100%daydreams325d ago0x6dda25…14b72f
0x3660…24e50x6482…b779BaseBase$0.0001100%daydreams325d ago0xdd1fda…e50f56
0x3660…24e50x6482…b779BaseBase$0.0001100%daydreams325d ago0x739ffe…58e8e8
0x3660…24e50x6482…b779BaseBase$0.0001100%daydreams325d ago0x0c6269…e12acc
0x3660…24e50x6482…b779BaseBase$0.0001100%daydreams325d ago0x2731d2…79b394
0x3660…24e50x6482…b779BaseBase$0.0001100%daydreams325d ago0xb2aeae…0596d3
0x3660…24e50x6482…b779BaseBase$0.0001100%daydreams326d ago0xd2a448…904127
0x3660…24e50x6482…b779BaseBase$0.0001100%daydreams326d ago0x2bfc6b…2d346e
0x3660…24e50x6482…b779BaseBase$0.0001100%daydreams326d ago0x366118…db6a4e
0x3660…24e50x6482…b779BaseBase$0.0001100%daydreams326d ago0x5b41df…2dbfdf
0x3660…24e50x6482…b779BaseBase$0.0001100%daydreams326d ago0x3bd69c…c0aa40
0x3660…24e50x6482…b779BaseBase$0.0001100%daydreams326d ago0x8c7952…77a8de

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

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

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: 0x3660…24e5

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