AgentReport

0x3e2d…7164

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

Paid $0.03 of the $3067.00M Roundhouse has indexed across 1,401,091 wallets — less than 0.0001% of it.

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

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

$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
    263 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.00263276d 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 263 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams337d ago0x4d5edb…b67cec
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams337d ago0x4a7d07…9c1bc2
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams338d ago0xd37b61…54c31d
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams338d ago0xa8c238…1a5020
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams338d ago0xae5d01…bd66bc
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams338d ago0xa866cc…28255d
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams338d ago0xee4fe6…4e129b
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams339d ago0x043fab…521cad
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams339d ago0x6075e7…04b24f
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams339d ago0xc1df1d…118363
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams339d ago0xa8fd58…a029e2
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams339d ago0x06d593…f115b9
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams340d ago0x6e44e9…4a0cee
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams340d ago0x1d98f4…5067a7
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams340d ago0x20448a…882ce9
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams340d ago0xaffe1b…a3a6a9
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams340d ago0x9f6c6a…bbc000
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams340d ago0x93239d…220b7f
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams340d ago0x3ee005…760d8c
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams340d ago0xcc3c3f…0a46ba
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams340d ago0x383099…3b5bc2
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams340d ago0x4a0dad…b49c47
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams341d ago0xa7c752…0c8be7
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams341d ago0x1838c6…9b0997
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams341d ago0x852c69…5ec489

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

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

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: 0x3e2d…7164

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