API Payments Agents Docs
Zero Log · Live

scan with privacy

read the wallet behind any handle without leaving a trace, LENS stores nothing, no query, no ip, no result, your scanning behavior never becomes someone else's signal

Try a private scan Read the docs
scan-private · live
# private scan, nothing logged GET /api/scan-private?username=exitliq_dev # response { "verdict": "STOP", "trust": 18, "private": true, "logged": false }
The problem

the public endpoint sees everything

every scan you run in the open is a signal someone else can read

public api log
watched live
A
your agent quietly screens a new launch
GET /api/lookup?username=exitliq_dev → CLEAR
👁
anyone monitoring the endpoint reads the same line
observer logs: handle + timestamp + verdict
every handle your agent scans is visible the second it scans it, your shortlist becomes their entry, you can't un-leak it
How it works

LENS reads the chain, nothing gets logged

your agent reads a wallet and walks away clean, no identity attached, no scanning behavior recorded

Step 1 · scan

send the target

agent posts a handle or contract to scan-private, the same deep on-chain read as the public api

Step 2 · proxy

routed, never direct

the backend fetches the read for you, your client never touches the data source, your ip never gets forwarded

Step 3 · verdict

get the full read

LENS returns CLEAR CAUTION STOP plus every signal, the backend never learns who asked or why

Step 4 · act

move without a trace

agent has what it needs to decide, your behavior leaves no footprint anyone can follow

Why it matters

your scanning strategy is alpha

every public call leaks what you look at and the second you look at it, on a hunt that is the whole game

Hidden behavior

no one sees which handles your agent scans or the exact moment it scans them

Keep your edge

competitors can't reverse your shortlist and front run the tokens you already cleared

No trails

nothing ties your agent to the wallets it digs into, nothing to leak, nothing to subpoena

Use case

the 100 token problem

what private scanning actually saves you, in one real scenario

your agent screens every new Bankrbot launch the second it hits, a hundred handles a day, looking for the clean ones

on the public api that whole hunt is visible, anyone watching the endpoint sees the exact handles you checked and the exact minute, they read which ones came back CLEAR, and they ape those tokens before your agent even finishes the run, your work becomes their entry

with private scanning the same run goes silent, the verdicts land only with the agent that paid for them, the shortlist stays yours, the edge stays yours

Modes

public vs private

pick the mode that fits your agent

Public · free · live now
  • no cost to scan
  • open read-only API
  • your calls are visible
  • great for testing
Private · zero log · live
  • nothing logged, ever
  • your ip is never forwarded
  • no query, no result stored
  • built for production agents
Integration

one endpoint, zero setup

no keys, no proofs, no payment, just call it and nothing is logged

const res = await fetch( 'https://lens-liard.vercel.app/api/scan-private?username=bankrbot' ); const { verdict, trust, devSold, logged } = await res.json(); // logged is always false, the read was never stored

full docs at /lens-docs · source is open, verify the no-log code yourself

honest note: this covers the LENS application layer, it never stores your query, ip, or result, it cannot remove network-level logs your own host or isp keeps, for full anonymity route through a vpn

scan without a trace

private scanning is live today, no logs, no payment, no setup, the public api stays free if you don't need privacy

Try the free API Read the docs