Legalcode

Analyze supported corpora with counts, rates, averages, groups, matrices, trends, and actor statistics. Read Discover source_profile first: analyticsStatus and analyticsCapabilities are executable truth for the jurisdiction and source. Use court_case for court-only analysis and case for the broad decision rollup. Analysis may require q or a positive narrowing filter for expensive case aggregates, actor analysis, and high-cardinality matrices. q and a body-text filter target the same text, so provide one. Use measure document_count rather than count. Request sourceRef samples only when the profile explicitly allows them; use Search with matching filters for representative documents otherwise.

legalcode_analyze

Discover the exact Legalcode search contract before querying: source-owning jurisdictions, agreement-party scopes, named sources and scoped sourceCode values, supported fields, bounded facets, prefix-constrained facet values, analytics and relationship readiness, query syntax, costs, and examples. Use mode:"jurisdictions" for corpus owners; mode:"agreement_scopes" for treaty/agreement coverage; mode:"source_profile" with jurisdiction and sourceType for fields and capabilities; mode:"facets" or "facet_values" for stored filter values; and mode:"help" for workflows. Treat case as the broad decision rollup, court_case as confidently classified courts, and agency_decision as administrative, regulatory, or tribunal decisions. Never guess sourceCode or enum values.

legalcode_discover

Inspect one document using a sourceRef copied exactly from Search or Trace. mode:"metadata" returns document context and law-version status. mode:"excerpt" uses q or sectionRef for a targeted passage; supported structured references include Icelandic articles, Irish sections, EU articles, and Icelandic bill commentary sections. Prefer a returned downloadUrl for complete-document retrieval. mode:"full" is a cursor-paginated fallback only when a download is absent or unavailable; follow nextCursor until truncated is false. An official publisher URL is provenance metadata, not a text-retrieval instruction.

legalcode_fetch

Search ranked primary-source candidates and snippets. Choose one jurisdiction and one or more discovered sourceTypes: law (including regulations, narrowed by actType), case (broad decision rollup), court_case, agency_decision, guidance, agreement, pre_law, or patent. Prefer explicit identifier filters such as lawKey, CELEX, ELI, citation, or sourceCode for known instruments. q remains free text and never creates structured filters. Use quoted phrases or flat AND/OR; do not send raw SQL, fielded backend syntax, wildcards, or a language filter. Results include sourceRef and may include a signed downloadUrl; use Fetch for metadata or targeted excerpts and follow response nextAction guidance.

legalcode_search

Trace deterministic indexed relationships rather than ranked text matches. Supported families include cases_for_law, laws_for_case, cited_cases, citing_cases, pre_law_for_law, related_pre_law_flows, eea_incorporation_for_law, implementing_laws_for_eu_law, and eu_law_for_implementing_law. Start from a sourceRef or an exact law, case, citation, or legal-basis key. Short number/year keys require an explicit jurisdiction. Relationship availability and resolution coverage vary by source; inspect Discover source_profile/help before relying on an edge family. After a pre-law trace returns a flow, use Search resultLevel:"document" with its flowKey to enumerate attached documents.

legalcode_trace