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%daydreams343d ago0x819d0d…9a40e8
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams343d ago0x4dfbda…1f806e
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams343d ago0xcca22e…bb9984
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams343d ago0x60e709…7a9f03
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams344d ago0x9c3f85…849673
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams344d ago0x01ce4b…aee1c8
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams344d ago0xc67082…cdb6fa
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams344d ago0x96feb2…77667c
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams344d ago0x964284…9b7d00
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams344d ago0xf66544…eb3f28
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams344d ago0x86ec45…060c4c
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams344d ago0xb1b8fc…5244ab
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams344d ago0x6f0884…6bb2f5
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams344d ago0xa392f7…bb027a
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams344d ago0x51dbaf…e8008a
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams345d ago0x3ee67d…5fce10
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams345d ago0x61dcc0…333862
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams345d ago0xec0f06…d314e2
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams345d ago0xcd0601…e1546a
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams345d ago0x08aa82…126ade
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams345d ago0x6f89e3…0a1e14
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams345d ago0xd4b151…6ca36a
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams345d ago0x85620a…c4c4f3
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams345d ago0xdb26c3…226b79
0x3e2d…71640x6482…b779BaseBase$0.0001100%daydreams345d ago0xeeb9a1…f09d0b

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.