nu:legal Deutsches Recht

Ground a batch of German legal citations against the corpus. Call this BEFORE stating any citation you did not read here. Takes the citation in the form you already hold it — including the court name, the dispositive word and the date a model normally writes around a docket. KEEP THEM IN: the court and the date are used to disambiguate. An Aktenzeichen is unique per court, not nationwide, and 21,021 dockets in this corpus are held by more than one decision, so 'OLG Bamberg, 4 U 120/24' resolves to Bamberg's decision where the bare '4 U 120/24' is ambiguous or lands on another court's. Where the string has to be rewritten to be read, the rewrite is reported back under `normalised_from` / `normalised_to`, never silently, and `disambiguated_by` says when it was YOUR court or date that picked the decision out. Where the court you named writes a suffix your citation dropped ('4 U 120/24 e'), the answer carries `docket_completed` with the full Aktenzeichen — cite that one. Accepted kinds: norm citations ('§ 823 Abs. 1 BGB', '§§ 305-310 BGB', 'Art. 83 DSGVO'), Aktenzeichen ('2 C 9.22', '8 AZR 26/18'), ECLI ('ECLI:DE:BGH:2019:180619UVIIIZR247.18.0') and Fundstellen ('BVerfGE 65, 1'). Full prose citations work: 'BVerwG, Urteil vom 24.10.2023 - 2 C 9.22'. It never returns a near match. A miss comes back as `not_in_corpus` (we hold nothing and know of nothing), `attested` / `known_missing` (the decision provably EXISTS — decisions we do hold cite it by Aktenzeichen, and they are listed as the evidence — but we do not have its text), `ambiguous` (with candidates) or `unparseable`. `attested` is not a failure: you may state that the decision exists, cite it, and say the text was not available to you. What you must not do is treat it as `not_in_corpus`. A resolved norm carries `fundstelle`: the gazette citation of the authentic text, which is the citation a court accepts. Our own URL is a reading copy, and for Land law the gazette citation is the only source reference there is. Prefer it in anything you publish. `text` on a resolved norm is a 300-character stub unless you pass `include: ["text"]`, and `text_truncated` says which it is. Never verify a quotation against the stub: it is the head of the provision, not the Absatz you cited. When you supply a date or a court that does not match the decision the docket resolves to, the result carries `date_mismatch` / `court_mismatch` with the actual value. That is the hallucinated-citation case this tool exists for: cite what is actually there, not what you held — and a `court_mismatch` usually means this is not the decision you meant at all.

{
  "type": "object",
  "properties": {
    "citations": {
      "type": "array",
      "minItems": 1,
      "maxItems": 100,
      "items": {
        "type": "string",
        "maxLength": 400
      },
      "description": "The citations, verbatim as you hold them.",
      "examples": [
        [
          "§ 622 Abs. 2 BGB",
          "BVerwG, Urteil vom 24.10.2023 - 2 C 9.22",
          "BVerfGE 65, 1",
          "Art. 83 DSGVO"
        ]
      ]
    },
    "include": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "text",
          "leitsatz"
        ]
      },
      "description": "Opt-in extra payload. 'text' returns a norm's FULL text instead of the 300-character stub — the stub is the same 300 characters whichever Absatz you cited, so never verify a quotation against it. 'leitsatz' returns a decision's whole Leitsatz instead of its preview. An unknown value is refused, not ignored."
    }
  },
  "required": [
    "citations"
  ]
}

