Full-text search over federal statutes.

Returns {query, corrected, results[]}. For the few queries that a curated page on this site answers — "wie viel Schmerzensgeld nach einem Unfall", which no statute answers — the response additionally carries pages[]: entries with type: "page", kind, title, url, description and optional stats/updated. The key is absent otherwise, and results is unaffected, so a client that ignores it is correct. Same match as the hint shown above the results on /suche.

This endpoint searches STATUTES. Decisions live at /v1/case-search — and since agent-sim 15.09.2026 every response says so with numbers: cases_available is how many decisions match the same query and cases_url is the call that returns them. The measurement behind that: q=Verzugspauschale answered {"results": []} while 184 decisions used the word, because the term is not in § 288's text (the statute says "Pauschale in Höhe von 40 Euro") — so an API-first agent concluded the corpus held nothing on it and left. An empty results additionally carries suggestions, the /v1/suggest list, rather than being a bare dead end.

cases_available is null when the count could not be measured, which is NOT zero; it is capped (cases_available_capped: true says so), because it is the same bounded probe that fills the Rechtsprechung tab header on /suche.

An unknown query parameter is a 400, not a silent drop.