List the US and Canadian jurisdictions Juriset covers, or find one by name. The other Juriset tools take slugs, not names. Each entry has the slug, name, level (country, state, province, county or city) and parent. Examples: Washington or WA → us-wa; Alberta → ca-ab; the federal levels are us and ca. Omit query for all of them. Reads the registry; no rule lookup.

List the kinds of rule Juriset publishes. Each entry has its slug (the rule_type argument of the other tools), domain, description, how jurisdiction levels combine (override, max or stack) and the JSON Schema of its data, with every field described. Examples: minimum_wage and overtime (domain employment). Optional domain filter. Reads the registry; no rule lookup.

Get the rule in force today for one rule type in one jurisdiction, with its citation: source URL, verbatim excerpt and the snapshot Juriset stored. Example: {"rule_type": "minimum_wage", "jurisdiction": "us-wa"}. The response is the API's: data holds the values (described by the JSON Schema at schema_url), effective_from and verified_at date them, id is the version id to record with any decision that relies on it (see resolve_version), and verification says which models extracted and checked it and whether a person reviewed it. Where levels stack (e.g. US federal and state overtime) every level comes back as its own entry in layers; Juriset never merges them. Informational only, not legal advice (disclaimer).

Get the rule that was (or will be) in effect on a date, in the same shape as get_rule. Example: {"rule_type": "minimum_wage", "jurisdiction": "us-wa", "as_of": "2025-06-30"}. Use it to see what applied when a past decision was made. A date before Juriset's coverage of that jurisdiction is answered with an error that says where coverage starts. Informational only, not legal advice. If the API key's plan does not include as-of queries the error says so.

List every version ever published of one jurisdiction's rule, with its effective dates, values, citation and whether it is current, superseded or withdrawn. Example: {"rule_type": "minimum_wage", "jurisdiction": "us-wa"}. Covers that jurisdiction's own rule only; other levels that apply (e.g. us) are separate calls. Each entry's id can be passed to resolve_version. Informational only, not legal advice.

Get one rule type across jurisdictions in one call, each entry in the same shape as get_rule. Example: {"rule_type": "minimum_wage", "jurisdictions": ["us-wa", "us-or", "us-ca"]}. Without jurisdictions, every state and province (or the level you name) is returned: about 3 KB each, 50+ entries. Entries are never merged or ranked. Informational only, not legal advice. as_of needs an API key whose plan includes as-of queries.

List changes to published rules, oldest first: new versions, amendments, corrections and repeals, each naming the rule, the versions moved from and to, the effective date and the version id to pass to resolve_version. Example: {"since": "2026-10-01", "jurisdictions": ["us", "us-wa"]}. Each jurisdiction matches its own rules only, so for everything that changes Washington's answer pass the federal level too. While has_more is true, call again with the response's cursor. Needs an API key whose plan includes the change feed; otherwise the error says so. Informational only, not legal advice.

Get exactly the version a stored id names, forever, even after it was superseded or withdrawn: the values, effective dates, citation, verification record and its status today. Version ids (rv_…) come from the id of any rule response. Use it to re-check the value a decision relied on, or to show an auditor which rule applied. Example: {"version_id": "rv_000000000000000000000000F2"}. Informational only, not legal advice.