Architecture

LENS is a thin client over a small, honest backend. The extension and agents call one API; the API reads the chain and a launch index, with an optional AI pass.

How a scan flows

The extension or an agent sends an address to the LENS API. The API reads on-chain history through Alchemy on Base, checks a launch index in Supabase for tokens shipped through Bankrbot, and optionally runs the picture through Venice for a plain-language AI summary. The red-line rules run over all of it, and the verdict comes back.

The pieces

• Alchemy provides the Base RPC, the raw on-chain reads, deploys, transfers, funding.
• Supabase holds the bankr_launches index, so a token can be matched to its launch without crawling the whole chain.
• Venice powers the optional AI verdict that explains the result in a sentence.
• lens-listener is a background worker that polls for new launches and keeps the index current, so fresh tokens are scannable quickly.

Everything the API touches is public data. There is no wallet connection anywhere in the flow, and nothing LENS reads requires a signature.