Architecture
XanLens is intentionally lean: no database, no user accounts, no session state. Each request is stateless and self-contained.
Stack
- Next.js 16 on Vercel — frontend and API routes
- Gemini API — primary AI engine + content generation
- NVIDIA NIM — Llama 3.3 70B for second engine perspective
- Tavily API — AI-native search with real-time web data
- x402 protocol — HTTP-native USDC payments on Base
- Vercel Edge — global deployment, sub-100ms TTFB
Request Flow
User/Agent → API Route → Audit Engine
Audit Engine → [Gemini, Llama, Tavily] (parallel)
Audit Engine → Site Crawler → Score + Findings
Score + Findings → Content Generator → 7 Content Types
→ JSON Response
Design Principles
- Stateless — no database, no sessions, no auth tokens
- Fast — parallel engine queries, edge-deployed
- Portable — works from any HTTP client, curl to Claude
- Transparent — scores show exactly what each engine said