Complete guide to understanding, deploying, and integrating LENS. Everything you need to add on-chain intelligence to your product.
API Docs · Setup Guide · Examples · FAQ
LENS reads the deployer wallet behind any X profile or Base contract and returns a plain-language rug-risk verdict: CLEAR, CAUTION, or STOP.
The read includes dev sells, fee capture, liquidity status, linked accounts, funding trail, and on-chain history. It powers the Chrome extension, the public API, and the skill pack.
I just want to use the API → API Docs
I want to run the backend locally → Setup Guide
I want to integrate LENS into my app → Examples
I want to build a custom skill → Skills Guide
I want to customize the extension → Extension Guide
I have a question → FAQ
| Component | Purpose | Repo |
|---|---|---|
| Extension | Chrome popup that injects verdicts into X profiles | lens-extension |
| Backend API | Reads chains, returns verdicts, runs Bankrbot cron | Lens |
| Skill Pack | Ready skill for agent frameworks (AEON, Claude MCP, etc) | lens-skill-pack |
| Website | Marketing, API docs, community | lens-web |
- User opens an X profile → Extension detects wallet/contract addresses in bio
- Extension calls the API →
GET /api/lookup?username=handle - Backend queries Supabase + Alchemy → Fetches token launches, dev sells, linked accounts
- Returns a verdict →
CLEAR,CAUTION,STOP+ detailed signals - Card renders inline → User sees the read right under the bio
The same API is available publicly for any app to use. No key required, read-only.
Backend (Node.js + Supabase + Alchemy)
/api/lookup— main endpoint, resolves dev wallet + scores it/api/index-launches— cron job, fetches Bankrbot launches every 5 min/api/verdict— AI scoring logic/api/linked-accounts— sibling wallet detection
Frontend (Chrome extension, vanilla JS)
- Content script injects card into X DOM
- Popup settings stored in chrome.storage (local)
- Background service worker handles API calls
Database (Supabase PostgreSQL)
bankr_launches— indexed token launches from Bankrbot- Custom queries for linked accounts, dev history
Verdict
CLEAR— on-chain history backs the pitch, no alarmsCAUTION— mixed signals worth a second lookSTOP— dev dumped, liquidity unlocked, shared funder with scammer siblings
Trust Score
- 0-100, higher is safer
- Computed from dev sells, fee capture, account age, linked networks
Linked Accounts
- Other X handles sharing the same deployer wallet
- Detected via Supabase queries + on-chain transaction analysis
Found a bug or want to improve LENS? Issues and PRs welcome.
Questions? Check the FAQ or open an issue.
built on Base · lnsx.io