Docs menu
Get started
Quickstart Install: Claude Code Install: Codex Install: other clients API keysConcepts
How a run works The app profile The severity model What a run does not sayTools
check_access claim_trial_key set_profile run_lint get_law resolve_domain_jurisdiction submit_feedback upload_lint_runGuides
A whole run, end to end Console TestPack in CIReference
Endpoint and transport lexlint.yml schema Errors ChangelogHelp
Support and feedbackTools
get_law
One jurisdiction's law across all eight topics, with its sources.
What it does
One jurisdiction's law, across all eight topics LexLint covers: AI law, scraping and
access legality, personal-data and biometric privacy, product-security and
cyber-resilience law, communications law (marketing messages, calls and texts, call
recording, cookie consent), content-moderation law (liability for what users post, notice-and-takedown, moderation transparency), age-gating and age verification, and reuse law (quotation and snippets, press-publisher rights, linking, news bargaining codes). Returns the instruments
(citation, status, behavior categories, as_of_date) together with the
jurisdiction's crawl posture: an overall crawl-posture reading, a per-scenario access matrix,
robots.txt legal weight, and TDM opt-out status.
Argument: jurisdiction (slug). Resolution walks to the most specific
jurisdiction with data and reports the walk.
It is one call for all eight questions, because it is one payload. It replaced
get_ai_law and get_scraping_law, which returned that same
payload under two names and left privacy with no name at all. Those two names are
gone, not deprecated: a configuration still naming either gets an
unknown-tool error, and the fix is to name get_law.
Parameters
| Name | Type | Required | What it takes |
|---|---|---|---|
jurisdiction | string | yes | Jurisdiction slug, lowercase, "/"-separated (e.g. "us", "us/ca", "eu") |