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
resolve_domain_jurisdiction
Whose law a domain answers to, and how that is known.
reads
Domain to governing jurisdiction
What it does
Maps a hostname or URL to the operator's home jurisdiction, as one input signal for
feeding into the other tools. Argument: domain. IP addresses are refused: a server's
location is not the legal signal, the operator's establishment is.
It costs one to four upstream requests, not a fixed number: it tries the exact host, then up
to three parent domains, stopping at the first match, and a fall-back to top-level-domain
inference costs nothing further. It is not part of the five-request lint total on the run_lint page; call it
only to derive a jurisdiction rather than declaring one.
Parameters
| Name | Type | Required | What it takes |
|---|---|---|---|
domain | string | yes | Hostname or URL (e.g. "ventura.org"). IP addresses are rejected. |
Example request
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "resolve_domain_jurisdiction",
"arguments": {
"domain": "ventura.org"
}
}
}