One query over BOTH corpora: federal and Land statutes (lexical, with concept pinning) and court decisions (semantic — natural-language questions work well here and are the better shape for case law). Search both unless you have a reason not to. A term of art often does not appear in the statute that governs it: 'Verzugspauschale' matches no provision (§ 288 BGB says 'Pauschale in Höhe von 40 Euro') while 184 decisions use the word. scope='norms' alone will read as 'nothing here' in exactly those cases. CROSS-LAND COMPARISON: a single query returns the parallel provisions of the Bund and of every covered Land side by side, each row jurisdiction-labelled, plus a `by_jurisdiction` roll-up. Ask 'Videoüberwachung öffentlich zugänglicher Räume' and you get BDSG § 4 next to the Land data-protection and police provisions. Full text is held for Bayern, Brandenburg, Nordrhein-Westfalen and Sachsen. Decision hits come back already anchored at the best-matching Randnummer (…#rd_51), so you can quote a paragraph rather than a document, AND carry `doknr` — the key `listCasePassages`, `listCitedAuthorities` and `listCitingDecisions` take, so you can go straight from a search hit to that decision's passages or its authorities without resolving anything first. Query in German; write raw umlauts, they are handled.

{
  "type": "object",
  "properties": {
    "q": {
      "type": "string",
      "minLength": 2,
      "maxLength": 2000,
      "description": "German query. Keywords, a citation, or a full question.",
      "examples": [
        "Kündigungsfrist Arbeitsverhältnis 10 Jahre",
        "Videoüberwachung öffentlich zugänglicher Räume",
        "Welche Rechte hat ein Arbeitnehmer bei verspäteter Lohnzahlung"
      ]
    },
    "scope": {
      "type": "string",
      "enum": [
        "all",
        "norms",
        "cases"
      ],
      "default": "all",
      "description": "'all' (default) searches both. Narrow only when you know which corpus answers."
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 50,
      "default": 10
    },
    "include_repealed": {
      "type": "boolean",
      "default": false,
      "description": "Include repealed (aufgehobene) provisions. Off by default; turn it on when researching an older state of the law."
    }
  },
  "required": [
    "q"
  ]
}

The text of one provision, by default as clean Markdown — about a tenth the size of the reader page for the same provision, with no navigation, no scripts and no boilerplate. `law` is the abbreviation as a citation writes it ('BGB', 'DSGVO', 'BDSG 2018', 'RVG'); `ref` is the bare number, with any letter suffix and no § or Art. ('622', '823', '3a', '83'). Aliases resolve, and CASE IS READ: 'LwG' is the federal Landwirtschaftsgesetz while 'LWG' is a Land statute (Bayern's Landeswahlgesetz, NRW's Landeswassergesetz), so write the abbreviation the way your citation writes it. A spelling that matches no law exactly still resolves case-insensitively, and a miss lists the other laws the abbreviation names under `other_laws`, each with a `law_key` you can call again with. POINT IN TIME: `as_of=YYYY-MM-DD` returns the version stored for that date. Read `version_coverage` on every answer — the version archive begins 2019-06-10, and a date before that answers `outside_coverage` with the law's amendment register attached. That is a limit of our archive and says nothing about whether the provision existed. Every answer carries `first_observed`, `valid_to`, `date_precision` and `amendment_note`. `first_observed` is the day we first saw the text, NOT the legal Inkrafttreten — do not compute a deadline from it without reading `date_precision` (day / week / launch; 'launch' means the date is a floor). TRUST: `fundstelle` is the gazette citation of the authentic text — the citation a court accepts. `authoritative_source` names what our copy is (a consolidated, non-official reading version) and where the binding text lives. Quote the provision from `markdown`; the reader page at `url` carries per-Absatz anchors (#abs-N) if you want to deep-link a single Absatz.

{
  "type": "object",
  "properties": {
    "law": {
      "type": "string",
      "description": "Law abbreviation, or a `law_key` (`slug` in search results) when an abbreviation is ambiguous.",
      "examples": [
        "BGB",
        "DSGVO",
        "RVG",
        "BDSG 2018",
        "SächsDSDG"
      ]
    },
    "ref": {
      "type": "string",
      "description": "Provision number without § or Art. A sub-unit ('Abs. 1', 'lit. f') is dropped: the whole provision is returned.",
      "examples": [
        "622",
        "823",
        "3a",
        "83",
        "28"
      ]
    },
    "as_of": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Return the version stored for this date."
    },
    "format": {
      "type": "string",
      "enum": [
        "markdown",
        "json"
      ],
      "default": "markdown",
      "description": "'markdown' (default, compact, quotable) or 'json' for the structured payload."
    }
  },
  "required": [
    "law",
    "ref"
  ]
}

Every stored version of one provision, newest first, so you can find out which dates `getNorm(as_of=…)` can actually answer before you ask. Each entry carries `first_observed` (the day the text was first seen here — NOT the Inkrafttreten), `valid_to`, `date_precision` and the law-level `amendment_note`. `at_archive_floor: true` marks the version that was current when mirroring began: its date is a floor, not an amendment, and earlier amendments exist that are named in the law's Änderungsverlauf (linked as `amendment_history_url`) but whose text is not held. There is no diff tool: fetch two versions with `getNorm(as_of=…)` and diff them yourself — a diff we computed would hide which side of it came from a floor date.

{
  "type": "object",
  "properties": {
    "law": {
      "type": "string",
      "examples": [
        "BGB",
        "DSGVO"
      ]
    },
    "ref": {
      "type": "string",
      "examples": [
        "288",
        "622"
      ]
    }
  },
  "required": [
    "law",
    "ref"
  ]
}

Incoming citation edges. Give EITHER `law` + `ref` (which decisions apply this statute provision) OR `case` (which decisions cite this decision) — exactly one of the two. Results are ranked by citation weight, then court tier, then recency. Read the ranking honestly: for a provision with many EU decisions the first ten can be almost all CJEU, and the German courts appear only further down. If `total` exceeds what you read, page on with `offset` (`pagination.next_offset`) before concluding anything about national case law. NEWEST FIRST: pass `sort: "recent"` when the question is about current case law ('fünf aktuelle Entscheidungen zu …'). Paging works the same way. This ordering is bounded — for a handful of procedural giants (§ 154 VwGO, § 708 ZPO) it cannot be computed inside the query budget, and then the answer comes back in WEIGHT order and says so in `sort_applied` and `sort_note`. Check `sort_applied` before you describe a list as the most recent decisions. For a decision, each citer carries `citing_rn`: the Randnummer of the CITING decision's own text that holds the citation, as that court numbered it, and the URL is anchored to it. COVERAGE: the graph is built over federal case law. A Land provision can answer `total: 0` because it is not indexed, not because no court has cited it — `coverage.complete_for_this_norm` tells you which, and for a Land provision you should fall back to `search` on the provision's wording.

