AgentReport

lazergun.eth

0xfa3f54ae9c4287ca09a486dfaface7d1d4095d93Explorer
Lazergun.ethalso a merchant
Paid out
$73.17
Last 7d vs prior 7d
Received
$83.47
Last 7d vs prior 7d
Settlements
3400
Last 7d vs prior 7d
22
Distinct counterparties
Over the whole indexed history

Paid $73.17 of the $3058.83M Roundhouse has indexed across 1,396,716 wallets — less than 0.0001% of it.

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

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

Every merchant paid publishes at least one catalogued endpoint.

Services it paid

A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; for 1 of 1 the amount paid narrows the list to the ones listed at that price.

Folded from this wallet's 1,014 most recent settlements of 3,400 lifetime, which is as far back as one scan reaches — so every figure in this section is a floor, and the totals above are not.

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
0xa724…eda2$0.00$1.3013264d agoGraph
0x1b44…958e$0.00$0.101256d agoGraph
0x110c…b784$0.03$0.003136d agoGraph

Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.

Data quality

997 self-dealing settlements (payer = payee) observed, in the 1014 most recent settlements scanned (its history is longer than the 2000-row scan cap).

Organic volume $1.43 of $72.74 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
lazergun.ethlazergun.ethBaseBase$0.10100%x402rs163d ago0x2320a6…6b2f23
lazergun.ethlazergun.ethBaseBase$0.10100%x402rs163d ago0x96d91c…9fc142
lazergun.ethlazergun.ethBaseBase$0.10100%x402rs163d ago0x05393f…aef1e2
lazergun.ethlazergun.ethBaseBase$0.10100%x402rs163d ago0xadf714…16bc46
lazergun.ethlazergun.ethBaseBase$0.10100%x402rs163d ago0x70e5c6…8e06c4
lazergun.ethlazergun.ethBaseBase$0.10100%x402rs163d ago0xe240da…234083
lazergun.ethlazergun.ethBaseBase$0.10100%x402rs163d ago0x902219…359031
lazergun.ethlazergun.ethBaseBase$0.10100%x402rs163d ago0x7ae7f0…d467c5
lazergun.ethlazergun.ethBaseBase$0.10100%x402rs163d ago0x106a27…b4ffcd
lazergun.ethlazergun.ethBaseBase$0.10100%x402rs163d ago0x0191b5…8aa813
lazergun.ethlazergun.ethBaseBase$0.10100%x402rs163d ago0x78ecde…ae0190
lazergun.ethlazergun.ethBaseBase$0.10100%x402rs163d ago0xa53e18…59539b
lazergun.ethlazergun.ethBaseBase$0.10100%x402rs163d ago0x7344ad…e08f34
lazergun.ethlazergun.ethBaseBase$0.10100%x402rs163d ago0xf035f1…3e4bff
lazergun.ethlazergun.ethBaseBase$0.10100%x402rs163d ago0x0c26ee…a333e0
lazergun.ethlazergun.ethBaseBase$0.10100%x402rs163d ago0x85e171…4d6ee0
lazergun.ethlazergun.ethBaseBase$0.10100%x402rs163d ago0xcdf232…e628d9
lazergun.ethlazergun.ethBaseBase$0.10100%x402rs163d ago0xaeaa84…71baa7
lazergun.ethlazergun.ethBaseBase$0.10100%x402rs163d ago0x02bcbe…b0f76e
lazergun.ethlazergun.ethBaseBase$0.10100%x402rs163d ago0x1b34e6…8e8d5f
lazergun.ethlazergun.ethBaseBase$0.10100%x402rs163d ago0xaf62ff…cd5184
lazergun.ethlazergun.ethBaseBase$0.10100%x402rs163d ago0xfbd4c3…91176a
lazergun.ethlazergun.ethBaseBase$0.10100%x402rs163d ago0x0527e9…d3c217
lazergun.ethlazergun.ethBaseBase$0.10100%x402rs163d ago0x159868…0568f8
lazergun.ethlazergun.ethBaseBase$0.10100%x402rs163d ago0x3e6979…47c7ef

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 lazergun.eth has actually paid for over the free read API. No key, no account.

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

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: lazergun.eth

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