Concepts

How a run works

The tools answer a browser and an agent identically, so you can run one by hand to see what your agent will get back.

What LexLint stores

LexLint stores nothing unless you explicitly ask it to: your key is passed through to the UnGovr Open Data API on every call, and the upstream free tier (currently 50 requests per day) is the only meter. The one exception is upload_lint_run, covered in the tool reference: a run reaches the portal only when you upload it yourself from the CLI, after LexLint has shown you exactly what it contains and you have said yes, and it is then kept against your UnGovr account rather than against the stateless worker behind mcp.lexlint.io. Rate-limit and authentication errors come back from upstream unchanged.

What runs on a schedule

The lint itself is deterministic and runs in one place, the stateless worker behind mcp.lexlint.io. It reads the LexLint law library, which is to LexLint what an advisory database is to a dependency scanner. Behind the lint, three things happen on a schedule: the legal news wire is swept every day across every jurisdiction in the law library, and a story that outruns what we hold opens a research request; the law library is rebuilt and republished every day; and every law carries the date it was last checked against its sources, which check_access reports as a range rather than a single flattering figure. Research itself is done by people, in waves, so a law last checked four months ago says so.

Next