{
  "type": "object",
  "properties": {
    "law": {
      "type": "string",
      "examples": [
        "DSGVO",
        "RVG",
        "BGB"
      ]
    },
    "ref": {
      "type": "string",
      "examples": [
        "83",
        "3a",
        "288"
      ]
    },
    "case": {
      "type": "string",
      "description": "A juris doknr, an ECLI, or this site's decision URL as `search` returns it.",
      "examples": [
        "ECLI:DE:BAG:2018:250918.U.8AZR26.18.0"
      ]
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 100,
      "default": 20
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "default": 0,
      "description": "Rows to skip, for reading past the first page."
    },
    "sort": {
      "type": "string",
      "enum": [
        "weight",
        "recent"
      ],
      "default": "weight",
      "description": "'weight' (default) is citation weight, then court tier, then recency. 'recent' is newest decision first; where it cannot be computed the answer falls back to 'weight' and says so in `sort_applied`."
    }
  }
}

Outgoing citation edges of one decision: the statute provisions it cites (with how often it cites each — that is the Normenkette, weighted) and the decisions it relies on. `treatment` is null on every edge and stays null. Classifying an edge as gefolgt / abgegrenzt / aufgegeben is unbuilt work, and a wrong 'aufgegeben' in a brief is worse than no label at all. Read the citing passage yourself with `listCasePassages`. A decision we can prove exists but do not hold answers `known_missing`, with the decisions that attest it — not a 404.

{
  "type": "object",
  "properties": {
    "case": {
      "type": "string",
      "description": "A juris doknr, an ECLI, or this site's decision URL as `search` returns it."
    }
  },
  "required": [
    "case"
  ]
}

The full text of one decision, split into its paragraphs, each with a permalink you can cite. `rn` is the Randnummer the COURT printed, read out of the decision's own markup. It is never inferred from position: where a document prints no numbers, `rn` is null and stays null. `anchor_basis` is derived per decision — only 'native_numbering' means our anchor and the printed number provably coincide, so pin-cite a Randnummer only when you see that value. `amtliche_seite` is null everywhere: our texts carry no page breaks, so a BVerfGE-style page pin cannot be produced honestly. SIZE. Long decisions run to several hundred paragraphs, so the default page is 30. Three ways to move: `offset` pages, `limit` widens (max 400 — enough for a whole decision when you really want it), and `around` jumps. `pagination` appears whenever there is more than the page you were handed. `around: 51` returns a window of `limit` passages CENTRED on Randnummer 51 — the right call when `listCitingDecisions` gave you a `citing_rn`, when a search hit came back anchored at …#rd_51, or when you want the passage around a pin cite and not the whole judgment. It takes the number the court printed, not a position, and a decision that prints no such number answers `not_in_corpus` rather than silently handing you a different passage. `around` and `offset` address the same list two different ways; give one.

{
  "type": "object",
  "properties": {
    "case": {
      "type": "string",
      "description": "A juris doknr, an ECLI, or this site's decision URL as `search` returns it."
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "default": 0
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 400,
      "default": 30
    },
    "around": {
      "type": [
        "integer",
        "string"
      ],
      "description": "A Randnummer as the court printed it. Returns a window of `limit` passages centred on it. Not combinable with `offset`.",
      "examples": [
        51,
        "12"
      ]
    }
  },
  "required": [
    "case"
  ]
}

Which provisions got a new text recently, newest first — the freshness feed, as JSON. Poll it with `since` set to the newest `observed` you have already processed. `observed` is the day the new text was FIRST SEEN here, which is not necessarily the day it came into force. Say so if you report a date. The window is the last 120 days; the law's own Änderungsverlauf goes further back.

{
  "type": "object",
  "properties": {
    "since": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Only changes observed on or after this date."
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 200,
      "default": 50
    }
  }
}

Corpus scope with its holes stated. Call this once when your answer depends on whether an absence is real. Returns totals (laws, provisions, versions, decisions, courts, citation edges), the per-source windows, the count of Aktenzeichen we can prove exist and do not hold, and `limits`: the version-archive floor, the federal scope of the citation graph, what a version date actually means, and why source windows differ. Use it to tell `outside_coverage` from `not_in_corpus`. They are different answers and this API never collapses them.

{
  "type": "object",
  "properties": {}
}