The lint
The scanner. It reads what your app declares it does against LexLint's law library and returns the obligations that apply, each with its citation.
What goes in, what comes out
The declaration is the whole input: the activities the app performs, the jurisdictions it operates in, and the roles it plays under the law. No source code, schema or data leaves the repository.
Each finding names the law, the provision and what it asks, with a citation and the date the library last read it. The same declaration returns the same findings, and the lint is free.
One run
Paste this line into Claude Code or Codex. Your agent reads the procedure, writes the declaration from the code, and runs the lint.
No install, no account and no key for the first run. A whole run shows every step and what comes back.
Where it lives
The docs are on developer.lexlint.io: the quickstart, the install guides for Claude Code, Codex and other clients, and the tool reference. Keys and the console are on mcp.lexlint.io.
Before you start: the questions engineers ask, and why not just ask a frontier model.
What it is not
The lint is not legal review. A finding is legal information with a citation, for your team and your counsel to read, and the judgment stays with them.
Its findings go to the portal when you upload a run, and every one is drawn from the library.