Settings

How Lexis works for you

Card writer

No API key on the server

Cards cannot be written until a key is configured. Words you add will wait.

Get one free at openrouter.ai/keys. Running locally, put it in .env.local as OPENROUTER_API_KEY=sk-or-v1-… and restart. Deployed on Vercel, add it under Project Settings → Environment Variables and redeploy.

ModelFetched live from OpenRouter, so the list never goes stale.

Your level

Write definitions forOnly affects words added from now on. Rewrite an old card from its page to redo it at this level.

Cards per word

MeaningSee the word, recall what it means. The easy direction.RecallSee the meaning, produce the word. Harder, and where real fluency comes from.In contextFill the word into a real sentence. The strongest card type there is.ListeningHear the word, name it. Turn on if you want to catch words in speech.

Turning a type off only removes cards you have never seen — review history is never thrown away.

Daily pace

New words a dayCounts words, not cards. Every new word becomes about 8 reviews over the next month — 10 to 15 is a sustainable pace.Review capA ceiling for busy days. Skipped cards simply wait.

Target recallLexis schedules each card for the moment your chance of recalling it drops to this. Pushing to 95% roughly doubles your daily reviews.

Sound

Say the word when the answer showsUses your device voice. Works offline.

Your data

Your deck lives in this browser so review works offline. Clearing site data wipes it, so export now and then.

Import merges: words you already have are left untouched, and your review history comes back with them.

This build

v1.0.0 · 00a7fb9 · 13 Aug 2026

The commit is what actually identifies a build — quote it if something behaves unexpectedly, so there is no doubt about which code is running.