---
title: "Get the sections around this one"
method: GET
path: "/api/v1/us/statutes/section/{act_id}/related"
tags: ["US Statutes"]
---

# Get the sections around this one

`GET /api/v1/us/statutes/section/{act_id}/related`

## Request

- Base URL: `https://api.vaquill.ai`
- URL: `https://api.vaquill.ai/api/v1/us/statutes/section/{act_id}/related`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`
- TypeScript: <https://skmtc.dev/vaquill/apis/vaquill-developer-api/docs/api/v1/us/statutes/section/:act_id/related/get.ts> (a function with typed inputs; its response is checked against the schema)

The sections immediately before and after a given section, in statutory order.

**Cost**: 2 credits. Not-found and failed lookups are not charged, and neither is an
answer with no neighbour on either side (`note` says why it is empty).

Search cannot answer "what comes next", because relevance ranking is not
statutory order: the definitions a section relies on usually sit a few sections
back and its exceptions a few forward.

Neighbours never cross the containing chapter (or, where a section has no
chapter, the containing title or state code), so you get the sections a reader
would actually turn to, not the numerically adjacent row from an unrelated part
of the corpus.

Neighbours stay within ONE container: the first section of a chapter has an empty
`previous` and the last has an empty `next`, even when the code continues in the
adjacent chapter, part or title (which are not traversed). When that is why a
side is empty, `note` says so, so an empty side is not read as the start or end
of the whole code. Superseded or not-yet-effective versions of a section are
never returned as neighbours, and a section is never its own neighbour.

Ordering is natural, not lexicographic: `9` before `10`, `240.9` before
`240.10`, `1983` before `1983a`.


**Bounded rows.** A heavily amended section (26 U.S.C. 1) carries hundreds of references and a credit line of tens of thousands of characters. Each row keeps the first 50 items of every long list and the first 4,000 characters of `history` and `committeeNote`. A row that was cut carries `responseBounds` (`truncated`, and per field the `total`, what was `returned` and `nextOffset`); a row that was not cut omits it. The whole record is one call away: `GET /us/statutes/section/{actId}?full=true`.

## Path parameters

- `act_id` string, required: Section identifier, e.g. `USC_T42_C21_S1983` (42 U.S.C. § 1983). Take it from a `/us/statutes/search`, `/resolve` or `/divisions` result; do not assemble one. A citation such as `42 USC 1983` also works and adds the `/resolve` price (see `GET /us/statutes/section/{actId}`). State session laws (`SSL_` ids) are read at `/us/session-laws/{sessionLawId}`.

## Query parameters

- `limit` integer: How many sections to return on EACH side.

## Headers

- `Idempotency-Key` string, nullable: Optional. 16 to 255 visible ASCII characters (a UUIDv4 works). Repeating the same request with the same key replays the original 2xx response for 24 hours without charging again. The same key on a different request is rejected. With the account's `cacheQueryDerivedData` retention setting off, no body is stored and a retry answers 409 `idempotency_replay_unavailable`, still without a second charge.

## Response `200`

The section plus its neighbours.

- StatuteNeighborsResponse: Response for `GET /us/statutes/section/{act_id}/related`.
  - `section` StatuteResult, required: A single statute section from search results.
    - `actId` string, required: Unique section identifier (e.g., 'USC_T42_C21_S1983', 'CFR_T17_P240_S240_10b5_1').
    - `citation` string, nullable, required: Full citation (e.g., '42 U.S.C. § 1983 (2024)', '17 C.F.R. § 240.10b5-1 (2026)'). Always present; null when not known.
    - `citationShort` string, nullable, required: Short citation (e.g., '42 U.S.C. § 1983', '17 C.F.R. § 240.10b5-1'). Always present; null when not known.
    - `title` string, nullable, required: Section title. Always present; null when not known.
    - `corpusType` string, nullable, required: The corpus this section belongs to: one of `USC`, `CFR`, `STATE`, `CONSTITUTION`, `FEDERAL_RULES`, `FEDERAL_LOCAL_RULES`, `STATE_CONSTITUTION`, `STATE_RULES`, `EXECUTIVE_ACTION`, `REGULATION`, `FEDERAL_REGISTER`, `FEDERAL_REGISTER_NOTICE`, `AGENCY_GUIDANCE`, `SENTENCING_GUIDELINES`, `US_TAX_TREATY`, `US_TREATY`, `STATE_AGENCY_GUIDANCE`, `STATE_AG_OPINION`, `STATE_REGISTER`, `SESSION_LAW`, `STATUTE_COMPILATION`, `AGENCY_ADJUDICATION`, `CFR_ANNUAL`, `USC_ANNUAL`, `FEDERAL_BILL`, `FEDERAL_RULES_ANNUAL`, `FEDERAL_RULES_PROPOSED`. The same tokens the `corpusType` filter accepts. Always present; null when not known.
    - `state` string, nullable, required: 2-letter lowercase state code (e.g. `ca`, `tx`) when the row belongs to a state corpus. `federal` for federal rows. Always present; null when not known.
    - `source` string, nullable, required: The named source within `corpusType` this row belongs to, for corpora that fold several bodies of law into one token. Pass it back as the `source` search filter to scope to just this source; the accepted values, with their names, are listed on that filter. Null for corpora with only one source, which includes every state's statutes and regulations. Not a link, and not where the text came from: it is a filter token. The official link to the publisher's text is `sourceUrl`.
    - `year` integer, nullable, required: The year this row was ingested, not the year of the law. Most ingesters stamp the capture year (`time.gmtime().tm_year`) and a few pin a literal, so the bulk of the corpus reads the year it was captured. Do not filter or reason about currency with it. `lastAmendedYear` carries the amendment year, `currentThrough` and `currencyNote` carry the publisher's own currency statement, and `goodLawStatus` carries the status. Always present; null when not known.
    - `relevanceScore` number, nullable, required: Relevance score, normalized to roughly 0-1. Higher means a better match for ranking within one response. It is a relative ranking signal, not a calibrated confidence or probability, so do not compare scores across different queries or treat a fixed value as a quality threshold. Exception: a query that resolves to an exact citation (e.g. '42 U.S.C. § 1983', 'Cal. Civ. Code § 1950.5', 'Fed. R. Civ. P. 12') always scores that section 1.0, since it is a certain match rather than a ranked one -- a natural-language or keyword query never returns 1.0 by comparison. null on any endpoint that did not rank: fetching a section by id, a batch fetch, or a section embedded in an intelligence response. When the response carries `rankingDegraded: true`, the relevance model was unavailable and this is a retrieval score on a different, much smaller scale: still a valid ORDER, not a 0-1 relevance.
    - `excerpt` string, required: Text excerpt (up to 500 characters).
    - `body` string, nullable, required: Full plain text of the section. Always a key on the row: filled only when the request set `includeBody: true`, and null otherwise and on any row whose text could not be resolved (those rows are not charged for a body). A section the publisher prints as images has no text: its `body` is null and `bodyUnavailable` is `true`. This is the actual statutory text, not the `excerpt`. The two are different things and the difference matters for quoting: `excerpt` is a ranking preview windowed around the match, so it can begin mid-section and drop a leading subsection marker -- measured 2026-09-02, four of five California rows lost their opening `(a) `. `body` is the document as the publisher printed it.
    - `bodyUnavailable` boolean, nullable: Present, and `true`, only on a section that has no text to return: the publisher prints it as images (an appendix, a form, a map), or the text we hold is only a partial copy of the official text. Omitted on every other section. The section is real and its metadata is complete; there is simply no body, so `body` / `plain` / `html` are null, `available` is false on `/body`, and nothing is charged for a body. Read it instead of treating a null body as a fetch failure that is worth retrying.
    - `bodyUnavailableReason` 'image_only_source' | 'misfiled_source_text' | 'partial_snapshot_text', nullable: Why there is no body, present with `bodyUnavailable`. `image_only_source`: the publisher prints this section as images, so there is no text to extract. Where we hold an official link for the section it is in `sourceUrl`; it is null where we may not republish the publisher's link. `misfiled_source_text`: the text stored under this regulation opens with another rule's number (a prior version filed under a renumbered rule), so it is withheld rather than served as this rule. `partial_snapshot_text`: the text we hold for this section is only a partial copy of the official text, so it is withheld rather than served as if it were complete. Omitted from the response when it has no value.
    - `bodyNote` 'fetch_failed' | 'no_text' | 'insufficient_credits' | 'response_size_cap', nullable: Present only when the request set `includeBody: true` and this row's `body` is null for a reason on our side or yours, so a null body is never silent. `fetch_failed`: reading the text failed this time, retry; not charged. `no_text`: the read succeeded but returned no text for this section; not charged. `insufficient_credits`: your balance could not cover the bodies, so every body on the page was withheld (the ranking you paid for is intact); top up and repeat the call. `response_size_cap`: a batch response carries at most 4,000,000 characters of inline body text, and this row's body was dropped to stay under it; not charged, fetch it from `/section/{actId}/body`. A section printed as images carries `bodyUnavailable` instead.
    - `bodyServedNote` string, nullable: Present only when the request set `includeBody: true` and the `body` on this row is not the section's preferred copy: a lesser copy was served because the preferred one could not be read this time, a rendered table or figure was withheld, or the text is partial. The same words `/section/{actId}/body` returns in `note`. Not cached, so a repeat call may return the preferred copy.
    - `matchContexts` BooleanMatchContext[], nullable: Present only with `matchType: "boolean"`: up to 3 passages showing where this section satisfied the expression, in the order they appear in the section. Highlights follow the engine that decides membership: every conjunct of an AND, the OR branches that matched, the words of a phrase, both operands of a satisfied `/N`, `/s` or `/p` pair, the occurrences counted by `atleastN`, and for `a NOT W/N b` the `a` that has no `b` in range. A NOT never highlights anything. Unlike `excerpt` (the passage the relevance model ranked, which may not contain your terms), these passages always do. Empty (`[]`) when the expression matched only in the heading or citation (`title( )`, `cite( )`). Absent on a row whose passages could not be prepared within the search's time allowance; the row is still a verified match. Contexts never change which sections are returned, their order, or the price.
      - `text` string, required: About 240 characters of the section's text as published, cut on word boundaries, with each run of whitespace (line breaks included) shown as one space and soft hyphens removed (a word hyphenated across a line break is joined). It can begin and end mid-sentence.
      - `highlights` array[], required: The words that satisfied the expression, as `[start, end]` character offsets into `text` (start inclusive, end exclusive, counted in Unicode code points, so `text.slice(start, end)` in JavaScript holds only for text without astral characters; Python's `text[start:end]` always does). Sorted, never overlapping. Offsets point at the text as printed, which matching normalizes: a highlight for `section` can cover `§`, one for `café` can cover `CAFÉ` or a decomposed accent, and one for a phrase covers the whole phrase. Plain offsets, not markup, so you choose how to style them.
        - integer[]
    - `titleNumber` string, nullable, required: USC/CFR/state title number (e.g. '26', '13A'). Always present; null when not known.
    - `titleName` string, nullable, required: Title name (e.g., 'The Public Health and Welfare'). Always present; null when not known.
    - `chapter` string, nullable, required: Chapter number or identifier. Always present; null when not known.
    - `chapterName` string, nullable, required: Chapter name. Always present; null when not known.
    - `sectionNumber` string, nullable, required: Section number (e.g., '1983', '240.10b5-1'). Always present; null when not known.
    - `sectionTitle` string, nullable, required: The section's own heading (e.g., 'Rule G. Forfeiture Actions In Rem'). Distinct from `title`, which is the hierarchical display path. Always present; null when not known.
    - `displayPath` string, nullable, required: Full hierarchical path (Title > Chapter > Section). Always present; null when not known.
    - `breadcrumb` object[], nullable, required: Structured breadcrumb trail for navigation. Always present; null when not known.
    - `parent` object, nullable, required: Query for `GET /us/statutes/divisions` that lists this section's siblings (its containing chapter, part, code, article or federal rule set). Pass it straight back to walk up the hierarchy, or spread it into a `POST /us/statutes/search` body to search within that container: every key it carries is also a search filter. Null when the container cannot be determined.
    - `subchapter` string, nullable, required: Subchapter number or identifier. Always present; null when not known.
    - `subchapterName` string, nullable, required: Subchapter name. Always present; null when not known.
    - `part` string, nullable, required: Part number or identifier (CFR/state). Always present; null when not known.
    - `partName` string, nullable, required: Part name. Always present; null when not known.
    - `subpart` string, nullable, required: Subpart number or identifier (CFR). Always present; null when not known.
    - `subpartName` string, nullable, required: Subpart name. Always present; null when not known.
    - `popularName` string, nullable, required: Popular/common name of the act (e.g. 'Truth in Lending Act'), when known. Always present; null when not known.
    - `actStatus` string, nullable, required: Raw section status: `in_force`, `repealed`, `renumbered`, `transferred`, `omitted`, `reserved`, `vacant`, or `unconstitutional`. Some corpora also use `superseded` (a prior version), `enacted`, `pending` and `non_precedential`. This is the status recorded for the section; the currency verdict is `goodLawStatus`. Always present; null when not known.
    - `goodLawStatus` string, nullable, required: Derived currency verdict: `good_law`, `not_good_law`, `not_operative`, or `unknown`. `unknown` means no currency verdict is asserted for the section, which is different from out of date. It is returned where a jurisdiction does not publish repeal information (state statutes for California, for example, are stored `in_force` with `goodLawStatus: unknown`: the stored status is the publisher's own, and we do not certify it current because that state's repeal markers have not been verified), and for these corpora by design: attorney general opinions, register notices, statute compilations, the U.S. Code, executive actions and treaties. Annual editions (`cfr_annual`, `usc_annual`) return `not_good_law` because a later edition supersedes them. Read `corpusType` beside this field. `null` when currency checking is disabled.
    - `goodLawBasis` string, nullable, required: Why `goodLawStatus` has the value it has, as a short code; `null` exactly when `goodLawStatus` is `null`. `good_law`: `in_force` (recorded in force, in a jurisdiction whose repeal information we track). `not_good_law`: `repealed_or_moved` (repealed, renumbered, transferred or recodified), `past_edition` (an annual edition later editions supersede), `proposal` (a bill or proposed rule, never law at any stage), `superseded_by_later_guidance` (IRS guidance a later document superseded, obsoleted or revoked in full), `later_rule_removed` (a Federal Register final rule a later final rule removed from the CFR) or `later_order_revoked` (an executive order a later one revokes or supersedes in full). For the last three `supersededBy` names the later document, and for the last `actStatus` reads `revoked` or `superseded`. `not_operative`: `reserved_or_inactive` (reserved, vacant or unfunded), `not_yet_effective` (a future effective date is printed in the heading, or a final rule's `frEffectiveOn` is ahead) or `publisher_marker` (the publisher's own bracketed note in the heading). `unknown`: `no_repeal_signal` (the publisher gives no repeal markers to check its stored status against), `frozen_snapshot` (served from an edition frozen at a past date), `stated_as_of_date` (current only to the date the text states), `no_status`, `text_omitted_by_publisher` (the legislature prints only a placeholder such as 'Amendatory provisions; text omitted'; `currencyNote` says so) or `status_unrecognized`.
    - `currencyNote` string, nullable, required: Source's 'current through ...' note, when published. Always present; null when not known.
    - `renumberedTo` string, nullable: Where the publisher says this section went, when `actStatus` is `renumbered`. RAW SOURCE FORM, not an `actId` and not a citation: `self:4651` means section 4651 of this same title, `34:10105` means section 10105 of Title 34. Do not pass it to a section endpoint. Read `renumberedToLabel` instead, or resolve the citation it names through `/us/statutes/resolve`. Omitted from the response when it has no value.
    - `renumberedToLabel` string, nullable: `renumberedTo` written out, e.g. `section 10105 of Title 34`. Present whenever `renumberedTo` is. Omitted from the response when it has no value.
    - `transferredTo` string, nullable: Where the publisher says this section went, when `actStatus` is `transferred`. Same raw source form as `renumberedTo`, and the same warning: it is not an `actId`. Omitted from the response when it has no value.
    - `transferredToLabel` string, nullable: `transferredTo` written out. Present whenever `transferredTo` is. Omitted from the response when it has no value.
    - `issueDate` string, nullable, required: Issue/publication date of this version, as `YYYY-MM-DD`, when known. See `issueDateRaw` for the publisher's wording on the rare source that does not print ISO. Always present; null when not known.
    - `issueDateRaw` string, nullable: The issue date as the publisher writes it, present only when it differs from `issueDate`. Null across the corpus today; it exists so a source that starts printing prose cannot silently put prose in a field documented as a date.
    - `crossReferencesCfr` string[], nullable: CFR cross-references parsed from the text, e.g. `['1.6011-4']`. Omitted from the response when it has no value.
    - `crossReferencesCfrChecked` CfrReferenceCheck[], nullable: Each distinct entry of `crossReferencesCfr`, checked against the sections we hold. Only populated on `GET /us/statutes/section/{actId}` for a CFR section with references; null on search results and when the check could not be made, in which case treat the raw list as unchecked. Omitted from the response when it has no value.
      - `reference` string, required: The reference exactly as stored in `crossReferencesCfr`.
      - `title` integer, nullable: CFR title the reference names or was assumed to name. Null if malformed.
      - `section` string, nullable: Section number with sentence punctuation removed (`80.1426.` is `80.1426`).
      - `status` 'held' | 'not_held' | 'malformed', required: `held`: this exact section is in the corpus (fetch it by `actId`). `not_held`: no section with this exact number is held in that title; it may be a truncated stem, a part we do not hold or an extraction error. We never substitute a nearby section. `malformed`: not shaped like a CFR section number.
      - `actId` string, nullable: The held section's id, when `held`.
      - `titleAssumed` boolean: True when the reference carried no title and the citing section's own title was assumed. Such a reference can point at another title.
    - `crossReferencesUsc` string[], nullable: USC cross-references parsed from the text, e.g. `['42:1983']`. `'self:<section>'` denotes a reference to another section of the same title. Omitted from the response when it has no value.
    - `statutoryAuthority` object[], nullable: For a CFR/eCFR section: the USC (or other) citations in its 'Authority' note that authorize the rule, e.g. `[{'type': 'usc', 'title': 15, 'section': '78o', 'display': '15 U.S.C. 78o'}]`. Null for non-regulation corpora. Omitted from the response when it has no value.
    - `implementingRegulations` object[], nullable: For a USC section: the CFR parts that implement it, derived from the reverse of every CFR section's own `statutoryAuthority`, e.g. `[{'cfrTitle': 17, 'part': '240', 'partName': '...', 'display': '17 CFR Part 240'}]`. Null for non-USC corpora. Omitted from the response when it has no value.
    - `frRegulationIdNumbers` string[], nullable: Regulation Identifier Number(s) (RIN) assigned to this rule. Omitted from the response when it has no value.
    - `frDocketIds` string[], nullable: Rulemaking docket ID(s) this document was filed under. Omitted from the response when it has no value.
    - `frEffectiveOn` string, nullable: The rule's effective date (ISO 8601 date), when set. Omitted from the response when it has no value.
    - `frCommentsCloseOn` string, nullable: Public-comment deadline (ISO 8601 date). Proposed rules only. Omitted from the response when it has no value.
    - `frSignificant` boolean, nullable: Whether the Federal Register marked this rule 'economically significant' (EO 12866). Omitted from the response when it has no value.
    - `frCorrectionOf` string, nullable: Federal Register document number this document corrects, when this is a correction. Omitted from the response when it has no value.
    - `frCorrections` string[], nullable: Federal Register document number(s) that later corrected this document. Omitted from the response when it has no value.
    - `frRegulationsDotGovUrl` string, nullable: Link to this document's public comment docket on regulations.gov. Omitted from the response when it has no value.
    - `frRelatedDocuments` FrRelatedDocument[], nullable: Other Federal Register documents sharing this document's RIN(s) (its proposed rule, its final rule, and any corrections), most recent first. Only populated on `GET /us/statutes/section/{actId}` for a row that carries `frRegulationIdNumbers`; always null on `/us/statutes/search` results, since computing it needs a follow-up lookup that is too expensive to run per search result. Omitted from the response when it has no value.
      - `actId` string, required
      - `citation` string, nullable
      - `title` string, nullable: The related document's own title/heading, when known.
      - `documentType` string, nullable: `proposed_rule`, `final_rule`, or the raw Federal Register category otherwise.
      - `publicationDate` string, nullable: Federal Register publication date (ISO 8601 date), when known.
    - `frRelatedDocumentsNote` string, nullable: Set only when `frRelatedDocuments` is absent for a reason you should know: this document's RIN is shared by more than 25 other Federal Register documents (an umbrella RIN), so it names no single rulemaking and listing any subset would be a guess; or the related-document lookup was temporarily unavailable, so the list may be incomplete and a repeat call returns it. In that case the call is refunded (`creditsConsumed` is 0). Omitted from the response when it has no value.
    - `subject` string, nullable: The publisher's own subject or document-type label, where it prints one (for example a state insurance bulletin's `RE:` line, or its listing category such as `Rescission`). Omitted from the response when it has no value.
    - `rescindedOn` string, nullable: The date the document was rescinded or withdrawn, as `YYYY-MM-DD`, when the source states one. See `rescindedOnRaw`. Omitted from the response when it has no value.
    - `rescindedOnRaw` string, nullable: The rescission date as the publisher writes it, present only when it differs from `rescindedOn`.
    - `sourceCredit` string, nullable: The Office of the Law Revision Counsel's credit line for a USC section: the acts that enacted and amended it, in order, e.g. `June 25, 1948, ch. 646, 62 Stat. 869; Pub. L. 85-508, Sec. 12, July 7, 1958, 72 Stat. 348`. Parentheses stripped, whitespace normalized. USC only, and null on a USC section that prints no credit (a transferred, repealed or reclassified stub). CFR sections carry the same fact as a list in `federalRegisterCitations` instead, which is why the shape differs; no other corpus publishes one. Omitted from the response when it has no value.
    - `amendmentYears` integer[], nullable, required: Distinct years the section was amended, parsed from the publisher's history note. Always newest first, and de-duplicated. Ingesters store the array in both orders (eCFR writes newest first, state regulations and state statutes write oldest first), so the order is imposed at serve time and the served order is the only one to rely on. Years outside 1789..(current year) are dropped rather than served: amendment dates are parsed out of prose and a note can yield a sunset or substitution date that is not an amendment at all. Always present; null when not known.
    - `lastAmendedYear` integer, nullable, required: Most recent amendment year, when known. Re-derived at serve time as `max(amendmentYears)`, so it never exceeds the list served beside it. Falls back to the publisher's own scalar only when `amendmentYears` is empty, and only when that scalar is itself within 1789..(current year). Always present; null when not known.
    - `amendmentsCount` integer, nullable, required: How many amendments the publisher recorded for this section. Not the length of `amendmentYears`, and it is not safe to derive one from the other. For regulations and court rules this counts amending EVENTS: one per register citation, filing or history entry, so a section amended twice in the same year counts 2 against a single entry in `amendmentYears`. The two disagree on a large share of the regulation and court-rule corpora, so read each for what it is. For the other corpora, and for any source that publishes no per-event record, it is the number of distinct years and is capped at the length of `amendmentYears`, so it never counts a year the list dropped as implausible; it understates a section amended twice in one year. Always present; null when not known.
    - `currentThrough` string, nullable, required: How current the publisher says this text is, in the publisher's own terms. A date (`2025-01-06`) on every USC section and most compilations; otherwise the publisher's wording (`Current through Act 9046 of the 2025 session`, `Public Law 119-60`, `Supp. 19-2`, `2024 Edition`). Do not parse it as a date without checking its shape. `currencyNote` carries the same fact as prose where a publisher writes it that way. Always present; null when not known.
    - `pendingAdoptions` object[], nullable: New York only. State Register adoption notices that post-date the print volume this section's text was taken from. They are notices, not an updated consolidated text: `text` and `body` still reflect `currentThrough` / `currencyNote`. Look the notice up in the State Register by its `idNo`. Each entry: `idNo` (e.g. `DFS-23-26-00013-A`), `scope` (`section` when the notice names this section, `part` when it names the Part containing it), `effectiveDate` (ISO date, null if the notice states none), `agency`, `issueDate` (ISO date of the Register issue). No link is returned; it is withheld under licence, as with `sourceUrl` on these regulations. Only adoptions (`-A`, `-AA`) are listed, never proposals, emergency rules or withdrawals. Null on every section with no such notice, which does not mean the section is current: we cover Register adoptions for NYCRR Titles 3, 19 and 23 only. Omitted from the response when it has no value.
    - `adoptedAfterCurrentThrough` boolean, nullable: New York only. True when `pendingAdoptions` is non-empty, i.e. the State Register records at least one adoption naming this section or its Part that post-dates the volume `currentThrough` refers to, so the text served may be out of date. Null (never false) when no such adoption is recorded; null is not a claim that the text is current. Omitted from the response when it has no value.
    - `amendmentHistory` string[], nullable: Structured amendment entries where the publisher records them separately from the credit line in `history`. Omitted from the response when it has no value.
    - `amendmentHistoryNote` string, nullable: Present only when the section carries no amendment evidence and its state or document type does not record enough amendment history to read absence as a fact (for example New York, Massachusetts, Arizona and West Virginia statutes, several states' regulations, court rules and constitutions, opinions, register notices, bulletins, annual CFR editions and session laws). It says `amendmentYears`, `lastAmendedYear` and `amendmentsCount` are absent because nothing was recorded, not because the section is unamended; `amendmentsCount` is then null rather than 0. Also present on a Maryland section whose `history` is generated from General Assembly session data rather than a publisher credit line. Null where history is recorded, and an empty history there does mean the section has not been amended.
    - `fieldAbsenceNote` string, nullable: Present only when `year` or `effectiveDate` is null AND the ingester of this whole document type never records it (state constitutions carry no `year`; federal local court rules rarely carry a `year` or `effectiveDate`, as of 2026-10-31). It says the field is null because nothing was recorded, which is not a claim that the document has no such date. Null otherwise.
    - `citationNote` string, nullable: Present only on a state-constitution unit the source gives no section number (an amendment, preamble, schedule or whole article). `citation` is then the article-level form without a section sign, and `sectionNumber` is null. Absent otherwise.
    - `responseBounds` ResponseBounds: Whether the default response is the whole record, and if not, what is missing.
      - `truncated` boolean, required: True when at least one field below was shortened. False means this response carries the whole record. Nothing is dropped silently: every shortened field is listed in `fields`.
      - `fields` BoundedField[]: Every field shortened in this response. Empty when `truncated` is false.
        - `field` string, required: The response field that was shortened, by its response name.
        - `unit` 'items' | 'characters', required: `items` for a list, `characters` for the verbatim `history` credit line.
        - `total` integer, required: How many items (or characters) the record holds.
        - `returned` integer, required: How many items (or characters) this response carries.
        - `nextOffset` integer, required: Zero-based position of the first omitted item (or character) in the full value. What follows it is the omitted part: request `full=true` to receive it.
      - `note` string, nullable: Plain-language statement of what was cut and how to get all of it. Present only when `truncated` is true.
    - `sourceNote` string, nullable: The publisher's source note for the section, verbatim. Omitted from the response when it has no value.
    - `effectiveDate` string, nullable, required: When THIS version took effect, as `YYYY-MM-DD`, or null when the publisher's own string does not name one unambiguous day we can read without guessing. On a section with `actStatus=superseded` this is the start of that version's window. The publisher's wording is preserved in `effectiveDateRaw` whenever it differs.
    - `effectiveDateRaw` string, nullable: The date exactly as the publisher writes it, present only when it differs from `effectiveDate`. A section whose publisher already prints ISO leaves this null. Expect prose (`September 8, 1916`), abbreviated months (`Feb. 25, 1868`), US numerics (`9/28/15`), Spanish for Puerto Rico (`26 de junio de 1963`), and values that are not a single date at all (`April 1, 2023 to June 30, 2026`), which is why they cannot be published under `effectiveDate`.
    - `historyEffectiveDate` string, nullable, required: When this version took effect, as `YYYY-MM-DD`, read out of the publisher's amendment credit line in `history`, which is returned beside it as the evidence. A weaker fact than `effectiveDate` (a date the publisher put in a date field), so it is populated only where `effectiveDate` is null. It is the newest commencement the credit line names, and null whenever that cannot be stated without guessing: a credit line that dates only some entries, a date that belongs to a repeal, sunset, applicability rule or another section, a commencement still in the future, a date older than `lastAmendedYear`, or a state whose `history` format we have not measured. Statutes only.
    - `priorEffectiveDates` string[], nullable: Earlier effective dates recorded for the section, each as `YYYY-MM-DD`, in the order the publisher lists them. A publisher's list written as one string (`3-15-22; 7-1-26`) is split into its dates. A value that names no single day (`March 2007`, `immediately`) is not here: it is in `priorEffectiveDatesRaw`. Omitted from the response when it has no value.
    - `priorEffectiveDatesRaw` string[], nullable: The publisher's own wording of `priorEffectiveDates`, one string per stored entry, present only when it differs from the ISO list or holds an entry that names no single day. Nothing the publisher recorded is dropped.
    - `history` string, nullable, required: The publisher's own amendment/history credit line, verbatim, e.g. `Effective 5/4/2005; Superseded 8/1/2016`. `amendmentYears` is parsed from this; keep both when you need the exact wording. Always present; null when not known.
    - `supersededBy` string, nullable: `actId` of the section that replaced this one. Present on a superseded version so you can fetch the current text in one hop via `GET /statutes/section/{actId}`. Omitted from the response when it has no value.
    - `supersedes` string, nullable: `actId` of the earlier version this section replaced, when known. Omitted from the response when it has no value.
    - `pendingAmendments` PendingAmendment[], nullable: Federal Rules only: the amendments proposed to this rule that are not yet in force, each with its lifecycle `status`, `cycle`, `effectiveDate`, `commentPeriodEnd`, `sourceUrl` and `textComplete`. Fetch one with `GET /us/statutes/section/{id}`. Absent on every other section and on a rule with nothing pending. A proposal is never law until its effective date: the text above is the rule in force.
      - `id` string, required: `actId` of the proposed amendment. Fetch it with `GET /us/statutes/section/{id}` or `/body`; it is never returned by an unscoped search.
      - `status` string, nullable: Where the proposal is in the Rules Enabling Act process: `published_for_comment`, `approved_by_standing_committee`, `approved_by_judicial_conference`, `transmitted_to_supreme_court`, `adopted_by_supreme_court` or `transmitted_to_congress`. A proposal that is in force or withdrawn is not listed here.
      - `cycle` integer, nullable: The rules cycle (the year the amendment is meant to take effect).
      - `effectiveDate` string, nullable: The date the amendment takes effect if it is adopted unchanged (ISO 8601 date).
      - `commentPeriodEnd` string, nullable: Last day of the public comment period (ISO 8601 date), when one applies.
      - `sourceUrl` string, nullable: The official page the proposal was taken from, when we hold a link we may publish.
      - `textComplete` boolean, nullable: `true` when the proposed text we hold is the whole amended rule; `false` when it is partial (for example only the changed paragraphs).
      - `commentDocketIds` string[]: Rulemaking docket ids that hold the public comments on this proposal. Each resolves on `GET /us/rulemaking/dockets/{docketId}`. Empty when none is known.
    - `ruleSet` string, nullable: For court rules, the rule family this belongs to, e.g. `North Dakota Rules of Civil Procedure`. Rule numbers repeat across families (a Civil Rule 12 and a Criminal Rule 12 both exist), so this is what disambiguates them. Omitted from the response when it has no value.
    - `publicLaws` string[], nullable: Public Laws referenced by the section, e.g. `['Pub. L. 96-170']`. Omitted from the response when it has no value.
    - `federalRegisterCitations` string[], nullable: Federal Register citations associated with the section, e.g. `['48 FR 3956', '49 FR 15073']`. This is the CFR's form of the credit line `sourceCredit` carries for the USC: the rulemakings that established and amended the section. Populated on 37.4% of CFR sections, empty where eCFR prints no source note. Omitted from the response when it has no value.
    - `granuleId` string, nullable: govinfo granule identifier (USC/CFR provenance). Omitted from the response when it has no value.
    - `packageId` string, nullable: govinfo package identifier (USC/CFR provenance). Omitted from the response when it has no value.
    - `htmlUrl` string, nullable, required: HTML version of the statute section. Always present; null when not known.
    - `pdfUrl` string, nullable, required: PDF version of the statute section. Always present; null when not known.
    - `xmlUrl` string, nullable, required: XML version of the statute section. Always present; null when not known.
    - `textUrl` string, nullable, required: Plain-text version of the section, from the open-data copy we hold in our own storage. Populated for many state corpora (MS, NJ, NY, NV, etc.) and for United States Code sections. The URL is public by design: the text is open data, so it opens without an API key and carries no credit charge. Null when we hold no plain-text copy. It is never a commercial platform's link.
    - `docxUrl` string, nullable: Microsoft Word (DOCX) version, when available. Omitted from the response when it has no value.
    - `stateHtmlUrl` string, nullable, required: HTML rendering of the document. For most state corpora this is the publisher's own page; for corpora we mirror (state agency guidance, regulations, court rules) it is our archived copy of the artifact the publisher served, on statutes-us.vaquill.ai. Use `externalUrl` for the publisher's canonical address. Never a PDF: a mirrored PDF is served as `pdfUrl` instead. Populated for state corpora only. Always present; null when not known.
    - `govInfoHtmlUrl` string, nullable: Official govinfo.gov HTML version. Omitted from the response when it has no value.
    - `govInfoPdfUrl` string, nullable: Official govinfo.gov PDF version. Omitted from the response when it has no value.
    - `abstract` string, nullable: The issuing agency's own summary of the document, as published in the Federal Register. Populated on 99.9% of rules and proposed rules, so a document can be triaged without fetching the full text. Omitted from the response when it has no value.
    - `agencies` string[], nullable: Issuing agencies, by name. Populated on 99.9% of Federal Register documents. Pair with `agencySlugs` when you need the token the `agency` search filter takes. Omitted from the response when it has no value.
    - `agencySlugs` string[], nullable: The issuing agencies as slugs. These are exactly the values the `agency` filter on `/us/statutes/search` accepts, so an agency facet can be round-tripped straight back into a query. Omitted from the response when it has no value.
    - `topics` string[], nullable: The Federal Register's own CFR-index subject terms. Populated on ~71% of rules and ~68% of proposed rules, with one hard boundary: documents published before 2000 carry none, because the Federal Register did not index them this way. Omitted from the response when it has no value.
    - `documentTypeLabel` string, nullable: The instrument type as the publisher names it: `Rule`, `Proposed Rule`, `Presidential Document`, `Declaratory Ruling`, `Resolution Agreement`. Deliberately not `corpusType`, which says which body of law a document belongs to: two documents in one corpus can be very different instruments. Omitted from the response when it has no value.
    - `documentSubtype` string, nullable: Finer instrument class where the publisher gives one. On presidential documents this separates an executive order from a proclamation, a memorandum or a notice (~90% populated there). Omitted from the response when it has no value.
    - `action` string, nullable: The Federal Register's own ACTION line, ~100% populated. Carries distinctions no other field makes: interim final rule, direct final rule, withdrawal, reopening of the comment period. Omitted from the response when it has no value.
    - `president` string, nullable: The president in office for this document, on Federal Register and presidential-document corpora spanning 1994 to present. Omitted from the response when it has no value.
    - `signingDate` string, nullable: When a presidential document was signed, as `YYYY-MM-DD`, which is routinely earlier than `publicationDate` and is the legally operative date. See `signingDateRaw`. Omitted from the response when it has no value.
    - `signingDateRaw` string, nullable: The signing date as the publisher writes it, present only when it differs from `signingDate`.
    - `executiveOrderNumber` string, nullable: The executive order number a lawyer cites the order by (`14179` for Executive Order 14179 of January 23, 2025). Set only on executive orders; the `citation` is the Federal Register page, not this. See `instrumentNumberSource` for where the value came from. Omitted from the response when it has no value.
    - `proclamationNumber` string, nullable: The proclamation number (`10886` for Proclamation 10886). Set only on proclamations. Memoranda, determinations and notices are not numbered in either series and carry null in both fields, never an invented number. Omitted from the response when it has no value.
    - `instrumentNumberSource` string, nullable: Provenance of `executiveOrderNumber` / `proclamationNumber`. `stored` is the number recorded when the document was ingested. `derived_from_text` is read at request time from the document's own header line (`Executive Order 14179 of January 23, 2025`), accepted only when that line opens the document and its date equals `signingDate`; it is null when the header is not in the text returned (for example a later chunk of a search hit), which means unknown, not unnumbered. Omitted from the response when it has no value.
    - `datesText` string, nullable: The verbatim DATES block from the Federal Register, ~98% populated. Worth reading alongside `frEffectiveOn`: a rule with staged or conditional effective dates has them here, and the single date flattens that away. Omitted from the response when it has no value.
    - `frVolume` integer, nullable: Federal Register volume, the `66` in `66 FR 64768`. Omitted from the response when it has no value.
    - `frStartPage` integer, nullable: First Federal Register page, the `64768` in `66 FR 64768`. Omitted from the response when it has no value.
    - `frEndPage` integer, nullable: Last Federal Register page. With `frStartPage` this gives the page RANGE, which `citation` cannot express because it carries only the first page. Omitted from the response when it has no value.
    - `wordCount` integer, nullable: Words in the full document, so a caller can size a fetch before paying for the body. Omitted from the response when it has no value.
    - `issuingAgency` string, nullable: The body that promulgated or issued this document: the state agency behind a regulation, the division behind an agency letter. Populated at 83.6-100% across the state-regulation corpora that carry it. Omitted from the response when it has no value.
    - `adoptingCitations` string[], nullable: Citations to the instrument that ADOPTED this rule: the state register notice, the Washington filing number, the adopting order. The rulemaking audit trail. Unified across four different payload spellings, so this is comparable across states in a way the underlying data is not. These are also the independent way to confirm a section when the publisher's own page cannot be read without a browser (see `externalUrl`): a Texas rule's `['50 TexReg 8285']` names the Texas Register issue and page that printed its adoption. Omitted from the response when it has no value.
    - `lawImplemented` string, nullable: The statute this rule IMPLEMENTS, as distinct from `statutoryAuthority`, which is the statute granting the rulemaking power. Florida populates both and they differ. Omitted from the response when it has no value.
    - `lastAmendedDate` string, nullable: Full date of the most recent amendment, as `YYYY-MM-DD`, where the publisher gives one. See `lastAmendedDateRaw` for the wording. Illinois and Colorado regulations carry their amendment provenance only here and in `amendmentNote`: neither state has a `history`, and Colorado has no `effectiveDate` either, so for Colorado this is the only date that exists. Omitted from the response when it has no value.
    - `lastAmendedDateRaw` string, nullable: The last-amended date as the publisher writes it, present only when it differs from `lastAmendedDate`, or null when it is not a date at all.
    - `amendmentNote` string, nullable: The publisher's amendment credit line where it is stored separately from `history`. Illinois and Colorado regulations, ~72% populated. Omitted from the response when it has no value.
    - `currencyYear` integer, nullable: Machine-readable counterpart to `currencyNote`, which is prose. 100% populated on the nine state-regulation corpora that carry a currency statement. Omitted from the response when it has no value.
    - `reviewDate` string, nullable: The date a rule must be re-adopted or it expires, where the state runs a sunset review. Ohio regulations, ~80% populated. Not an amendment date: it is in the future. Omitted from the response when it has no value.
    - `reviewDateRaw` string, nullable: The review date as the publisher writes it, present only when it differs from `reviewDate`, or null when it is not a date at all.
    - `originalEnactmentDate` string, nullable: When the section was FIRST enacted, as `YYYY-MM-DD`, ~72% populated on the US Code. Deliberately separate from `effectiveDate`: merging them would report an amended section as effective from its original year. On 35.7% of US Code points this is the only enactment date we hold. See `originalEnactmentDateRaw` for the publisher's wording. Omitted from the response when it has no value.
    - `originalEnactmentDateRaw` string, nullable: The enactment date as the publisher writes it, present only when it differs from `originalEnactmentDate`. The US Code prints `Aug. 14, 1935` where GovInfo statute compilations print `1935-08-14` for the same fact.
    - `releaseDate` string, nullable: When the document was released publicly, where that differs from when it was issued. NLRB advice memoranda are written years before release; measured, the two dates are never equal. Omitted from the response when it has no value.
    - `releaseDateRaw` string, nullable: The release date as the publisher writes it, present only when it differs from `releaseDate`, or null when it is not a date at all.
    - `documentNumber` string, nullable: The issuer's own document or case number, for exact lookup: an FCC DA number, an NLRB case-handling docket, a ruling number. On NLRB advice memoranda and FCC/HHS OCR documents this is not recoverable from `sectionNumber`. Omitted from the response when it has no value.
    - `caseName` string, nullable: The charged party or covered entity a document concerns. Only 27% equal to `sectionTitle` on HHS OCR, so it is not recoverable from the served text. Omitted from the response when it has no value.
    - `forum` string, nullable: For `corpusType=AGENCY_ADJUDICATION`, the KIND of proceeding that produced the document, in the publisher's own words. On CFPB enforcement actions this is `Administrative Proceeding` (the Bureau's own Office of Administrative Adjudication, under 12 C.F.R. Part 1081) or `Civil Action` (a suit the Bureau filed in a federal district court). One action can carry both, in which case they are joined with `; `. Null on every other corpus. Omitted from the response when it has no value.
    - `court` string, nullable: The body that heard the matter, where the publisher names one. Distinct from `forum`, which is the KIND of proceeding: `forum` has two values and is what you filter on, `court` has as many values as there are districts and is for display. Populated on every CFPB civil action and on the administrative proceedings the Bureau labels with its own adjudication office. Omitted from the response when it has no value.
    - `relatedDocuments` string[], nullable: The publisher's own labels for the filings whose text this record carries, in the order the publisher lists them. A CFPB enforcement action is ONE legal event published as two to seventeen PDFs and the unit we serve is the ACTION, not the filing: a consent order and the stipulation consenting to it are one record, because splitting them makes every search return two half-answers. This is what tells you which filings are inside the record you are holding. Only the operative instrument is mirrored under `pdfUrl`. Omitted from the response when it has no value.
    - `settlementAmount` string, nullable: The monetary penalty or settlement, as the agency prints it. 95.2% populated on HHS OCR resolution agreements, where it is the single most-asked fact of the corpus. Omitted from the response when it has no value.
    - `requesters` string[], nullable: Who asked for the determination or relief. On export-control commodity-jurisdiction determinations this is the applicant (100% populated); on no-action letters it determines who may rely on the relief. Omitted from the response when it has no value.
    - `program` string, nullable: The benefit or regulatory program a document governs, e.g. Old-Age and Survivors Insurance. 100% populated on Social Security rulings, where it is the primary axis a practitioner filters on. Omitted from the response when it has no value.
    - `languageCode` string, nullable: ISO code of the language the document is written in, present where a corpus is not wholly English. 86% of Puerto Rico insurance bulletins are Spanish (`es`). Omitted from the response when it has no value.
    - `volume` integer, nullable: Volume number for corpora organised in volumes, e.g. the USCIS Policy Manual, whose Volume is the top hierarchy level and had no served representation at all. Omitted from the response when it has no value.
    - `articleNumber` string, nullable: Article number. Article is the PRIMARY hierarchy level in state constitutions, where `chapter` and `part` are 0-6% populated, so without this those corpora served almost no structure. Omitted from the response when it has no value.
    - `articleName` string, nullable: Article title, the companion to `articleNumber`. Omitted from the response when it has no value.
    - `ruleSetCode` string, nullable: Stable machine key for the rule family, where `ruleSet` gives only the prose name. 100% populated on the court-rules states that have a rule set. Omitted from the response when it has no value.
    - `edition` string, nullable: The publisher's edition or year for this text. Omitted from the response when it has no value.
    - `relatedCitations` string[], nullable: Citations OUT of this document that are neither USC nor CFR: the state statutes a regulation implements, the Internal Revenue Code sections a ruling construes, other guidance it points at. `crossReferencesUsc` and `crossReferencesCfr` are 0% on several of these corpora, so this is the only outbound citation set they have. Omitted from the response when it has no value.
    - `supersessionActions` object, nullable: What this document does to EARLIER documents, keyed by the issuer's own verb: `modifies`, `obsoletes`, `amplifies`, `clarifies`, `rescinds`, each mapping to the documents affected. `supersedes` and `supersededBy` cover only the strongest verb. Without these a caller cannot tell a modified revenue procedure from an untouched one, nor see which memorandum rescinded which. Omitted from the response when it has no value.
    - `subtitle` string, nullable: Subtitle, where a jurisdiction puts a level between title and chapter. Maryland's regulations are organised Title > Subtitle > Chapter and are 100% populated; no other served field expressed that level. Deliberately not the same as `subchapter`, which sits below chapter. Omitted from the response when it has no value.
    - `subtitleName` string, nullable: Subtitle title, the companion to `subtitle`. Omitted from the response when it has no value.
    - `publisherKey` string, nullable: The publisher's own stable identifier for this document, where it issues one. On the US Code this is the OLRC's `usckey` (100% populated), which joins directly to the uscode.house.gov bulk XML; on Colorado regulations it is the state's rule id. Use it to reconcile our records against the publisher's without matching on citation strings. Omitted from the response when it has no value.
    - `versionId` string, nullable: The publisher's identifier for THIS VERSION of the document, where it versions them separately from the document itself. 100% populated on Colorado regulations, where it is the only version pointer that exists. Omitted from the response when it has no value.
    - `referencedShortTitles` string[], nullable: Popular names of acts this section REFERENCES, ~10% of the US Code. Distinct from `popularName`, which is the section's own. Omitted from the response when it has no value.
    - `subjectNumber` string, nullable: The publisher's numbered subject index entry, the companion to the term in `topics`. 100% populated on Social Security rulings. Omitted from the response when it has no value.
    - `audience` string, nullable: Who the document is addressed to or binds, where the issuer states it. 100% populated on the Montana insurance bulletins. Omitted from the response when it has no value.
    - `sourceCharStart` integer, nullable: Character offset where this text begins in the source document, for callers reconciling our extraction against the original PDF. Pairs with `sourcePageStart`. Omitted from the response when it has no value.
    - `sourceCharEnd` integer, nullable: Character offset where this text ends in the source document. Omitted from the response when it has no value.
    - `matchSegment` 'rule_text' | 'source_credit' | 'note', nullable, required: On a search hit in a federal rule, which part of the rule document the matched passage sits in: `rule_text`, `source_credit`, or `note` (an Advisory Committee Note). Null when unknown, and always null outside federal rules and on a section fetched by id. A label only, it never changes the ranking.
    - `matchNoteYear` integer, nullable, required: When `matchSegment` is `note`, the year named by the note heading the passage sits under (1993 for 'Notes of Advisory Committee on Rules, 1993 Amendment'). Null when the heading names no year or `matchSegment` is not `note`.
    - `alternateCitations` string[], nullable: Other official citation forms for THIS document, where a publisher prints more than one. Puerto Rico gives an L.P.R.A. cite, Arizona a long form, the IRS an Internal Revenue Bulletin cite, the Federal Reserve a paired Consumer Affairs number. Distinct from `relatedCitations`, which is what this document points AT. Use these when you need to match a citation a user typed in the form their jurisdiction actually publishes. Omitted from the response when it has no value.
    - `expirationDate` string, nullable: When this rule lapses unless re-adopted, as `YYYY-MM-DD`. Distinct from `reviewDate` (the review deadline) and from any amendment date: it is in the future and it ENDS the rule. See `expirationDateRaw` for the publisher's wording. Omitted from the response when it has no value.
    - `expirationDateRaw` string, nullable: The expiry date as the publisher writes it, present only when it differs from `expirationDate`. State regulators print this as `1/1/2028` and `03-01-2029` as well as ISO.
    - `committeeNote` string, nullable: Advisory-committee note on a procedural rule: the standard interpretive gloss courts read alongside the rule text. Deliberately separate from `amendmentNote`, which records when the rule changed rather than what it means. Omitted from the response when it has no value.
    - `sourcePageStart` integer, nullable: First page in the official PDF this text was extracted from, for a pinpoint print citation. 100% populated on the Federal Rules. Omitted from the response when it has no value.
    - `sourcePageEnd` integer, nullable: Last page in the official PDF; companion to `sourcePageStart`. Omitted from the response when it has no value.
    - `displayLabel` string, nullable: The publisher's own short label for this section, e.g. `Cal. BPC § 655.2` or `MPEP § 2165.03`. Populated on essentially every document we hold. Usually equal to `citationShort`, but not always: on the Federal Communications Commission, NLRB, HHS OCR and BIS corpora the two differ on every document, and there `displayLabel` is the form the publisher itself prints. Omitted from the response when it has no value.
    - `publicationDate` string, nullable: The date this document was published by its source. For Federal Register documents this is the FR publication date, the primary citation and sort key, populated on 100% of rules and proposed rules. Distinct from `effectiveDate` (when it takes legal effect) and from `issueDate` (when the issuing body dated it). A rule is routinely published before it is effective. Omitted from the response when it has no value.
    - `publicationDateRaw` string, nullable: The publication date as the publisher writes it, present only when it differs from `publicationDate`, or null when it is not a date at all.
    - `publicLawCites` object[], nullable: Structured Statutes at Large citations parsed out of the source credit, populated on ~72% of the US Code. Each entry carries `statVolume`, `statPage`, `type` and a `display` string. `publicLaws` gives the bare `Pub. L.` list and `sourceCredit` the raw prose; this is the same information already parsed, so a caller can link to the Statutes at Large without re-parsing the credit line. Omitted from the response when it has no value.
    - `topLevelTitle` string, nullable: The outermost division this document sits under, where the corpus has one that `titleNumber`/`chapter`/`part` do not already express. Examples: `Title 9: Criminal` for the DOJ Justice Manual, `Volume 1 - General Policies and Procedures` for the USCIS Policy Manual. Null for flat corpora, where one document is the whole unit. Omitted from the response when it has no value.
    - `externalUrl` string, nullable, required: The publisher's own page for this section, exactly as recorded at ingest: uscode.house.gov, ecfr.gov, a state legislature or a state register. Null when the publisher issues no per-section link, or when the link is withheld. Prefer `sourceUrl`, which is this link when present and otherwise the best official alternative. Some official publishers serve their code only through a JavaScript application, so the link renders in a browser but returns an empty page shell to a plain HTTP client. Texas is the main case: the Secretary of State publishes the Texas Administrative Code only on its Appian portal (texas-sos.appianportalsgov.com). The link is still the correct citation. To check a section without a browser, use `adoptingCitations` (for Texas, the `NN TexReg PPPP` register citations that adopted and amended it) and read the text we captured at `textUrl`.
    - `sourceUrl` string, nullable, required: Where the government published this text: the link to cite and to verify against. The same value `/us/statutes/section/{actId}/body` returns as `sourceUrl`, on every search result, section record and batch item. It is `externalUrl` when the publisher issued a per-section link, and otherwise falls back to the govinfo.gov page, then the state's own page, then our archived copy of the publisher's page. Null when we hold no publishable link: only official government links are served here.
    - `sourceUrlNote` string, nullable, required: Says why `sourceUrl` is null. Either we serve no link for this section on purpose and it is cited by `citation` alone, or the publisher issues it only inside a larger file (an archive, spreadsheet or whole volume) that is not a page of the section, or no source link is recorded for it at all. Null when `sourceUrl` is set.
  - `previous` StatuteResult[]: Sections immediately BEFORE this one in the same container, nearest last.
    - `actId` string, required: Unique section identifier (e.g., 'USC_T42_C21_S1983', 'CFR_T17_P240_S240_10b5_1').
    - `citation` string, nullable, required: Full citation (e.g., '42 U.S.C. § 1983 (2024)', '17 C.F.R. § 240.10b5-1 (2026)'). Always present; null when not known.
    - `citationShort` string, nullable, required: Short citation (e.g., '42 U.S.C. § 1983', '17 C.F.R. § 240.10b5-1'). Always present; null when not known.
    - `title` string, nullable, required: Section title. Always present; null when not known.
    - `corpusType` string, nullable, required: The corpus this section belongs to: one of `USC`, `CFR`, `STATE`, `CONSTITUTION`, `FEDERAL_RULES`, `FEDERAL_LOCAL_RULES`, `STATE_CONSTITUTION`, `STATE_RULES`, `EXECUTIVE_ACTION`, `REGULATION`, `FEDERAL_REGISTER`, `FEDERAL_REGISTER_NOTICE`, `AGENCY_GUIDANCE`, `SENTENCING_GUIDELINES`, `US_TAX_TREATY`, `US_TREATY`, `STATE_AGENCY_GUIDANCE`, `STATE_AG_OPINION`, `STATE_REGISTER`, `SESSION_LAW`, `STATUTE_COMPILATION`, `AGENCY_ADJUDICATION`, `CFR_ANNUAL`, `USC_ANNUAL`, `FEDERAL_BILL`, `FEDERAL_RULES_ANNUAL`, `FEDERAL_RULES_PROPOSED`. The same tokens the `corpusType` filter accepts. Always present; null when not known.
    - `state` string, nullable, required: 2-letter lowercase state code (e.g. `ca`, `tx`) when the row belongs to a state corpus. `federal` for federal rows. Always present; null when not known.
    - `source` string, nullable, required: The named source within `corpusType` this row belongs to, for corpora that fold several bodies of law into one token. Pass it back as the `source` search filter to scope to just this source; the accepted values, with their names, are listed on that filter. Null for corpora with only one source, which includes every state's statutes and regulations. Not a link, and not where the text came from: it is a filter token. The official link to the publisher's text is `sourceUrl`.
    - `year` integer, nullable, required: The year this row was ingested, not the year of the law. Most ingesters stamp the capture year (`time.gmtime().tm_year`) and a few pin a literal, so the bulk of the corpus reads the year it was captured. Do not filter or reason about currency with it. `lastAmendedYear` carries the amendment year, `currentThrough` and `currencyNote` carry the publisher's own currency statement, and `goodLawStatus` carries the status. Always present; null when not known.
    - `relevanceScore` number, nullable, required: Relevance score, normalized to roughly 0-1. Higher means a better match for ranking within one response. It is a relative ranking signal, not a calibrated confidence or probability, so do not compare scores across different queries or treat a fixed value as a quality threshold. Exception: a query that resolves to an exact citation (e.g. '42 U.S.C. § 1983', 'Cal. Civ. Code § 1950.5', 'Fed. R. Civ. P. 12') always scores that section 1.0, since it is a certain match rather than a ranked one -- a natural-language or keyword query never returns 1.0 by comparison. null on any endpoint that did not rank: fetching a section by id, a batch fetch, or a section embedded in an intelligence response. When the response carries `rankingDegraded: true`, the relevance model was unavailable and this is a retrieval score on a different, much smaller scale: still a valid ORDER, not a 0-1 relevance.
    - `excerpt` string, required: Text excerpt (up to 500 characters).
    - `body` string, nullable, required: Full plain text of the section. Always a key on the row: filled only when the request set `includeBody: true`, and null otherwise and on any row whose text could not be resolved (those rows are not charged for a body). A section the publisher prints as images has no text: its `body` is null and `bodyUnavailable` is `true`. This is the actual statutory text, not the `excerpt`. The two are different things and the difference matters for quoting: `excerpt` is a ranking preview windowed around the match, so it can begin mid-section and drop a leading subsection marker -- measured 2026-09-02, four of five California rows lost their opening `(a) `. `body` is the document as the publisher printed it.
    - `bodyUnavailable` boolean, nullable: Present, and `true`, only on a section that has no text to return: the publisher prints it as images (an appendix, a form, a map), or the text we hold is only a partial copy of the official text. Omitted on every other section. The section is real and its metadata is complete; there is simply no body, so `body` / `plain` / `html` are null, `available` is false on `/body`, and nothing is charged for a body. Read it instead of treating a null body as a fetch failure that is worth retrying.
    - `bodyUnavailableReason` 'image_only_source' | 'misfiled_source_text' | 'partial_snapshot_text', nullable: Why there is no body, present with `bodyUnavailable`. `image_only_source`: the publisher prints this section as images, so there is no text to extract. Where we hold an official link for the section it is in `sourceUrl`; it is null where we may not republish the publisher's link. `misfiled_source_text`: the text stored under this regulation opens with another rule's number (a prior version filed under a renumbered rule), so it is withheld rather than served as this rule. `partial_snapshot_text`: the text we hold for this section is only a partial copy of the official text, so it is withheld rather than served as if it were complete. Omitted from the response when it has no value.
    - `bodyNote` 'fetch_failed' | 'no_text' | 'insufficient_credits' | 'response_size_cap', nullable: Present only when the request set `includeBody: true` and this row's `body` is null for a reason on our side or yours, so a null body is never silent. `fetch_failed`: reading the text failed this time, retry; not charged. `no_text`: the read succeeded but returned no text for this section; not charged. `insufficient_credits`: your balance could not cover the bodies, so every body on the page was withheld (the ranking you paid for is intact); top up and repeat the call. `response_size_cap`: a batch response carries at most 4,000,000 characters of inline body text, and this row's body was dropped to stay under it; not charged, fetch it from `/section/{actId}/body`. A section printed as images carries `bodyUnavailable` instead.
    - `bodyServedNote` string, nullable: Present only when the request set `includeBody: true` and the `body` on this row is not the section's preferred copy: a lesser copy was served because the preferred one could not be read this time, a rendered table or figure was withheld, or the text is partial. The same words `/section/{actId}/body` returns in `note`. Not cached, so a repeat call may return the preferred copy.
    - `matchContexts` BooleanMatchContext[], nullable: Present only with `matchType: "boolean"`: up to 3 passages showing where this section satisfied the expression, in the order they appear in the section. Highlights follow the engine that decides membership: every conjunct of an AND, the OR branches that matched, the words of a phrase, both operands of a satisfied `/N`, `/s` or `/p` pair, the occurrences counted by `atleastN`, and for `a NOT W/N b` the `a` that has no `b` in range. A NOT never highlights anything. Unlike `excerpt` (the passage the relevance model ranked, which may not contain your terms), these passages always do. Empty (`[]`) when the expression matched only in the heading or citation (`title( )`, `cite( )`). Absent on a row whose passages could not be prepared within the search's time allowance; the row is still a verified match. Contexts never change which sections are returned, their order, or the price.
      - `text` string, required: About 240 characters of the section's text as published, cut on word boundaries, with each run of whitespace (line breaks included) shown as one space and soft hyphens removed (a word hyphenated across a line break is joined). It can begin and end mid-sentence.
      - `highlights` array[], required: The words that satisfied the expression, as `[start, end]` character offsets into `text` (start inclusive, end exclusive, counted in Unicode code points, so `text.slice(start, end)` in JavaScript holds only for text without astral characters; Python's `text[start:end]` always does). Sorted, never overlapping. Offsets point at the text as printed, which matching normalizes: a highlight for `section` can cover `§`, one for `café` can cover `CAFÉ` or a decomposed accent, and one for a phrase covers the whole phrase. Plain offsets, not markup, so you choose how to style them.
        - integer[]
    - `titleNumber` string, nullable, required: USC/CFR/state title number (e.g. '26', '13A'). Always present; null when not known.
    - `titleName` string, nullable, required: Title name (e.g., 'The Public Health and Welfare'). Always present; null when not known.
    - `chapter` string, nullable, required: Chapter number or identifier. Always present; null when not known.
    - `chapterName` string, nullable, required: Chapter name. Always present; null when not known.
    - `sectionNumber` string, nullable, required: Section number (e.g., '1983', '240.10b5-1'). Always present; null when not known.
    - `sectionTitle` string, nullable, required: The section's own heading (e.g., 'Rule G. Forfeiture Actions In Rem'). Distinct from `title`, which is the hierarchical display path. Always present; null when not known.
    - `displayPath` string, nullable, required: Full hierarchical path (Title > Chapter > Section). Always present; null when not known.
    - `breadcrumb` object[], nullable, required: Structured breadcrumb trail for navigation. Always present; null when not known.
    - `parent` object, nullable, required: Query for `GET /us/statutes/divisions` that lists this section's siblings (its containing chapter, part, code, article or federal rule set). Pass it straight back to walk up the hierarchy, or spread it into a `POST /us/statutes/search` body to search within that container: every key it carries is also a search filter. Null when the container cannot be determined.
    - `subchapter` string, nullable, required: Subchapter number or identifier. Always present; null when not known.
    - `subchapterName` string, nullable, required: Subchapter name. Always present; null when not known.
    - `part` string, nullable, required: Part number or identifier (CFR/state). Always present; null when not known.
    - `partName` string, nullable, required: Part name. Always present; null when not known.
    - `subpart` string, nullable, required: Subpart number or identifier (CFR). Always present; null when not known.
    - `subpartName` string, nullable, required: Subpart name. Always present; null when not known.
    - `popularName` string, nullable, required: Popular/common name of the act (e.g. 'Truth in Lending Act'), when known. Always present; null when not known.
    - `actStatus` string, nullable, required: Raw section status: `in_force`, `repealed`, `renumbered`, `transferred`, `omitted`, `reserved`, `vacant`, or `unconstitutional`. Some corpora also use `superseded` (a prior version), `enacted`, `pending` and `non_precedential`. This is the status recorded for the section; the currency verdict is `goodLawStatus`. Always present; null when not known.
    - `goodLawStatus` string, nullable, required: Derived currency verdict: `good_law`, `not_good_law`, `not_operative`, or `unknown`. `unknown` means no currency verdict is asserted for the section, which is different from out of date. It is returned where a jurisdiction does not publish repeal information (state statutes for California, for example, are stored `in_force` with `goodLawStatus: unknown`: the stored status is the publisher's own, and we do not certify it current because that state's repeal markers have not been verified), and for these corpora by design: attorney general opinions, register notices, statute compilations, the U.S. Code, executive actions and treaties. Annual editions (`cfr_annual`, `usc_annual`) return `not_good_law` because a later edition supersedes them. Read `corpusType` beside this field. `null` when currency checking is disabled.
    - `goodLawBasis` string, nullable, required: Why `goodLawStatus` has the value it has, as a short code; `null` exactly when `goodLawStatus` is `null`. `good_law`: `in_force` (recorded in force, in a jurisdiction whose repeal information we track). `not_good_law`: `repealed_or_moved` (repealed, renumbered, transferred or recodified), `past_edition` (an annual edition later editions supersede), `proposal` (a bill or proposed rule, never law at any stage), `superseded_by_later_guidance` (IRS guidance a later document superseded, obsoleted or revoked in full), `later_rule_removed` (a Federal Register final rule a later final rule removed from the CFR) or `later_order_revoked` (an executive order a later one revokes or supersedes in full). For the last three `supersededBy` names the later document, and for the last `actStatus` reads `revoked` or `superseded`. `not_operative`: `reserved_or_inactive` (reserved, vacant or unfunded), `not_yet_effective` (a future effective date is printed in the heading, or a final rule's `frEffectiveOn` is ahead) or `publisher_marker` (the publisher's own bracketed note in the heading). `unknown`: `no_repeal_signal` (the publisher gives no repeal markers to check its stored status against), `frozen_snapshot` (served from an edition frozen at a past date), `stated_as_of_date` (current only to the date the text states), `no_status`, `text_omitted_by_publisher` (the legislature prints only a placeholder such as 'Amendatory provisions; text omitted'; `currencyNote` says so) or `status_unrecognized`.
    - `currencyNote` string, nullable, required: Source's 'current through ...' note, when published. Always present; null when not known.
    - `renumberedTo` string, nullable: Where the publisher says this section went, when `actStatus` is `renumbered`. RAW SOURCE FORM, not an `actId` and not a citation: `self:4651` means section 4651 of this same title, `34:10105` means section 10105 of Title 34. Do not pass it to a section endpoint. Read `renumberedToLabel` instead, or resolve the citation it names through `/us/statutes/resolve`. Omitted from the response when it has no value.
    - `renumberedToLabel` string, nullable: `renumberedTo` written out, e.g. `section 10105 of Title 34`. Present whenever `renumberedTo` is. Omitted from the response when it has no value.
    - `transferredTo` string, nullable: Where the publisher says this section went, when `actStatus` is `transferred`. Same raw source form as `renumberedTo`, and the same warning: it is not an `actId`. Omitted from the response when it has no value.
    - `transferredToLabel` string, nullable: `transferredTo` written out. Present whenever `transferredTo` is. Omitted from the response when it has no value.
    - `issueDate` string, nullable, required: Issue/publication date of this version, as `YYYY-MM-DD`, when known. See `issueDateRaw` for the publisher's wording on the rare source that does not print ISO. Always present; null when not known.
    - `issueDateRaw` string, nullable: The issue date as the publisher writes it, present only when it differs from `issueDate`. Null across the corpus today; it exists so a source that starts printing prose cannot silently put prose in a field documented as a date.
    - `crossReferencesCfr` string[], nullable: CFR cross-references parsed from the text, e.g. `['1.6011-4']`. Omitted from the response when it has no value.
    - `crossReferencesCfrChecked` CfrReferenceCheck[], nullable: Each distinct entry of `crossReferencesCfr`, checked against the sections we hold. Only populated on `GET /us/statutes/section/{actId}` for a CFR section with references; null on search results and when the check could not be made, in which case treat the raw list as unchecked. Omitted from the response when it has no value.
      - `reference` string, required: The reference exactly as stored in `crossReferencesCfr`.
      - `title` integer, nullable: CFR title the reference names or was assumed to name. Null if malformed.
      - `section` string, nullable: Section number with sentence punctuation removed (`80.1426.` is `80.1426`).
      - `status` 'held' | 'not_held' | 'malformed', required: `held`: this exact section is in the corpus (fetch it by `actId`). `not_held`: no section with this exact number is held in that title; it may be a truncated stem, a part we do not hold or an extraction error. We never substitute a nearby section. `malformed`: not shaped like a CFR section number.
      - `actId` string, nullable: The held section's id, when `held`.
      - `titleAssumed` boolean: True when the reference carried no title and the citing section's own title was assumed. Such a reference can point at another title.
    - `crossReferencesUsc` string[], nullable: USC cross-references parsed from the text, e.g. `['42:1983']`. `'self:<section>'` denotes a reference to another section of the same title. Omitted from the response when it has no value.
    - `statutoryAuthority` object[], nullable: For a CFR/eCFR section: the USC (or other) citations in its 'Authority' note that authorize the rule, e.g. `[{'type': 'usc', 'title': 15, 'section': '78o', 'display': '15 U.S.C. 78o'}]`. Null for non-regulation corpora. Omitted from the response when it has no value.
    - `implementingRegulations` object[], nullable: For a USC section: the CFR parts that implement it, derived from the reverse of every CFR section's own `statutoryAuthority`, e.g. `[{'cfrTitle': 17, 'part': '240', 'partName': '...', 'display': '17 CFR Part 240'}]`. Null for non-USC corpora. Omitted from the response when it has no value.
    - `frRegulationIdNumbers` string[], nullable: Regulation Identifier Number(s) (RIN) assigned to this rule. Omitted from the response when it has no value.
    - `frDocketIds` string[], nullable: Rulemaking docket ID(s) this document was filed under. Omitted from the response when it has no value.
    - `frEffectiveOn` string, nullable: The rule's effective date (ISO 8601 date), when set. Omitted from the response when it has no value.
    - `frCommentsCloseOn` string, nullable: Public-comment deadline (ISO 8601 date). Proposed rules only. Omitted from the response when it has no value.
    - `frSignificant` boolean, nullable: Whether the Federal Register marked this rule 'economically significant' (EO 12866). Omitted from the response when it has no value.
    - `frCorrectionOf` string, nullable: Federal Register document number this document corrects, when this is a correction. Omitted from the response when it has no value.
    - `frCorrections` string[], nullable: Federal Register document number(s) that later corrected this document. Omitted from the response when it has no value.
    - `frRegulationsDotGovUrl` string, nullable: Link to this document's public comment docket on regulations.gov. Omitted from the response when it has no value.
    - `frRelatedDocuments` FrRelatedDocument[], nullable: Other Federal Register documents sharing this document's RIN(s) (its proposed rule, its final rule, and any corrections), most recent first. Only populated on `GET /us/statutes/section/{actId}` for a row that carries `frRegulationIdNumbers`; always null on `/us/statutes/search` results, since computing it needs a follow-up lookup that is too expensive to run per search result. Omitted from the response when it has no value.
      - `actId` string, required
      - `citation` string, nullable
      - `title` string, nullable: The related document's own title/heading, when known.
      - `documentType` string, nullable: `proposed_rule`, `final_rule`, or the raw Federal Register category otherwise.
      - `publicationDate` string, nullable: Federal Register publication date (ISO 8601 date), when known.
    - `frRelatedDocumentsNote` string, nullable: Set only when `frRelatedDocuments` is absent for a reason you should know: this document's RIN is shared by more than 25 other Federal Register documents (an umbrella RIN), so it names no single rulemaking and listing any subset would be a guess; or the related-document lookup was temporarily unavailable, so the list may be incomplete and a repeat call returns it. In that case the call is refunded (`creditsConsumed` is 0). Omitted from the response when it has no value.
    - `subject` string, nullable: The publisher's own subject or document-type label, where it prints one (for example a state insurance bulletin's `RE:` line, or its listing category such as `Rescission`). Omitted from the response when it has no value.
    - `rescindedOn` string, nullable: The date the document was rescinded or withdrawn, as `YYYY-MM-DD`, when the source states one. See `rescindedOnRaw`. Omitted from the response when it has no value.
    - `rescindedOnRaw` string, nullable: The rescission date as the publisher writes it, present only when it differs from `rescindedOn`.
    - `sourceCredit` string, nullable: The Office of the Law Revision Counsel's credit line for a USC section: the acts that enacted and amended it, in order, e.g. `June 25, 1948, ch. 646, 62 Stat. 869; Pub. L. 85-508, Sec. 12, July 7, 1958, 72 Stat. 348`. Parentheses stripped, whitespace normalized. USC only, and null on a USC section that prints no credit (a transferred, repealed or reclassified stub). CFR sections carry the same fact as a list in `federalRegisterCitations` instead, which is why the shape differs; no other corpus publishes one. Omitted from the response when it has no value.
    - `amendmentYears` integer[], nullable, required: Distinct years the section was amended, parsed from the publisher's history note. Always newest first, and de-duplicated. Ingesters store the array in both orders (eCFR writes newest first, state regulations and state statutes write oldest first), so the order is imposed at serve time and the served order is the only one to rely on. Years outside 1789..(current year) are dropped rather than served: amendment dates are parsed out of prose and a note can yield a sunset or substitution date that is not an amendment at all. Always present; null when not known.
    - `lastAmendedYear` integer, nullable, required: Most recent amendment year, when known. Re-derived at serve time as `max(amendmentYears)`, so it never exceeds the list served beside it. Falls back to the publisher's own scalar only when `amendmentYears` is empty, and only when that scalar is itself within 1789..(current year). Always present; null when not known.
    - `amendmentsCount` integer, nullable, required: How many amendments the publisher recorded for this section. Not the length of `amendmentYears`, and it is not safe to derive one from the other. For regulations and court rules this counts amending EVENTS: one per register citation, filing or history entry, so a section amended twice in the same year counts 2 against a single entry in `amendmentYears`. The two disagree on a large share of the regulation and court-rule corpora, so read each for what it is. For the other corpora, and for any source that publishes no per-event record, it is the number of distinct years and is capped at the length of `amendmentYears`, so it never counts a year the list dropped as implausible; it understates a section amended twice in one year. Always present; null when not known.
    - `currentThrough` string, nullable, required: How current the publisher says this text is, in the publisher's own terms. A date (`2025-01-06`) on every USC section and most compilations; otherwise the publisher's wording (`Current through Act 9046 of the 2025 session`, `Public Law 119-60`, `Supp. 19-2`, `2024 Edition`). Do not parse it as a date without checking its shape. `currencyNote` carries the same fact as prose where a publisher writes it that way. Always present; null when not known.
    - `pendingAdoptions` object[], nullable: New York only. State Register adoption notices that post-date the print volume this section's text was taken from. They are notices, not an updated consolidated text: `text` and `body` still reflect `currentThrough` / `currencyNote`. Look the notice up in the State Register by its `idNo`. Each entry: `idNo` (e.g. `DFS-23-26-00013-A`), `scope` (`section` when the notice names this section, `part` when it names the Part containing it), `effectiveDate` (ISO date, null if the notice states none), `agency`, `issueDate` (ISO date of the Register issue). No link is returned; it is withheld under licence, as with `sourceUrl` on these regulations. Only adoptions (`-A`, `-AA`) are listed, never proposals, emergency rules or withdrawals. Null on every section with no such notice, which does not mean the section is current: we cover Register adoptions for NYCRR Titles 3, 19 and 23 only. Omitted from the response when it has no value.
    - `adoptedAfterCurrentThrough` boolean, nullable: New York only. True when `pendingAdoptions` is non-empty, i.e. the State Register records at least one adoption naming this section or its Part that post-dates the volume `currentThrough` refers to, so the text served may be out of date. Null (never false) when no such adoption is recorded; null is not a claim that the text is current. Omitted from the response when it has no value.
    - `amendmentHistory` string[], nullable: Structured amendment entries where the publisher records them separately from the credit line in `history`. Omitted from the response when it has no value.
    - `amendmentHistoryNote` string, nullable: Present only when the section carries no amendment evidence and its state or document type does not record enough amendment history to read absence as a fact (for example New York, Massachusetts, Arizona and West Virginia statutes, several states' regulations, court rules and constitutions, opinions, register notices, bulletins, annual CFR editions and session laws). It says `amendmentYears`, `lastAmendedYear` and `amendmentsCount` are absent because nothing was recorded, not because the section is unamended; `amendmentsCount` is then null rather than 0. Also present on a Maryland section whose `history` is generated from General Assembly session data rather than a publisher credit line. Null where history is recorded, and an empty history there does mean the section has not been amended.
    - `fieldAbsenceNote` string, nullable: Present only when `year` or `effectiveDate` is null AND the ingester of this whole document type never records it (state constitutions carry no `year`; federal local court rules rarely carry a `year` or `effectiveDate`, as of 2026-10-31). It says the field is null because nothing was recorded, which is not a claim that the document has no such date. Null otherwise.
    - `citationNote` string, nullable: Present only on a state-constitution unit the source gives no section number (an amendment, preamble, schedule or whole article). `citation` is then the article-level form without a section sign, and `sectionNumber` is null. Absent otherwise.
    - `responseBounds` ResponseBounds: Whether the default response is the whole record, and if not, what is missing.
      - `truncated` boolean, required: True when at least one field below was shortened. False means this response carries the whole record. Nothing is dropped silently: every shortened field is listed in `fields`.
      - `fields` BoundedField[]: Every field shortened in this response. Empty when `truncated` is false.
        - `field` string, required: The response field that was shortened, by its response name.
        - `unit` 'items' | 'characters', required: `items` for a list, `characters` for the verbatim `history` credit line.
        - `total` integer, required: How many items (or characters) the record holds.
        - `returned` integer, required: How many items (or characters) this response carries.
        - `nextOffset` integer, required: Zero-based position of the first omitted item (or character) in the full value. What follows it is the omitted part: request `full=true` to receive it.
      - `note` string, nullable: Plain-language statement of what was cut and how to get all of it. Present only when `truncated` is true.
    - `sourceNote` string, nullable: The publisher's source note for the section, verbatim. Omitted from the response when it has no value.
    - `effectiveDate` string, nullable, required: When THIS version took effect, as `YYYY-MM-DD`, or null when the publisher's own string does not name one unambiguous day we can read without guessing. On a section with `actStatus=superseded` this is the start of that version's window. The publisher's wording is preserved in `effectiveDateRaw` whenever it differs.
    - `effectiveDateRaw` string, nullable: The date exactly as the publisher writes it, present only when it differs from `effectiveDate`. A section whose publisher already prints ISO leaves this null. Expect prose (`September 8, 1916`), abbreviated months (`Feb. 25, 1868`), US numerics (`9/28/15`), Spanish for Puerto Rico (`26 de junio de 1963`), and values that are not a single date at all (`April 1, 2023 to June 30, 2026`), which is why they cannot be published under `effectiveDate`.
    - `historyEffectiveDate` string, nullable, required: When this version took effect, as `YYYY-MM-DD`, read out of the publisher's amendment credit line in `history`, which is returned beside it as the evidence. A weaker fact than `effectiveDate` (a date the publisher put in a date field), so it is populated only where `effectiveDate` is null. It is the newest commencement the credit line names, and null whenever that cannot be stated without guessing: a credit line that dates only some entries, a date that belongs to a repeal, sunset, applicability rule or another section, a commencement still in the future, a date older than `lastAmendedYear`, or a state whose `history` format we have not measured. Statutes only.
    - `priorEffectiveDates` string[], nullable: Earlier effective dates recorded for the section, each as `YYYY-MM-DD`, in the order the publisher lists them. A publisher's list written as one string (`3-15-22; 7-1-26`) is split into its dates. A value that names no single day (`March 2007`, `immediately`) is not here: it is in `priorEffectiveDatesRaw`. Omitted from the response when it has no value.
    - `priorEffectiveDatesRaw` string[], nullable: The publisher's own wording of `priorEffectiveDates`, one string per stored entry, present only when it differs from the ISO list or holds an entry that names no single day. Nothing the publisher recorded is dropped.
    - `history` string, nullable, required: The publisher's own amendment/history credit line, verbatim, e.g. `Effective 5/4/2005; Superseded 8/1/2016`. `amendmentYears` is parsed from this; keep both when you need the exact wording. Always present; null when not known.
    - `supersededBy` string, nullable: `actId` of the section that replaced this one. Present on a superseded version so you can fetch the current text in one hop via `GET /statutes/section/{actId}`. Omitted from the response when it has no value.
    - `supersedes` string, nullable: `actId` of the earlier version this section replaced, when known. Omitted from the response when it has no value.
    - `pendingAmendments` PendingAmendment[], nullable: Federal Rules only: the amendments proposed to this rule that are not yet in force, each with its lifecycle `status`, `cycle`, `effectiveDate`, `commentPeriodEnd`, `sourceUrl` and `textComplete`. Fetch one with `GET /us/statutes/section/{id}`. Absent on every other section and on a rule with nothing pending. A proposal is never law until its effective date: the text above is the rule in force.
      - `id` string, required: `actId` of the proposed amendment. Fetch it with `GET /us/statutes/section/{id}` or `/body`; it is never returned by an unscoped search.
      - `status` string, nullable: Where the proposal is in the Rules Enabling Act process: `published_for_comment`, `approved_by_standing_committee`, `approved_by_judicial_conference`, `transmitted_to_supreme_court`, `adopted_by_supreme_court` or `transmitted_to_congress`. A proposal that is in force or withdrawn is not listed here.
      - `cycle` integer, nullable: The rules cycle (the year the amendment is meant to take effect).
      - `effectiveDate` string, nullable: The date the amendment takes effect if it is adopted unchanged (ISO 8601 date).
      - `commentPeriodEnd` string, nullable: Last day of the public comment period (ISO 8601 date), when one applies.
      - `sourceUrl` string, nullable: The official page the proposal was taken from, when we hold a link we may publish.
      - `textComplete` boolean, nullable: `true` when the proposed text we hold is the whole amended rule; `false` when it is partial (for example only the changed paragraphs).
      - `commentDocketIds` string[]: Rulemaking docket ids that hold the public comments on this proposal. Each resolves on `GET /us/rulemaking/dockets/{docketId}`. Empty when none is known.
    - `ruleSet` string, nullable: For court rules, the rule family this belongs to, e.g. `North Dakota Rules of Civil Procedure`. Rule numbers repeat across families (a Civil Rule 12 and a Criminal Rule 12 both exist), so this is what disambiguates them. Omitted from the response when it has no value.
    - `publicLaws` string[], nullable: Public Laws referenced by the section, e.g. `['Pub. L. 96-170']`. Omitted from the response when it has no value.
    - `federalRegisterCitations` string[], nullable: Federal Register citations associated with the section, e.g. `['48 FR 3956', '49 FR 15073']`. This is the CFR's form of the credit line `sourceCredit` carries for the USC: the rulemakings that established and amended the section. Populated on 37.4% of CFR sections, empty where eCFR prints no source note. Omitted from the response when it has no value.
    - `granuleId` string, nullable: govinfo granule identifier (USC/CFR provenance). Omitted from the response when it has no value.
    - `packageId` string, nullable: govinfo package identifier (USC/CFR provenance). Omitted from the response when it has no value.
    - `htmlUrl` string, nullable, required: HTML version of the statute section. Always present; null when not known.
    - `pdfUrl` string, nullable, required: PDF version of the statute section. Always present; null when not known.
    - `xmlUrl` string, nullable, required: XML version of the statute section. Always present; null when not known.
    - `textUrl` string, nullable, required: Plain-text version of the section, from the open-data copy we hold in our own storage. Populated for many state corpora (MS, NJ, NY, NV, etc.) and for United States Code sections. The URL is public by design: the text is open data, so it opens without an API key and carries no credit charge. Null when we hold no plain-text copy. It is never a commercial platform's link.
    - `docxUrl` string, nullable: Microsoft Word (DOCX) version, when available. Omitted from the response when it has no value.
    - `stateHtmlUrl` string, nullable, required: HTML rendering of the document. For most state corpora this is the publisher's own page; for corpora we mirror (state agency guidance, regulations, court rules) it is our archived copy of the artifact the publisher served, on statutes-us.vaquill.ai. Use `externalUrl` for the publisher's canonical address. Never a PDF: a mirrored PDF is served as `pdfUrl` instead. Populated for state corpora only. Always present; null when not known.
    - `govInfoHtmlUrl` string, nullable: Official govinfo.gov HTML version. Omitted from the response when it has no value.
    - `govInfoPdfUrl` string, nullable: Official govinfo.gov PDF version. Omitted from the response when it has no value.
    - `abstract` string, nullable: The issuing agency's own summary of the document, as published in the Federal Register. Populated on 99.9% of rules and proposed rules, so a document can be triaged without fetching the full text. Omitted from the response when it has no value.
    - `agencies` string[], nullable: Issuing agencies, by name. Populated on 99.9% of Federal Register documents. Pair with `agencySlugs` when you need the token the `agency` search filter takes. Omitted from the response when it has no value.
    - `agencySlugs` string[], nullable: The issuing agencies as slugs. These are exactly the values the `agency` filter on `/us/statutes/search` accepts, so an agency facet can be round-tripped straight back into a query. Omitted from the response when it has no value.
    - `topics` string[], nullable: The Federal Register's own CFR-index subject terms. Populated on ~71% of rules and ~68% of proposed rules, with one hard boundary: documents published before 2000 carry none, because the Federal Register did not index them this way. Omitted from the response when it has no value.
    - `documentTypeLabel` string, nullable: The instrument type as the publisher names it: `Rule`, `Proposed Rule`, `Presidential Document`, `Declaratory Ruling`, `Resolution Agreement`. Deliberately not `corpusType`, which says which body of law a document belongs to: two documents in one corpus can be very different instruments. Omitted from the response when it has no value.
    - `documentSubtype` string, nullable: Finer instrument class where the publisher gives one. On presidential documents this separates an executive order from a proclamation, a memorandum or a notice (~90% populated there). Omitted from the response when it has no value.
    - `action` string, nullable: The Federal Register's own ACTION line, ~100% populated. Carries distinctions no other field makes: interim final rule, direct final rule, withdrawal, reopening of the comment period. Omitted from the response when it has no value.
    - `president` string, nullable: The president in office for this document, on Federal Register and presidential-document corpora spanning 1994 to present. Omitted from the response when it has no value.
    - `signingDate` string, nullable: When a presidential document was signed, as `YYYY-MM-DD`, which is routinely earlier than `publicationDate` and is the legally operative date. See `signingDateRaw`. Omitted from the response when it has no value.
    - `signingDateRaw` string, nullable: The signing date as the publisher writes it, present only when it differs from `signingDate`.
    - `executiveOrderNumber` string, nullable: The executive order number a lawyer cites the order by (`14179` for Executive Order 14179 of January 23, 2025). Set only on executive orders; the `citation` is the Federal Register page, not this. See `instrumentNumberSource` for where the value came from. Omitted from the response when it has no value.
    - `proclamationNumber` string, nullable: The proclamation number (`10886` for Proclamation 10886). Set only on proclamations. Memoranda, determinations and notices are not numbered in either series and carry null in both fields, never an invented number. Omitted from the response when it has no value.
    - `instrumentNumberSource` string, nullable: Provenance of `executiveOrderNumber` / `proclamationNumber`. `stored` is the number recorded when the document was ingested. `derived_from_text` is read at request time from the document's own header line (`Executive Order 14179 of January 23, 2025`), accepted only when that line opens the document and its date equals `signingDate`; it is null when the header is not in the text returned (for example a later chunk of a search hit), which means unknown, not unnumbered. Omitted from the response when it has no value.
    - `datesText` string, nullable: The verbatim DATES block from the Federal Register, ~98% populated. Worth reading alongside `frEffectiveOn`: a rule with staged or conditional effective dates has them here, and the single date flattens that away. Omitted from the response when it has no value.
    - `frVolume` integer, nullable: Federal Register volume, the `66` in `66 FR 64768`. Omitted from the response when it has no value.
    - `frStartPage` integer, nullable: First Federal Register page, the `64768` in `66 FR 64768`. Omitted from the response when it has no value.
    - `frEndPage` integer, nullable: Last Federal Register page. With `frStartPage` this gives the page RANGE, which `citation` cannot express because it carries only the first page. Omitted from the response when it has no value.
    - `wordCount` integer, nullable: Words in the full document, so a caller can size a fetch before paying for the body. Omitted from the response when it has no value.
    - `issuingAgency` string, nullable: The body that promulgated or issued this document: the state agency behind a regulation, the division behind an agency letter. Populated at 83.6-100% across the state-regulation corpora that carry it. Omitted from the response when it has no value.
    - `adoptingCitations` string[], nullable: Citations to the instrument that ADOPTED this rule: the state register notice, the Washington filing number, the adopting order. The rulemaking audit trail. Unified across four different payload spellings, so this is comparable across states in a way the underlying data is not. These are also the independent way to confirm a section when the publisher's own page cannot be read without a browser (see `externalUrl`): a Texas rule's `['50 TexReg 8285']` names the Texas Register issue and page that printed its adoption. Omitted from the response when it has no value.
    - `lawImplemented` string, nullable: The statute this rule IMPLEMENTS, as distinct from `statutoryAuthority`, which is the statute granting the rulemaking power. Florida populates both and they differ. Omitted from the response when it has no value.
    - `lastAmendedDate` string, nullable: Full date of the most recent amendment, as `YYYY-MM-DD`, where the publisher gives one. See `lastAmendedDateRaw` for the wording. Illinois and Colorado regulations carry their amendment provenance only here and in `amendmentNote`: neither state has a `history`, and Colorado has no `effectiveDate` either, so for Colorado this is the only date that exists. Omitted from the response when it has no value.
    - `lastAmendedDateRaw` string, nullable: The last-amended date as the publisher writes it, present only when it differs from `lastAmendedDate`, or null when it is not a date at all.
    - `amendmentNote` string, nullable: The publisher's amendment credit line where it is stored separately from `history`. Illinois and Colorado regulations, ~72% populated. Omitted from the response when it has no value.
    - `currencyYear` integer, nullable: Machine-readable counterpart to `currencyNote`, which is prose. 100% populated on the nine state-regulation corpora that carry a currency statement. Omitted from the response when it has no value.
    - `reviewDate` string, nullable: The date a rule must be re-adopted or it expires, where the state runs a sunset review. Ohio regulations, ~80% populated. Not an amendment date: it is in the future. Omitted from the response when it has no value.
    - `reviewDateRaw` string, nullable: The review date as the publisher writes it, present only when it differs from `reviewDate`, or null when it is not a date at all.
    - `originalEnactmentDate` string, nullable: When the section was FIRST enacted, as `YYYY-MM-DD`, ~72% populated on the US Code. Deliberately separate from `effectiveDate`: merging them would report an amended section as effective from its original year. On 35.7% of US Code points this is the only enactment date we hold. See `originalEnactmentDateRaw` for the publisher's wording. Omitted from the response when it has no value.
    - `originalEnactmentDateRaw` string, nullable: The enactment date as the publisher writes it, present only when it differs from `originalEnactmentDate`. The US Code prints `Aug. 14, 1935` where GovInfo statute compilations print `1935-08-14` for the same fact.
    - `releaseDate` string, nullable: When the document was released publicly, where that differs from when it was issued. NLRB advice memoranda are written years before release; measured, the two dates are never equal. Omitted from the response when it has no value.
    - `releaseDateRaw` string, nullable: The release date as the publisher writes it, present only when it differs from `releaseDate`, or null when it is not a date at all.
    - `documentNumber` string, nullable: The issuer's own document or case number, for exact lookup: an FCC DA number, an NLRB case-handling docket, a ruling number. On NLRB advice memoranda and FCC/HHS OCR documents this is not recoverable from `sectionNumber`. Omitted from the response when it has no value.
    - `caseName` string, nullable: The charged party or covered entity a document concerns. Only 27% equal to `sectionTitle` on HHS OCR, so it is not recoverable from the served text. Omitted from the response when it has no value.
    - `forum` string, nullable: For `corpusType=AGENCY_ADJUDICATION`, the KIND of proceeding that produced the document, in the publisher's own words. On CFPB enforcement actions this is `Administrative Proceeding` (the Bureau's own Office of Administrative Adjudication, under 12 C.F.R. Part 1081) or `Civil Action` (a suit the Bureau filed in a federal district court). One action can carry both, in which case they are joined with `; `. Null on every other corpus. Omitted from the response when it has no value.
    - `court` string, nullable: The body that heard the matter, where the publisher names one. Distinct from `forum`, which is the KIND of proceeding: `forum` has two values and is what you filter on, `court` has as many values as there are districts and is for display. Populated on every CFPB civil action and on the administrative proceedings the Bureau labels with its own adjudication office. Omitted from the response when it has no value.
    - `relatedDocuments` string[], nullable: The publisher's own labels for the filings whose text this record carries, in the order the publisher lists them. A CFPB enforcement action is ONE legal event published as two to seventeen PDFs and the unit we serve is the ACTION, not the filing: a consent order and the stipulation consenting to it are one record, because splitting them makes every search return two half-answers. This is what tells you which filings are inside the record you are holding. Only the operative instrument is mirrored under `pdfUrl`. Omitted from the response when it has no value.
    - `settlementAmount` string, nullable: The monetary penalty or settlement, as the agency prints it. 95.2% populated on HHS OCR resolution agreements, where it is the single most-asked fact of the corpus. Omitted from the response when it has no value.
    - `requesters` string[], nullable: Who asked for the determination or relief. On export-control commodity-jurisdiction determinations this is the applicant (100% populated); on no-action letters it determines who may rely on the relief. Omitted from the response when it has no value.
    - `program` string, nullable: The benefit or regulatory program a document governs, e.g. Old-Age and Survivors Insurance. 100% populated on Social Security rulings, where it is the primary axis a practitioner filters on. Omitted from the response when it has no value.
    - `languageCode` string, nullable: ISO code of the language the document is written in, present where a corpus is not wholly English. 86% of Puerto Rico insurance bulletins are Spanish (`es`). Omitted from the response when it has no value.
    - `volume` integer, nullable: Volume number for corpora organised in volumes, e.g. the USCIS Policy Manual, whose Volume is the top hierarchy level and had no served representation at all. Omitted from the response when it has no value.
    - `articleNumber` string, nullable: Article number. Article is the PRIMARY hierarchy level in state constitutions, where `chapter` and `part` are 0-6% populated, so without this those corpora served almost no structure. Omitted from the response when it has no value.
    - `articleName` string, nullable: Article title, the companion to `articleNumber`. Omitted from the response when it has no value.
    - `ruleSetCode` string, nullable: Stable machine key for the rule family, where `ruleSet` gives only the prose name. 100% populated on the court-rules states that have a rule set. Omitted from the response when it has no value.
    - `edition` string, nullable: The publisher's edition or year for this text. Omitted from the response when it has no value.
    - `relatedCitations` string[], nullable: Citations OUT of this document that are neither USC nor CFR: the state statutes a regulation implements, the Internal Revenue Code sections a ruling construes, other guidance it points at. `crossReferencesUsc` and `crossReferencesCfr` are 0% on several of these corpora, so this is the only outbound citation set they have. Omitted from the response when it has no value.
    - `supersessionActions` object, nullable: What this document does to EARLIER documents, keyed by the issuer's own verb: `modifies`, `obsoletes`, `amplifies`, `clarifies`, `rescinds`, each mapping to the documents affected. `supersedes` and `supersededBy` cover only the strongest verb. Without these a caller cannot tell a modified revenue procedure from an untouched one, nor see which memorandum rescinded which. Omitted from the response when it has no value.
    - `subtitle` string, nullable: Subtitle, where a jurisdiction puts a level between title and chapter. Maryland's regulations are organised Title > Subtitle > Chapter and are 100% populated; no other served field expressed that level. Deliberately not the same as `subchapter`, which sits below chapter. Omitted from the response when it has no value.
    - `subtitleName` string, nullable: Subtitle title, the companion to `subtitle`. Omitted from the response when it has no value.
    - `publisherKey` string, nullable: The publisher's own stable identifier for this document, where it issues one. On the US Code this is the OLRC's `usckey` (100% populated), which joins directly to the uscode.house.gov bulk XML; on Colorado regulations it is the state's rule id. Use it to reconcile our records against the publisher's without matching on citation strings. Omitted from the response when it has no value.
    - `versionId` string, nullable: The publisher's identifier for THIS VERSION of the document, where it versions them separately from the document itself. 100% populated on Colorado regulations, where it is the only version pointer that exists. Omitted from the response when it has no value.
    - `referencedShortTitles` string[], nullable: Popular names of acts this section REFERENCES, ~10% of the US Code. Distinct from `popularName`, which is the section's own. Omitted from the response when it has no value.
    - `subjectNumber` string, nullable: The publisher's numbered subject index entry, the companion to the term in `topics`. 100% populated on Social Security rulings. Omitted from the response when it has no value.
    - `audience` string, nullable: Who the document is addressed to or binds, where the issuer states it. 100% populated on the Montana insurance bulletins. Omitted from the response when it has no value.
    - `sourceCharStart` integer, nullable: Character offset where this text begins in the source document, for callers reconciling our extraction against the original PDF. Pairs with `sourcePageStart`. Omitted from the response when it has no value.
    - `sourceCharEnd` integer, nullable: Character offset where this text ends in the source document. Omitted from the response when it has no value.
    - `matchSegment` 'rule_text' | 'source_credit' | 'note', nullable, required: On a search hit in a federal rule, which part of the rule document the matched passage sits in: `rule_text`, `source_credit`, or `note` (an Advisory Committee Note). Null when unknown, and always null outside federal rules and on a section fetched by id. A label only, it never changes the ranking.
    - `matchNoteYear` integer, nullable, required: When `matchSegment` is `note`, the year named by the note heading the passage sits under (1993 for 'Notes of Advisory Committee on Rules, 1993 Amendment'). Null when the heading names no year or `matchSegment` is not `note`.
    - `alternateCitations` string[], nullable: Other official citation forms for THIS document, where a publisher prints more than one. Puerto Rico gives an L.P.R.A. cite, Arizona a long form, the IRS an Internal Revenue Bulletin cite, the Federal Reserve a paired Consumer Affairs number. Distinct from `relatedCitations`, which is what this document points AT. Use these when you need to match a citation a user typed in the form their jurisdiction actually publishes. Omitted from the response when it has no value.
    - `expirationDate` string, nullable: When this rule lapses unless re-adopted, as `YYYY-MM-DD`. Distinct from `reviewDate` (the review deadline) and from any amendment date: it is in the future and it ENDS the rule. See `expirationDateRaw` for the publisher's wording. Omitted from the response when it has no value.
    - `expirationDateRaw` string, nullable: The expiry date as the publisher writes it, present only when it differs from `expirationDate`. State regulators print this as `1/1/2028` and `03-01-2029` as well as ISO.
    - `committeeNote` string, nullable: Advisory-committee note on a procedural rule: the standard interpretive gloss courts read alongside the rule text. Deliberately separate from `amendmentNote`, which records when the rule changed rather than what it means. Omitted from the response when it has no value.
    - `sourcePageStart` integer, nullable: First page in the official PDF this text was extracted from, for a pinpoint print citation. 100% populated on the Federal Rules. Omitted from the response when it has no value.
    - `sourcePageEnd` integer, nullable: Last page in the official PDF; companion to `sourcePageStart`. Omitted from the response when it has no value.
    - `displayLabel` string, nullable: The publisher's own short label for this section, e.g. `Cal. BPC § 655.2` or `MPEP § 2165.03`. Populated on essentially every document we hold. Usually equal to `citationShort`, but not always: on the Federal Communications Commission, NLRB, HHS OCR and BIS corpora the two differ on every document, and there `displayLabel` is the form the publisher itself prints. Omitted from the response when it has no value.
    - `publicationDate` string, nullable: The date this document was published by its source. For Federal Register documents this is the FR publication date, the primary citation and sort key, populated on 100% of rules and proposed rules. Distinct from `effectiveDate` (when it takes legal effect) and from `issueDate` (when the issuing body dated it). A rule is routinely published before it is effective. Omitted from the response when it has no value.
    - `publicationDateRaw` string, nullable: The publication date as the publisher writes it, present only when it differs from `publicationDate`, or null when it is not a date at all.
    - `publicLawCites` object[], nullable: Structured Statutes at Large citations parsed out of the source credit, populated on ~72% of the US Code. Each entry carries `statVolume`, `statPage`, `type` and a `display` string. `publicLaws` gives the bare `Pub. L.` list and `sourceCredit` the raw prose; this is the same information already parsed, so a caller can link to the Statutes at Large without re-parsing the credit line. Omitted from the response when it has no value.
    - `topLevelTitle` string, nullable: The outermost division this document sits under, where the corpus has one that `titleNumber`/`chapter`/`part` do not already express. Examples: `Title 9: Criminal` for the DOJ Justice Manual, `Volume 1 - General Policies and Procedures` for the USCIS Policy Manual. Null for flat corpora, where one document is the whole unit. Omitted from the response when it has no value.
    - `externalUrl` string, nullable, required: The publisher's own page for this section, exactly as recorded at ingest: uscode.house.gov, ecfr.gov, a state legislature or a state register. Null when the publisher issues no per-section link, or when the link is withheld. Prefer `sourceUrl`, which is this link when present and otherwise the best official alternative. Some official publishers serve their code only through a JavaScript application, so the link renders in a browser but returns an empty page shell to a plain HTTP client. Texas is the main case: the Secretary of State publishes the Texas Administrative Code only on its Appian portal (texas-sos.appianportalsgov.com). The link is still the correct citation. To check a section without a browser, use `adoptingCitations` (for Texas, the `NN TexReg PPPP` register citations that adopted and amended it) and read the text we captured at `textUrl`.
    - `sourceUrl` string, nullable, required: Where the government published this text: the link to cite and to verify against. The same value `/us/statutes/section/{actId}/body` returns as `sourceUrl`, on every search result, section record and batch item. It is `externalUrl` when the publisher issued a per-section link, and otherwise falls back to the govinfo.gov page, then the state's own page, then our archived copy of the publisher's page. Null when we hold no publishable link: only official government links are served here.
    - `sourceUrlNote` string, nullable, required: Says why `sourceUrl` is null. Either we serve no link for this section on purpose and it is cited by `citation` alone, or the publisher issues it only inside a larger file (an archive, spreadsheet or whole volume) that is not a page of the section, or no source link is recorded for it at all. Null when `sourceUrl` is set.
  - `next` StatuteResult[]: Sections immediately AFTER this one, nearest first.
    - `actId` string, required: Unique section identifier (e.g., 'USC_T42_C21_S1983', 'CFR_T17_P240_S240_10b5_1').
    - `citation` string, nullable, required: Full citation (e.g., '42 U.S.C. § 1983 (2024)', '17 C.F.R. § 240.10b5-1 (2026)'). Always present; null when not known.
    - `citationShort` string, nullable, required: Short citation (e.g., '42 U.S.C. § 1983', '17 C.F.R. § 240.10b5-1'). Always present; null when not known.
    - `title` string, nullable, required: Section title. Always present; null when not known.
    - `corpusType` string, nullable, required: The corpus this section belongs to: one of `USC`, `CFR`, `STATE`, `CONSTITUTION`, `FEDERAL_RULES`, `FEDERAL_LOCAL_RULES`, `STATE_CONSTITUTION`, `STATE_RULES`, `EXECUTIVE_ACTION`, `REGULATION`, `FEDERAL_REGISTER`, `FEDERAL_REGISTER_NOTICE`, `AGENCY_GUIDANCE`, `SENTENCING_GUIDELINES`, `US_TAX_TREATY`, `US_TREATY`, `STATE_AGENCY_GUIDANCE`, `STATE_AG_OPINION`, `STATE_REGISTER`, `SESSION_LAW`, `STATUTE_COMPILATION`, `AGENCY_ADJUDICATION`, `CFR_ANNUAL`, `USC_ANNUAL`, `FEDERAL_BILL`, `FEDERAL_RULES_ANNUAL`, `FEDERAL_RULES_PROPOSED`. The same tokens the `corpusType` filter accepts. Always present; null when not known.
    - `state` string, nullable, required: 2-letter lowercase state code (e.g. `ca`, `tx`) when the row belongs to a state corpus. `federal` for federal rows. Always present; null when not known.
    - `source` string, nullable, required: The named source within `corpusType` this row belongs to, for corpora that fold several bodies of law into one token. Pass it back as the `source` search filter to scope to just this source; the accepted values, with their names, are listed on that filter. Null for corpora with only one source, which includes every state's statutes and regulations. Not a link, and not where the text came from: it is a filter token. The official link to the publisher's text is `sourceUrl`.
    - `year` integer, nullable, required: The year this row was ingested, not the year of the law. Most ingesters stamp the capture year (`time.gmtime().tm_year`) and a few pin a literal, so the bulk of the corpus reads the year it was captured. Do not filter or reason about currency with it. `lastAmendedYear` carries the amendment year, `currentThrough` and `currencyNote` carry the publisher's own currency statement, and `goodLawStatus` carries the status. Always present; null when not known.
    - `relevanceScore` number, nullable, required: Relevance score, normalized to roughly 0-1. Higher means a better match for ranking within one response. It is a relative ranking signal, not a calibrated confidence or probability, so do not compare scores across different queries or treat a fixed value as a quality threshold. Exception: a query that resolves to an exact citation (e.g. '42 U.S.C. § 1983', 'Cal. Civ. Code § 1950.5', 'Fed. R. Civ. P. 12') always scores that section 1.0, since it is a certain match rather than a ranked one -- a natural-language or keyword query never returns 1.0 by comparison. null on any endpoint that did not rank: fetching a section by id, a batch fetch, or a section embedded in an intelligence response. When the response carries `rankingDegraded: true`, the relevance model was unavailable and this is a retrieval score on a different, much smaller scale: still a valid ORDER, not a 0-1 relevance.
    - `excerpt` string, required: Text excerpt (up to 500 characters).
    - `body` string, nullable, required: Full plain text of the section. Always a key on the row: filled only when the request set `includeBody: true`, and null otherwise and on any row whose text could not be resolved (those rows are not charged for a body). A section the publisher prints as images has no text: its `body` is null and `bodyUnavailable` is `true`. This is the actual statutory text, not the `excerpt`. The two are different things and the difference matters for quoting: `excerpt` is a ranking preview windowed around the match, so it can begin mid-section and drop a leading subsection marker -- measured 2026-09-02, four of five California rows lost their opening `(a) `. `body` is the document as the publisher printed it.
    - `bodyUnavailable` boolean, nullable: Present, and `true`, only on a section that has no text to return: the publisher prints it as images (an appendix, a form, a map), or the text we hold is only a partial copy of the official text. Omitted on every other section. The section is real and its metadata is complete; there is simply no body, so `body` / `plain` / `html` are null, `available` is false on `/body`, and nothing is charged for a body. Read it instead of treating a null body as a fetch failure that is worth retrying.
    - `bodyUnavailableReason` 'image_only_source' | 'misfiled_source_text' | 'partial_snapshot_text', nullable: Why there is no body, present with `bodyUnavailable`. `image_only_source`: the publisher prints this section as images, so there is no text to extract. Where we hold an official link for the section it is in `sourceUrl`; it is null where we may not republish the publisher's link. `misfiled_source_text`: the text stored under this regulation opens with another rule's number (a prior version filed under a renumbered rule), so it is withheld rather than served as this rule. `partial_snapshot_text`: the text we hold for this section is only a partial copy of the official text, so it is withheld rather than served as if it were complete. Omitted from the response when it has no value.
    - `bodyNote` 'fetch_failed' | 'no_text' | 'insufficient_credits' | 'response_size_cap', nullable: Present only when the request set `includeBody: true` and this row's `body` is null for a reason on our side or yours, so a null body is never silent. `fetch_failed`: reading the text failed this time, retry; not charged. `no_text`: the read succeeded but returned no text for this section; not charged. `insufficient_credits`: your balance could not cover the bodies, so every body on the page was withheld (the ranking you paid for is intact); top up and repeat the call. `response_size_cap`: a batch response carries at most 4,000,000 characters of inline body text, and this row's body was dropped to stay under it; not charged, fetch it from `/section/{actId}/body`. A section printed as images carries `bodyUnavailable` instead.
    - `bodyServedNote` string, nullable: Present only when the request set `includeBody: true` and the `body` on this row is not the section's preferred copy: a lesser copy was served because the preferred one could not be read this time, a rendered table or figure was withheld, or the text is partial. The same words `/section/{actId}/body` returns in `note`. Not cached, so a repeat call may return the preferred copy.
    - `matchContexts` BooleanMatchContext[], nullable: Present only with `matchType: "boolean"`: up to 3 passages showing where this section satisfied the expression, in the order they appear in the section. Highlights follow the engine that decides membership: every conjunct of an AND, the OR branches that matched, the words of a phrase, both operands of a satisfied `/N`, `/s` or `/p` pair, the occurrences counted by `atleastN`, and for `a NOT W/N b` the `a` that has no `b` in range. A NOT never highlights anything. Unlike `excerpt` (the passage the relevance model ranked, which may not contain your terms), these passages always do. Empty (`[]`) when the expression matched only in the heading or citation (`title( )`, `cite( )`). Absent on a row whose passages could not be prepared within the search's time allowance; the row is still a verified match. Contexts never change which sections are returned, their order, or the price.
      - `text` string, required: About 240 characters of the section's text as published, cut on word boundaries, with each run of whitespace (line breaks included) shown as one space and soft hyphens removed (a word hyphenated across a line break is joined). It can begin and end mid-sentence.
      - `highlights` array[], required: The words that satisfied the expression, as `[start, end]` character offsets into `text` (start inclusive, end exclusive, counted in Unicode code points, so `text.slice(start, end)` in JavaScript holds only for text without astral characters; Python's `text[start:end]` always does). Sorted, never overlapping. Offsets point at the text as printed, which matching normalizes: a highlight for `section` can cover `§`, one for `café` can cover `CAFÉ` or a decomposed accent, and one for a phrase covers the whole phrase. Plain offsets, not markup, so you choose how to style them.
        - integer[]
    - `titleNumber` string, nullable, required: USC/CFR/state title number (e.g. '26', '13A'). Always present; null when not known.
    - `titleName` string, nullable, required: Title name (e.g., 'The Public Health and Welfare'). Always present; null when not known.
    - `chapter` string, nullable, required: Chapter number or identifier. Always present; null when not known.
    - `chapterName` string, nullable, required: Chapter name. Always present; null when not known.
    - `sectionNumber` string, nullable, required: Section number (e.g., '1983', '240.10b5-1'). Always present; null when not known.
    - `sectionTitle` string, nullable, required: The section's own heading (e.g., 'Rule G. Forfeiture Actions In Rem'). Distinct from `title`, which is the hierarchical display path. Always present; null when not known.
    - `displayPath` string, nullable, required: Full hierarchical path (Title > Chapter > Section). Always present; null when not known.
    - `breadcrumb` object[], nullable, required: Structured breadcrumb trail for navigation. Always present; null when not known.
    - `parent` object, nullable, required: Query for `GET /us/statutes/divisions` that lists this section's siblings (its containing chapter, part, code, article or federal rule set). Pass it straight back to walk up the hierarchy, or spread it into a `POST /us/statutes/search` body to search within that container: every key it carries is also a search filter. Null when the container cannot be determined.
    - `subchapter` string, nullable, required: Subchapter number or identifier. Always present; null when not known.
    - `subchapterName` string, nullable, required: Subchapter name. Always present; null when not known.
    - `part` string, nullable, required: Part number or identifier (CFR/state). Always present; null when not known.
    - `partName` string, nullable, required: Part name. Always present; null when not known.
    - `subpart` string, nullable, required: Subpart number or identifier (CFR). Always present; null when not known.
    - `subpartName` string, nullable, required: Subpart name. Always present; null when not known.
    - `popularName` string, nullable, required: Popular/common name of the act (e.g. 'Truth in Lending Act'), when known. Always present; null when not known.
    - `actStatus` string, nullable, required: Raw section status: `in_force`, `repealed`, `renumbered`, `transferred`, `omitted`, `reserved`, `vacant`, or `unconstitutional`. Some corpora also use `superseded` (a prior version), `enacted`, `pending` and `non_precedential`. This is the status recorded for the section; the currency verdict is `goodLawStatus`. Always present; null when not known.
    - `goodLawStatus` string, nullable, required: Derived currency verdict: `good_law`, `not_good_law`, `not_operative`, or `unknown`. `unknown` means no currency verdict is asserted for the section, which is different from out of date. It is returned where a jurisdiction does not publish repeal information (state statutes for California, for example, are stored `in_force` with `goodLawStatus: unknown`: the stored status is the publisher's own, and we do not certify it current because that state's repeal markers have not been verified), and for these corpora by design: attorney general opinions, register notices, statute compilations, the U.S. Code, executive actions and treaties. Annual editions (`cfr_annual`, `usc_annual`) return `not_good_law` because a later edition supersedes them. Read `corpusType` beside this field. `null` when currency checking is disabled.
    - `goodLawBasis` string, nullable, required: Why `goodLawStatus` has the value it has, as a short code; `null` exactly when `goodLawStatus` is `null`. `good_law`: `in_force` (recorded in force, in a jurisdiction whose repeal information we track). `not_good_law`: `repealed_or_moved` (repealed, renumbered, transferred or recodified), `past_edition` (an annual edition later editions supersede), `proposal` (a bill or proposed rule, never law at any stage), `superseded_by_later_guidance` (IRS guidance a later document superseded, obsoleted or revoked in full), `later_rule_removed` (a Federal Register final rule a later final rule removed from the CFR) or `later_order_revoked` (an executive order a later one revokes or supersedes in full). For the last three `supersededBy` names the later document, and for the last `actStatus` reads `revoked` or `superseded`. `not_operative`: `reserved_or_inactive` (reserved, vacant or unfunded), `not_yet_effective` (a future effective date is printed in the heading, or a final rule's `frEffectiveOn` is ahead) or `publisher_marker` (the publisher's own bracketed note in the heading). `unknown`: `no_repeal_signal` (the publisher gives no repeal markers to check its stored status against), `frozen_snapshot` (served from an edition frozen at a past date), `stated_as_of_date` (current only to the date the text states), `no_status`, `text_omitted_by_publisher` (the legislature prints only a placeholder such as 'Amendatory provisions; text omitted'; `currencyNote` says so) or `status_unrecognized`.
    - `currencyNote` string, nullable, required: Source's 'current through ...' note, when published. Always present; null when not known.
    - `renumberedTo` string, nullable: Where the publisher says this section went, when `actStatus` is `renumbered`. RAW SOURCE FORM, not an `actId` and not a citation: `self:4651` means section 4651 of this same title, `34:10105` means section 10105 of Title 34. Do not pass it to a section endpoint. Read `renumberedToLabel` instead, or resolve the citation it names through `/us/statutes/resolve`. Omitted from the response when it has no value.
    - `renumberedToLabel` string, nullable: `renumberedTo` written out, e.g. `section 10105 of Title 34`. Present whenever `renumberedTo` is. Omitted from the response when it has no value.
    - `transferredTo` string, nullable: Where the publisher says this section went, when `actStatus` is `transferred`. Same raw source form as `renumberedTo`, and the same warning: it is not an `actId`. Omitted from the response when it has no value.
    - `transferredToLabel` string, nullable: `transferredTo` written out. Present whenever `transferredTo` is. Omitted from the response when it has no value.
    - `issueDate` string, nullable, required: Issue/publication date of this version, as `YYYY-MM-DD`, when known. See `issueDateRaw` for the publisher's wording on the rare source that does not print ISO. Always present; null when not known.
    - `issueDateRaw` string, nullable: The issue date as the publisher writes it, present only when it differs from `issueDate`. Null across the corpus today; it exists so a source that starts printing prose cannot silently put prose in a field documented as a date.
    - `crossReferencesCfr` string[], nullable: CFR cross-references parsed from the text, e.g. `['1.6011-4']`. Omitted from the response when it has no value.
    - `crossReferencesCfrChecked` CfrReferenceCheck[], nullable: Each distinct entry of `crossReferencesCfr`, checked against the sections we hold. Only populated on `GET /us/statutes/section/{actId}` for a CFR section with references; null on search results and when the check could not be made, in which case treat the raw list as unchecked. Omitted from the response when it has no value.
      - `reference` string, required: The reference exactly as stored in `crossReferencesCfr`.
      - `title` integer, nullable: CFR title the reference names or was assumed to name. Null if malformed.
      - `section` string, nullable: Section number with sentence punctuation removed (`80.1426.` is `80.1426`).
      - `status` 'held' | 'not_held' | 'malformed', required: `held`: this exact section is in the corpus (fetch it by `actId`). `not_held`: no section with this exact number is held in that title; it may be a truncated stem, a part we do not hold or an extraction error. We never substitute a nearby section. `malformed`: not shaped like a CFR section number.
      - `actId` string, nullable: The held section's id, when `held`.
      - `titleAssumed` boolean: True when the reference carried no title and the citing section's own title was assumed. Such a reference can point at another title.
    - `crossReferencesUsc` string[], nullable: USC cross-references parsed from the text, e.g. `['42:1983']`. `'self:<section>'` denotes a reference to another section of the same title. Omitted from the response when it has no value.
    - `statutoryAuthority` object[], nullable: For a CFR/eCFR section: the USC (or other) citations in its 'Authority' note that authorize the rule, e.g. `[{'type': 'usc', 'title': 15, 'section': '78o', 'display': '15 U.S.C. 78o'}]`. Null for non-regulation corpora. Omitted from the response when it has no value.
    - `implementingRegulations` object[], nullable: For a USC section: the CFR parts that implement it, derived from the reverse of every CFR section's own `statutoryAuthority`, e.g. `[{'cfrTitle': 17, 'part': '240', 'partName': '...', 'display': '17 CFR Part 240'}]`. Null for non-USC corpora. Omitted from the response when it has no value.
    - `frRegulationIdNumbers` string[], nullable: Regulation Identifier Number(s) (RIN) assigned to this rule. Omitted from the response when it has no value.
    - `frDocketIds` string[], nullable: Rulemaking docket ID(s) this document was filed under. Omitted from the response when it has no value.
    - `frEffectiveOn` string, nullable: The rule's effective date (ISO 8601 date), when set. Omitted from the response when it has no value.
    - `frCommentsCloseOn` string, nullable: Public-comment deadline (ISO 8601 date). Proposed rules only. Omitted from the response when it has no value.
    - `frSignificant` boolean, nullable: Whether the Federal Register marked this rule 'economically significant' (EO 12866). Omitted from the response when it has no value.
    - `frCorrectionOf` string, nullable: Federal Register document number this document corrects, when this is a correction. Omitted from the response when it has no value.
    - `frCorrections` string[], nullable: Federal Register document number(s) that later corrected this document. Omitted from the response when it has no value.
    - `frRegulationsDotGovUrl` string, nullable: Link to this document's public comment docket on regulations.gov. Omitted from the response when it has no value.
    - `frRelatedDocuments` FrRelatedDocument[], nullable: Other Federal Register documents sharing this document's RIN(s) (its proposed rule, its final rule, and any corrections), most recent first. Only populated on `GET /us/statutes/section/{actId}` for a row that carries `frRegulationIdNumbers`; always null on `/us/statutes/search` results, since computing it needs a follow-up lookup that is too expensive to run per search result. Omitted from the response when it has no value.
      - `actId` string, required
      - `citation` string, nullable
      - `title` string, nullable: The related document's own title/heading, when known.
      - `documentType` string, nullable: `proposed_rule`, `final_rule`, or the raw Federal Register category otherwise.
      - `publicationDate` string, nullable: Federal Register publication date (ISO 8601 date), when known.
    - `frRelatedDocumentsNote` string, nullable: Set only when `frRelatedDocuments` is absent for a reason you should know: this document's RIN is shared by more than 25 other Federal Register documents (an umbrella RIN), so it names no single rulemaking and listing any subset would be a guess; or the related-document lookup was temporarily unavailable, so the list may be incomplete and a repeat call returns it. In that case the call is refunded (`creditsConsumed` is 0). Omitted from the response when it has no value.
    - `subject` string, nullable: The publisher's own subject or document-type label, where it prints one (for example a state insurance bulletin's `RE:` line, or its listing category such as `Rescission`). Omitted from the response when it has no value.
    - `rescindedOn` string, nullable: The date the document was rescinded or withdrawn, as `YYYY-MM-DD`, when the source states one. See `rescindedOnRaw`. Omitted from the response when it has no value.
    - `rescindedOnRaw` string, nullable: The rescission date as the publisher writes it, present only when it differs from `rescindedOn`.
    - `sourceCredit` string, nullable: The Office of the Law Revision Counsel's credit line for a USC section: the acts that enacted and amended it, in order, e.g. `June 25, 1948, ch. 646, 62 Stat. 869; Pub. L. 85-508, Sec. 12, July 7, 1958, 72 Stat. 348`. Parentheses stripped, whitespace normalized. USC only, and null on a USC section that prints no credit (a transferred, repealed or reclassified stub). CFR sections carry the same fact as a list in `federalRegisterCitations` instead, which is why the shape differs; no other corpus publishes one. Omitted from the response when it has no value.
    - `amendmentYears` integer[], nullable, required: Distinct years the section was amended, parsed from the publisher's history note. Always newest first, and de-duplicated. Ingesters store the array in both orders (eCFR writes newest first, state regulations and state statutes write oldest first), so the order is imposed at serve time and the served order is the only one to rely on. Years outside 1789..(current year) are dropped rather than served: amendment dates are parsed out of prose and a note can yield a sunset or substitution date that is not an amendment at all. Always present; null when not known.
    - `lastAmendedYear` integer, nullable, required: Most recent amendment year, when known. Re-derived at serve time as `max(amendmentYears)`, so it never exceeds the list served beside it. Falls back to the publisher's own scalar only when `amendmentYears` is empty, and only when that scalar is itself within 1789..(current year). Always present; null when not known.
    - `amendmentsCount` integer, nullable, required: How many amendments the publisher recorded for this section. Not the length of `amendmentYears`, and it is not safe to derive one from the other. For regulations and court rules this counts amending EVENTS: one per register citation, filing or history entry, so a section amended twice in the same year counts 2 against a single entry in `amendmentYears`. The two disagree on a large share of the regulation and court-rule corpora, so read each for what it is. For the other corpora, and for any source that publishes no per-event record, it is the number of distinct years and is capped at the length of `amendmentYears`, so it never counts a year the list dropped as implausible; it understates a section amended twice in one year. Always present; null when not known.
    - `currentThrough` string, nullable, required: How current the publisher says this text is, in the publisher's own terms. A date (`2025-01-06`) on every USC section and most compilations; otherwise the publisher's wording (`Current through Act 9046 of the 2025 session`, `Public Law 119-60`, `Supp. 19-2`, `2024 Edition`). Do not parse it as a date without checking its shape. `currencyNote` carries the same fact as prose where a publisher writes it that way. Always present; null when not known.
    - `pendingAdoptions` object[], nullable: New York only. State Register adoption notices that post-date the print volume this section's text was taken from. They are notices, not an updated consolidated text: `text` and `body` still reflect `currentThrough` / `currencyNote`. Look the notice up in the State Register by its `idNo`. Each entry: `idNo` (e.g. `DFS-23-26-00013-A`), `scope` (`section` when the notice names this section, `part` when it names the Part containing it), `effectiveDate` (ISO date, null if the notice states none), `agency`, `issueDate` (ISO date of the Register issue). No link is returned; it is withheld under licence, as with `sourceUrl` on these regulations. Only adoptions (`-A`, `-AA`) are listed, never proposals, emergency rules or withdrawals. Null on every section with no such notice, which does not mean the section is current: we cover Register adoptions for NYCRR Titles 3, 19 and 23 only. Omitted from the response when it has no value.
    - `adoptedAfterCurrentThrough` boolean, nullable: New York only. True when `pendingAdoptions` is non-empty, i.e. the State Register records at least one adoption naming this section or its Part that post-dates the volume `currentThrough` refers to, so the text served may be out of date. Null (never false) when no such adoption is recorded; null is not a claim that the text is current. Omitted from the response when it has no value.
    - `amendmentHistory` string[], nullable: Structured amendment entries where the publisher records them separately from the credit line in `history`. Omitted from the response when it has no value.
    - `amendmentHistoryNote` string, nullable: Present only when the section carries no amendment evidence and its state or document type does not record enough amendment history to read absence as a fact (for example New York, Massachusetts, Arizona and West Virginia statutes, several states' regulations, court rules and constitutions, opinions, register notices, bulletins, annual CFR editions and session laws). It says `amendmentYears`, `lastAmendedYear` and `amendmentsCount` are absent because nothing was recorded, not because the section is unamended; `amendmentsCount` is then null rather than 0. Also present on a Maryland section whose `history` is generated from General Assembly session data rather than a publisher credit line. Null where history is recorded, and an empty history there does mean the section has not been amended.
    - `fieldAbsenceNote` string, nullable: Present only when `year` or `effectiveDate` is null AND the ingester of this whole document type never records it (state constitutions carry no `year`; federal local court rules rarely carry a `year` or `effectiveDate`, as of 2026-10-31). It says the field is null because nothing was recorded, which is not a claim that the document has no such date. Null otherwise.
    - `citationNote` string, nullable: Present only on a state-constitution unit the source gives no section number (an amendment, preamble, schedule or whole article). `citation` is then the article-level form without a section sign, and `sectionNumber` is null. Absent otherwise.
    - `responseBounds` ResponseBounds: Whether the default response is the whole record, and if not, what is missing.
      - `truncated` boolean, required: True when at least one field below was shortened. False means this response carries the whole record. Nothing is dropped silently: every shortened field is listed in `fields`.
      - `fields` BoundedField[]: Every field shortened in this response. Empty when `truncated` is false.
        - `field` string, required: The response field that was shortened, by its response name.
        - `unit` 'items' | 'characters', required: `items` for a list, `characters` for the verbatim `history` credit line.
        - `total` integer, required: How many items (or characters) the record holds.
        - `returned` integer, required: How many items (or characters) this response carries.
        - `nextOffset` integer, required: Zero-based position of the first omitted item (or character) in the full value. What follows it is the omitted part: request `full=true` to receive it.
      - `note` string, nullable: Plain-language statement of what was cut and how to get all of it. Present only when `truncated` is true.
    - `sourceNote` string, nullable: The publisher's source note for the section, verbatim. Omitted from the response when it has no value.
    - `effectiveDate` string, nullable, required: When THIS version took effect, as `YYYY-MM-DD`, or null when the publisher's own string does not name one unambiguous day we can read without guessing. On a section with `actStatus=superseded` this is the start of that version's window. The publisher's wording is preserved in `effectiveDateRaw` whenever it differs.
    - `effectiveDateRaw` string, nullable: The date exactly as the publisher writes it, present only when it differs from `effectiveDate`. A section whose publisher already prints ISO leaves this null. Expect prose (`September 8, 1916`), abbreviated months (`Feb. 25, 1868`), US numerics (`9/28/15`), Spanish for Puerto Rico (`26 de junio de 1963`), and values that are not a single date at all (`April 1, 2023 to June 30, 2026`), which is why they cannot be published under `effectiveDate`.
    - `historyEffectiveDate` string, nullable, required: When this version took effect, as `YYYY-MM-DD`, read out of the publisher's amendment credit line in `history`, which is returned beside it as the evidence. A weaker fact than `effectiveDate` (a date the publisher put in a date field), so it is populated only where `effectiveDate` is null. It is the newest commencement the credit line names, and null whenever that cannot be stated without guessing: a credit line that dates only some entries, a date that belongs to a repeal, sunset, applicability rule or another section, a commencement still in the future, a date older than `lastAmendedYear`, or a state whose `history` format we have not measured. Statutes only.
    - `priorEffectiveDates` string[], nullable: Earlier effective dates recorded for the section, each as `YYYY-MM-DD`, in the order the publisher lists them. A publisher's list written as one string (`3-15-22; 7-1-26`) is split into its dates. A value that names no single day (`March 2007`, `immediately`) is not here: it is in `priorEffectiveDatesRaw`. Omitted from the response when it has no value.
    - `priorEffectiveDatesRaw` string[], nullable: The publisher's own wording of `priorEffectiveDates`, one string per stored entry, present only when it differs from the ISO list or holds an entry that names no single day. Nothing the publisher recorded is dropped.
    - `history` string, nullable, required: The publisher's own amendment/history credit line, verbatim, e.g. `Effective 5/4/2005; Superseded 8/1/2016`. `amendmentYears` is parsed from this; keep both when you need the exact wording. Always present; null when not known.
    - `supersededBy` string, nullable: `actId` of the section that replaced this one. Present on a superseded version so you can fetch the current text in one hop via `GET /statutes/section/{actId}`. Omitted from the response when it has no value.
    - `supersedes` string, nullable: `actId` of the earlier version this section replaced, when known. Omitted from the response when it has no value.
    - `pendingAmendments` PendingAmendment[], nullable: Federal Rules only: the amendments proposed to this rule that are not yet in force, each with its lifecycle `status`, `cycle`, `effectiveDate`, `commentPeriodEnd`, `sourceUrl` and `textComplete`. Fetch one with `GET /us/statutes/section/{id}`. Absent on every other section and on a rule with nothing pending. A proposal is never law until its effective date: the text above is the rule in force.
      - `id` string, required: `actId` of the proposed amendment. Fetch it with `GET /us/statutes/section/{id}` or `/body`; it is never returned by an unscoped search.
      - `status` string, nullable: Where the proposal is in the Rules Enabling Act process: `published_for_comment`, `approved_by_standing_committee`, `approved_by_judicial_conference`, `transmitted_to_supreme_court`, `adopted_by_supreme_court` or `transmitted_to_congress`. A proposal that is in force or withdrawn is not listed here.
      - `cycle` integer, nullable: The rules cycle (the year the amendment is meant to take effect).
      - `effectiveDate` string, nullable: The date the amendment takes effect if it is adopted unchanged (ISO 8601 date).
      - `commentPeriodEnd` string, nullable: Last day of the public comment period (ISO 8601 date), when one applies.
      - `sourceUrl` string, nullable: The official page the proposal was taken from, when we hold a link we may publish.
      - `textComplete` boolean, nullable: `true` when the proposed text we hold is the whole amended rule; `false` when it is partial (for example only the changed paragraphs).
      - `commentDocketIds` string[]: Rulemaking docket ids that hold the public comments on this proposal. Each resolves on `GET /us/rulemaking/dockets/{docketId}`. Empty when none is known.
    - `ruleSet` string, nullable: For court rules, the rule family this belongs to, e.g. `North Dakota Rules of Civil Procedure`. Rule numbers repeat across families (a Civil Rule 12 and a Criminal Rule 12 both exist), so this is what disambiguates them. Omitted from the response when it has no value.
    - `publicLaws` string[], nullable: Public Laws referenced by the section, e.g. `['Pub. L. 96-170']`. Omitted from the response when it has no value.
    - `federalRegisterCitations` string[], nullable: Federal Register citations associated with the section, e.g. `['48 FR 3956', '49 FR 15073']`. This is the CFR's form of the credit line `sourceCredit` carries for the USC: the rulemakings that established and amended the section. Populated on 37.4% of CFR sections, empty where eCFR prints no source note. Omitted from the response when it has no value.
    - `granuleId` string, nullable: govinfo granule identifier (USC/CFR provenance). Omitted from the response when it has no value.
    - `packageId` string, nullable: govinfo package identifier (USC/CFR provenance). Omitted from the response when it has no value.
    - `htmlUrl` string, nullable, required: HTML version of the statute section. Always present; null when not known.
    - `pdfUrl` string, nullable, required: PDF version of the statute section. Always present; null when not known.
    - `xmlUrl` string, nullable, required: XML version of the statute section. Always present; null when not known.
    - `textUrl` string, nullable, required: Plain-text version of the section, from the open-data copy we hold in our own storage. Populated for many state corpora (MS, NJ, NY, NV, etc.) and for United States Code sections. The URL is public by design: the text is open data, so it opens without an API key and carries no credit charge. Null when we hold no plain-text copy. It is never a commercial platform's link.
    - `docxUrl` string, nullable: Microsoft Word (DOCX) version, when available. Omitted from the response when it has no value.
    - `stateHtmlUrl` string, nullable, required: HTML rendering of the document. For most state corpora this is the publisher's own page; for corpora we mirror (state agency guidance, regulations, court rules) it is our archived copy of the artifact the publisher served, on statutes-us.vaquill.ai. Use `externalUrl` for the publisher's canonical address. Never a PDF: a mirrored PDF is served as `pdfUrl` instead. Populated for state corpora only. Always present; null when not known.
    - `govInfoHtmlUrl` string, nullable: Official govinfo.gov HTML version. Omitted from the response when it has no value.
    - `govInfoPdfUrl` string, nullable: Official govinfo.gov PDF version. Omitted from the response when it has no value.
    - `abstract` string, nullable: The issuing agency's own summary of the document, as published in the Federal Register. Populated on 99.9% of rules and proposed rules, so a document can be triaged without fetching the full text. Omitted from the response when it has no value.
    - `agencies` string[], nullable: Issuing agencies, by name. Populated on 99.9% of Federal Register documents. Pair with `agencySlugs` when you need the token the `agency` search filter takes. Omitted from the response when it has no value.
    - `agencySlugs` string[], nullable: The issuing agencies as slugs. These are exactly the values the `agency` filter on `/us/statutes/search` accepts, so an agency facet can be round-tripped straight back into a query. Omitted from the response when it has no value.
    - `topics` string[], nullable: The Federal Register's own CFR-index subject terms. Populated on ~71% of rules and ~68% of proposed rules, with one hard boundary: documents published before 2000 carry none, because the Federal Register did not index them this way. Omitted from the response when it has no value.
    - `documentTypeLabel` string, nullable: The instrument type as the publisher names it: `Rule`, `Proposed Rule`, `Presidential Document`, `Declaratory Ruling`, `Resolution Agreement`. Deliberately not `corpusType`, which says which body of law a document belongs to: two documents in one corpus can be very different instruments. Omitted from the response when it has no value.
    - `documentSubtype` string, nullable: Finer instrument class where the publisher gives one. On presidential documents this separates an executive order from a proclamation, a memorandum or a notice (~90% populated there). Omitted from the response when it has no value.
    - `action` string, nullable: The Federal Register's own ACTION line, ~100% populated. Carries distinctions no other field makes: interim final rule, direct final rule, withdrawal, reopening of the comment period. Omitted from the response when it has no value.
    - `president` string, nullable: The president in office for this document, on Federal Register and presidential-document corpora spanning 1994 to present. Omitted from the response when it has no value.
    - `signingDate` string, nullable: When a presidential document was signed, as `YYYY-MM-DD`, which is routinely earlier than `publicationDate` and is the legally operative date. See `signingDateRaw`. Omitted from the response when it has no value.
    - `signingDateRaw` string, nullable: The signing date as the publisher writes it, present only when it differs from `signingDate`.
    - `executiveOrderNumber` string, nullable: The executive order number a lawyer cites the order by (`14179` for Executive Order 14179 of January 23, 2025). Set only on executive orders; the `citation` is the Federal Register page, not this. See `instrumentNumberSource` for where the value came from. Omitted from the response when it has no value.
    - `proclamationNumber` string, nullable: The proclamation number (`10886` for Proclamation 10886). Set only on proclamations. Memoranda, determinations and notices are not numbered in either series and carry null in both fields, never an invented number. Omitted from the response when it has no value.
    - `instrumentNumberSource` string, nullable: Provenance of `executiveOrderNumber` / `proclamationNumber`. `stored` is the number recorded when the document was ingested. `derived_from_text` is read at request time from the document's own header line (`Executive Order 14179 of January 23, 2025`), accepted only when that line opens the document and its date equals `signingDate`; it is null when the header is not in the text returned (for example a later chunk of a search hit), which means unknown, not unnumbered. Omitted from the response when it has no value.
    - `datesText` string, nullable: The verbatim DATES block from the Federal Register, ~98% populated. Worth reading alongside `frEffectiveOn`: a rule with staged or conditional effective dates has them here, and the single date flattens that away. Omitted from the response when it has no value.
    - `frVolume` integer, nullable: Federal Register volume, the `66` in `66 FR 64768`. Omitted from the response when it has no value.
    - `frStartPage` integer, nullable: First Federal Register page, the `64768` in `66 FR 64768`. Omitted from the response when it has no value.
    - `frEndPage` integer, nullable: Last Federal Register page. With `frStartPage` this gives the page RANGE, which `citation` cannot express because it carries only the first page. Omitted from the response when it has no value.
    - `wordCount` integer, nullable: Words in the full document, so a caller can size a fetch before paying for the body. Omitted from the response when it has no value.
    - `issuingAgency` string, nullable: The body that promulgated or issued this document: the state agency behind a regulation, the division behind an agency letter. Populated at 83.6-100% across the state-regulation corpora that carry it. Omitted from the response when it has no value.
    - `adoptingCitations` string[], nullable: Citations to the instrument that ADOPTED this rule: the state register notice, the Washington filing number, the adopting order. The rulemaking audit trail. Unified across four different payload spellings, so this is comparable across states in a way the underlying data is not. These are also the independent way to confirm a section when the publisher's own page cannot be read without a browser (see `externalUrl`): a Texas rule's `['50 TexReg 8285']` names the Texas Register issue and page that printed its adoption. Omitted from the response when it has no value.
    - `lawImplemented` string, nullable: The statute this rule IMPLEMENTS, as distinct from `statutoryAuthority`, which is the statute granting the rulemaking power. Florida populates both and they differ. Omitted from the response when it has no value.
    - `lastAmendedDate` string, nullable: Full date of the most recent amendment, as `YYYY-MM-DD`, where the publisher gives one. See `lastAmendedDateRaw` for the wording. Illinois and Colorado regulations carry their amendment provenance only here and in `amendmentNote`: neither state has a `history`, and Colorado has no `effectiveDate` either, so for Colorado this is the only date that exists. Omitted from the response when it has no value.
    - `lastAmendedDateRaw` string, nullable: The last-amended date as the publisher writes it, present only when it differs from `lastAmendedDate`, or null when it is not a date at all.
    - `amendmentNote` string, nullable: The publisher's amendment credit line where it is stored separately from `history`. Illinois and Colorado regulations, ~72% populated. Omitted from the response when it has no value.
    - `currencyYear` integer, nullable: Machine-readable counterpart to `currencyNote`, which is prose. 100% populated on the nine state-regulation corpora that carry a currency statement. Omitted from the response when it has no value.
    - `reviewDate` string, nullable: The date a rule must be re-adopted or it expires, where the state runs a sunset review. Ohio regulations, ~80% populated. Not an amendment date: it is in the future. Omitted from the response when it has no value.
    - `reviewDateRaw` string, nullable: The review date as the publisher writes it, present only when it differs from `reviewDate`, or null when it is not a date at all.
    - `originalEnactmentDate` string, nullable: When the section was FIRST enacted, as `YYYY-MM-DD`, ~72% populated on the US Code. Deliberately separate from `effectiveDate`: merging them would report an amended section as effective from its original year. On 35.7% of US Code points this is the only enactment date we hold. See `originalEnactmentDateRaw` for the publisher's wording. Omitted from the response when it has no value.
    - `originalEnactmentDateRaw` string, nullable: The enactment date as the publisher writes it, present only when it differs from `originalEnactmentDate`. The US Code prints `Aug. 14, 1935` where GovInfo statute compilations print `1935-08-14` for the same fact.
    - `releaseDate` string, nullable: When the document was released publicly, where that differs from when it was issued. NLRB advice memoranda are written years before release; measured, the two dates are never equal. Omitted from the response when it has no value.
    - `releaseDateRaw` string, nullable: The release date as the publisher writes it, present only when it differs from `releaseDate`, or null when it is not a date at all.
    - `documentNumber` string, nullable: The issuer's own document or case number, for exact lookup: an FCC DA number, an NLRB case-handling docket, a ruling number. On NLRB advice memoranda and FCC/HHS OCR documents this is not recoverable from `sectionNumber`. Omitted from the response when it has no value.
    - `caseName` string, nullable: The charged party or covered entity a document concerns. Only 27% equal to `sectionTitle` on HHS OCR, so it is not recoverable from the served text. Omitted from the response when it has no value.
    - `forum` string, nullable: For `corpusType=AGENCY_ADJUDICATION`, the KIND of proceeding that produced the document, in the publisher's own words. On CFPB enforcement actions this is `Administrative Proceeding` (the Bureau's own Office of Administrative Adjudication, under 12 C.F.R. Part 1081) or `Civil Action` (a suit the Bureau filed in a federal district court). One action can carry both, in which case they are joined with `; `. Null on every other corpus. Omitted from the response when it has no value.
    - `court` string, nullable: The body that heard the matter, where the publisher names one. Distinct from `forum`, which is the KIND of proceeding: `forum` has two values and is what you filter on, `court` has as many values as there are districts and is for display. Populated on every CFPB civil action and on the administrative proceedings the Bureau labels with its own adjudication office. Omitted from the response when it has no value.
    - `relatedDocuments` string[], nullable: The publisher's own labels for the filings whose text this record carries, in the order the publisher lists them. A CFPB enforcement action is ONE legal event published as two to seventeen PDFs and the unit we serve is the ACTION, not the filing: a consent order and the stipulation consenting to it are one record, because splitting them makes every search return two half-answers. This is what tells you which filings are inside the record you are holding. Only the operative instrument is mirrored under `pdfUrl`. Omitted from the response when it has no value.
    - `settlementAmount` string, nullable: The monetary penalty or settlement, as the agency prints it. 95.2% populated on HHS OCR resolution agreements, where it is the single most-asked fact of the corpus. Omitted from the response when it has no value.
    - `requesters` string[], nullable: Who asked for the determination or relief. On export-control commodity-jurisdiction determinations this is the applicant (100% populated); on no-action letters it determines who may rely on the relief. Omitted from the response when it has no value.
    - `program` string, nullable: The benefit or regulatory program a document governs, e.g. Old-Age and Survivors Insurance. 100% populated on Social Security rulings, where it is the primary axis a practitioner filters on. Omitted from the response when it has no value.
    - `languageCode` string, nullable: ISO code of the language the document is written in, present where a corpus is not wholly English. 86% of Puerto Rico insurance bulletins are Spanish (`es`). Omitted from the response when it has no value.
    - `volume` integer, nullable: Volume number for corpora organised in volumes, e.g. the USCIS Policy Manual, whose Volume is the top hierarchy level and had no served representation at all. Omitted from the response when it has no value.
    - `articleNumber` string, nullable: Article number. Article is the PRIMARY hierarchy level in state constitutions, where `chapter` and `part` are 0-6% populated, so without this those corpora served almost no structure. Omitted from the response when it has no value.
    - `articleName` string, nullable: Article title, the companion to `articleNumber`. Omitted from the response when it has no value.
    - `ruleSetCode` string, nullable: Stable machine key for the rule family, where `ruleSet` gives only the prose name. 100% populated on the court-rules states that have a rule set. Omitted from the response when it has no value.
    - `edition` string, nullable: The publisher's edition or year for this text. Omitted from the response when it has no value.
    - `relatedCitations` string[], nullable: Citations OUT of this document that are neither USC nor CFR: the state statutes a regulation implements, the Internal Revenue Code sections a ruling construes, other guidance it points at. `crossReferencesUsc` and `crossReferencesCfr` are 0% on several of these corpora, so this is the only outbound citation set they have. Omitted from the response when it has no value.
    - `supersessionActions` object, nullable: What this document does to EARLIER documents, keyed by the issuer's own verb: `modifies`, `obsoletes`, `amplifies`, `clarifies`, `rescinds`, each mapping to the documents affected. `supersedes` and `supersededBy` cover only the strongest verb. Without these a caller cannot tell a modified revenue procedure from an untouched one, nor see which memorandum rescinded which. Omitted from the response when it has no value.
    - `subtitle` string, nullable: Subtitle, where a jurisdiction puts a level between title and chapter. Maryland's regulations are organised Title > Subtitle > Chapter and are 100% populated; no other served field expressed that level. Deliberately not the same as `subchapter`, which sits below chapter. Omitted from the response when it has no value.
    - `subtitleName` string, nullable: Subtitle title, the companion to `subtitle`. Omitted from the response when it has no value.
    - `publisherKey` string, nullable: The publisher's own stable identifier for this document, where it issues one. On the US Code this is the OLRC's `usckey` (100% populated), which joins directly to the uscode.house.gov bulk XML; on Colorado regulations it is the state's rule id. Use it to reconcile our records against the publisher's without matching on citation strings. Omitted from the response when it has no value.
    - `versionId` string, nullable: The publisher's identifier for THIS VERSION of the document, where it versions them separately from the document itself. 100% populated on Colorado regulations, where it is the only version pointer that exists. Omitted from the response when it has no value.
    - `referencedShortTitles` string[], nullable: Popular names of acts this section REFERENCES, ~10% of the US Code. Distinct from `popularName`, which is the section's own. Omitted from the response when it has no value.
    - `subjectNumber` string, nullable: The publisher's numbered subject index entry, the companion to the term in `topics`. 100% populated on Social Security rulings. Omitted from the response when it has no value.
    - `audience` string, nullable: Who the document is addressed to or binds, where the issuer states it. 100% populated on the Montana insurance bulletins. Omitted from the response when it has no value.
    - `sourceCharStart` integer, nullable: Character offset where this text begins in the source document, for callers reconciling our extraction against the original PDF. Pairs with `sourcePageStart`. Omitted from the response when it has no value.
    - `sourceCharEnd` integer, nullable: Character offset where this text ends in the source document. Omitted from the response when it has no value.
    - `matchSegment` 'rule_text' | 'source_credit' | 'note', nullable, required: On a search hit in a federal rule, which part of the rule document the matched passage sits in: `rule_text`, `source_credit`, or `note` (an Advisory Committee Note). Null when unknown, and always null outside federal rules and on a section fetched by id. A label only, it never changes the ranking.
    - `matchNoteYear` integer, nullable, required: When `matchSegment` is `note`, the year named by the note heading the passage sits under (1993 for 'Notes of Advisory Committee on Rules, 1993 Amendment'). Null when the heading names no year or `matchSegment` is not `note`.
    - `alternateCitations` string[], nullable: Other official citation forms for THIS document, where a publisher prints more than one. Puerto Rico gives an L.P.R.A. cite, Arizona a long form, the IRS an Internal Revenue Bulletin cite, the Federal Reserve a paired Consumer Affairs number. Distinct from `relatedCitations`, which is what this document points AT. Use these when you need to match a citation a user typed in the form their jurisdiction actually publishes. Omitted from the response when it has no value.
    - `expirationDate` string, nullable: When this rule lapses unless re-adopted, as `YYYY-MM-DD`. Distinct from `reviewDate` (the review deadline) and from any amendment date: it is in the future and it ENDS the rule. See `expirationDateRaw` for the publisher's wording. Omitted from the response when it has no value.
    - `expirationDateRaw` string, nullable: The expiry date as the publisher writes it, present only when it differs from `expirationDate`. State regulators print this as `1/1/2028` and `03-01-2029` as well as ISO.
    - `committeeNote` string, nullable: Advisory-committee note on a procedural rule: the standard interpretive gloss courts read alongside the rule text. Deliberately separate from `amendmentNote`, which records when the rule changed rather than what it means. Omitted from the response when it has no value.
    - `sourcePageStart` integer, nullable: First page in the official PDF this text was extracted from, for a pinpoint print citation. 100% populated on the Federal Rules. Omitted from the response when it has no value.
    - `sourcePageEnd` integer, nullable: Last page in the official PDF; companion to `sourcePageStart`. Omitted from the response when it has no value.
    - `displayLabel` string, nullable: The publisher's own short label for this section, e.g. `Cal. BPC § 655.2` or `MPEP § 2165.03`. Populated on essentially every document we hold. Usually equal to `citationShort`, but not always: on the Federal Communications Commission, NLRB, HHS OCR and BIS corpora the two differ on every document, and there `displayLabel` is the form the publisher itself prints. Omitted from the response when it has no value.
    - `publicationDate` string, nullable: The date this document was published by its source. For Federal Register documents this is the FR publication date, the primary citation and sort key, populated on 100% of rules and proposed rules. Distinct from `effectiveDate` (when it takes legal effect) and from `issueDate` (when the issuing body dated it). A rule is routinely published before it is effective. Omitted from the response when it has no value.
    - `publicationDateRaw` string, nullable: The publication date as the publisher writes it, present only when it differs from `publicationDate`, or null when it is not a date at all.
    - `publicLawCites` object[], nullable: Structured Statutes at Large citations parsed out of the source credit, populated on ~72% of the US Code. Each entry carries `statVolume`, `statPage`, `type` and a `display` string. `publicLaws` gives the bare `Pub. L.` list and `sourceCredit` the raw prose; this is the same information already parsed, so a caller can link to the Statutes at Large without re-parsing the credit line. Omitted from the response when it has no value.
    - `topLevelTitle` string, nullable: The outermost division this document sits under, where the corpus has one that `titleNumber`/`chapter`/`part` do not already express. Examples: `Title 9: Criminal` for the DOJ Justice Manual, `Volume 1 - General Policies and Procedures` for the USCIS Policy Manual. Null for flat corpora, where one document is the whole unit. Omitted from the response when it has no value.
    - `externalUrl` string, nullable, required: The publisher's own page for this section, exactly as recorded at ingest: uscode.house.gov, ecfr.gov, a state legislature or a state register. Null when the publisher issues no per-section link, or when the link is withheld. Prefer `sourceUrl`, which is this link when present and otherwise the best official alternative. Some official publishers serve their code only through a JavaScript application, so the link renders in a browser but returns an empty page shell to a plain HTTP client. Texas is the main case: the Secretary of State publishes the Texas Administrative Code only on its Appian portal (texas-sos.appianportalsgov.com). The link is still the correct citation. To check a section without a browser, use `adoptingCitations` (for Texas, the `NN TexReg PPPP` register citations that adopted and amended it) and read the text we captured at `textUrl`.
    - `sourceUrl` string, nullable, required: Where the government published this text: the link to cite and to verify against. The same value `/us/statutes/section/{actId}/body` returns as `sourceUrl`, on every search result, section record and batch item. It is `externalUrl` when the publisher issued a per-section link, and otherwise falls back to the govinfo.gov page, then the state's own page, then our archived copy of the publisher's page. Null when we hold no publishable link: only official government links are served here.
    - `sourceUrlNote` string, nullable, required: Says why `sourceUrl` is null. Either we serve no link for this section on purpose and it is cited by `citation` alone, or the publisher issues it only inside a larger file (an archive, spreadsheet or whole volume) that is not a page of the section, or no source link is recorded for it at all. Null when `sourceUrl` is set.
  - `container` string, nullable: Human label for the grouping the neighbours were drawn from, e.g. the chapter name. Neighbours never cross this boundary.
  - `truncated` boolean: True when `previous` or `next` may be incomplete: the container was larger than the scan bound, the section was not found in its own container, or a neighbouring section could not be loaded. `note` says which. When false, an empty `next` really is the last section of the container and an empty `previous` the first (the container, not necessarily the code; see `note`).
  - `note` string, nullable: Set when `truncated` is true, and also when the section is the first or last of its container (an empty side then means the container ended, not the code: adjacent chapters, parts and titles are not traversed). Never read an empty `previous` or `next` as the edge of the code while this is set.
  - `resolvedFrom` SectionIdentifierResolution: How the identifier you sent was matched, when it was not an exact act_id. Present only when the input did NOT match as sent. Absent (null) means the section is exactly the act_id in your request.
    - `input` string, required: The identifier exactly as you sent it.
    - `actId` string, required: The act_id it matched. Send this next time to skip resolution.
    - `via` 'normalized_id' | 'citation', required: `citation` -- your input was a citation, resolved with the same resolver as `GET /us/statutes/resolve`. Check it the way you would check a `/resolve` answer. `normalized_id` -- your input was an act_id carrying surrounding whitespace, quotes, a trailing period or double percent-encoding, which were removed.
    - `subsection` string, nullable: The pincite your citation carried, e.g. `(h)(11)` for `26 U.S.C. § 1(h)(11)`. The whole section is served; use `pinpoint=(h)(11)` on `/body` to get that subsection, or `structured=true` for the whole tree.
    - `matchLevel` 'container' | 'multiple' | 'repaired' | 'register_reference', nullable: Present only when `section` is NOT the exact unit you cited. `container`: you cited a container in one of the supported forms (a Missouri, New Jersey, West Virginia or Wyoming regulation series or chapter, a constitution article or amendment, an Indiana chapter, an Illinois article, or a U.S. Code chapter such as `18 U.S.C. ch. 96`; a U.S. Code subchapter is not read), and `section` is the FIRST section inside it (see `container` for how many there are and what they are). A state STATUTE chapter, subchapter, title, article or part cited with its container word and a code name we read for that state (`8 Del. C. ch. 1, subch. VII`, `Tex. Penal Code ch. 19`, `N.Y. Penal Law art. 125`, `Mass. Gen. Laws ch. 93A`, `La. R.S. Title 14`) also answers `container`, with `section` the first live section in statutory order, but only where we hold that container and its number is unique within the code. A container we do not hold, a missing or unrecognised code name, a regulation or rule set, or a number that repeats in the code (California repeats chapter numbers across its titles) when the citation names more than one level, returns `resolved: false` with `missReason: container_not_supported`. An article that IS the section unit (`La. Civ. Code art. 2315`, `Tex. Code Crim. Proc. art. 38.23`) is read as a section. To browse chapters, titles and articles use `GET /us/statutes/divisions`. `multiple`: you cited several sections (`§§ 8, 10`, `§§ 1983-1985`) and `section` is the first of them (see `citedSections`), or your citation fits more than one held section (`D.C.COLO.LR 7.1` is both Local Civil and Local Criminal Rule 7.1) and every candidate is listed in `container`; a state statute container number that repeats within its code (`Cal. Penal Code tit. 8` is a title of each of four parts) lists each candidate container's first section there, never picking one, when there are at most 10. `repaired`: the code name you wrote is a recognised miscite and `section` is the one it names (see `repair`); or (`repair.kind: prior_edition`) the text you cited has been replaced by a current one, and `section` is NOT the text you cited: a C.F.R. or U.S.C. section the current code no longer holds, answered with the MOST RECENT historical annual edition we hold, or a superseded rule set whose rule numbers were kept, answered with the current rule (`Tex. R. Civ. Evid. 803` is answered by `Tex. R. Evid. 803`), or a state regulation we hold only as superseded filings, answered with the latest filing (`W. Va. Code R. § 64-14-5`); `repair.interpretedAs` names what was served and why, and `repair.alternatives` lists the other held editions, if any; or (`repair.kind: former_law`, `former_number`) you cited a FORMER section number, recodified or renumbered since, and `section` is the successor the state's own disposition table or history line names, never the former text (a former section split into several answers `multiple`, every successor in `citedSections`). or (`repair.kind: code_name_inferred`) your citation named no code (`CODE ANN. § 73.001`, `Code 4121-3-34`) and `section` is the only one in the state that carries that number, so the code was inferred from the number and not read from your citation; or (`repair.kind: repealed_range`, `renumbered_range`, `range_member`) you cited a New York or California section the publisher printed only inside a run of sections (`6 NYCRR 420.4` inside `420.3 to 420.4`), and `section` is that stub, not the section's own text (`repair.interpretedAs` names the range); `register_reference`: you cited a state register page, and `section` is a rule whose history cites it (see `registerReference`). `resolved` keeps its meaning (a section was returned) and is true at every level; read `matchLevel` to tell an exact section from a first-of-several. Absent for an exact match.
    - `container` ResolveContainerInfo: What the citation named, and what lies inside it.
      - `kind` string, required: What was cited: `chapter`, `subchapter`, `series` (a rule group number such as `5th Cir. R. 47`, held only as `47.1` to `47.10`), `article`, `section` (a constitution section made of numbered paragraphs, or a California regulation held as one document per subsection, `18 CCR 17071` being `(a)` to `(q)`), `amendment`, `document` (a rule set stored as one document holding several editions) or `alternatives` (with `matchLevel: multiple`: the held sections the citation could mean).
      - `label` string, required: The container, as we read your citation.
      - `childCount` integer, required: How many sections the container holds. Always exact, even when `children` is cut.
      - `children` ResolveContainerChild[]: The sections inside, in document order. `section` is the first of them that is in force (the first of all when none is), so it is `children[0]` unless that one is repealed or otherwise not in force. For an `amendment` of a state whose constitution is held as amended text, these are the sections whose own note credits that amendment, which is what the corpus records; a section the corpus does not annotate is not listed.
        - `actId` string, required: The child section's id.
        - `citation` string, nullable: The child's own citation.
        - `status` string, nullable: Its status in the corpus (`in_force`, `repealed`, ...).
      - `truncated` boolean: True when `children` lists fewer than `childCount` sections.
    - `citedSections` string[], nullable: Set with `matchLevel: multiple`. The sections your citation named, as written (a range such as `1983-1985` is one entry); `section` is the first. Omitted from the response when it has no value.
    - `repair` ResolveRepairInfo: A miscite we recognised, and how we read it.
      - `kind` string, required: What was repaired: `code_name` (a recognised miscite of the code name); `prior_edition` (the text you cited has been replaced, so `section` is not it: a C.F.R. or U.S.C. section held only as a historical annual edition, where `interpretedAs` names the edition and its year and `alternatives` the other editions; or a superseded rule set whose numbers were kept, such as the former Texas Rules of Civil and Criminal Evidence, answered with the current rule and the reason in `interpretedAs`; or a state regulation held only as superseded filings, where `interpretedAs` names the latest filing's date and `alternatives` the earlier filings); `code_name_inferred` (the citation named no code, so the only section in the state with that number was served: `interpretedAs` is that section's citation, `cited` the head as you wrote it, and `alternatives` is empty because a number held by two codes is refused, never guessed); `former_law` (you cited a section number the state's code no longer carries, and the state's own disposition table, a code commission comparative table, a revisor's renumbering stub or the Code's history credits, says which current section it became; `cited` is the number you wrote, `interpretedAs` the successor's citation with what the table says: recodified, renumbered or merged, the effective date when the table gives one, and the source. The former text itself is not served; with `matchLevel: multiple` the former section was SPLIT and `citedSections` lists every successor); `former_number` (the same, read from the successor's own history line where the state prints its lineage there: Georgia's `Code 1933, §` and Washington's `Formerly RCW`). Other values name the kind of miscite that was read through, such as `act_section`, `article_edition`, `ca_ucc_article_number`, `cfr_exchange_act_rule`, `cfr_five_digit_part`, `cfr_listing_of_impairments`, `cfr_part_number_mixed`, `cfr_part_omitted`, `cfr_part_truncated`, `cfr_separator`, `cfr_title`, `cfr_title_typo`, `code_article_for_constitution`, `dash_spacing`, `dotted_subdivision`, `duplicated_act`, `federal_label_state_rule`, `footnote_digit`, `former_code_name`, `former_collected`, `former_lpra_repealed_twin`, `former_title_renumbered`, `fused_subdivision`, `fused_subsection`, `fused_subsection_letter`, `glued_et_seq`, `glued_paragraph_letter`, `habeas_rules_stray_number`, `hyphen_restored`, `inside_range`, `letter_suffix_pinpoint`, `local_rule_series_inferred`, `lost_section_sign`, `merged_section`, `nm_rule_set_prefix`, `number_spelling`, `nycrr_title`, `ocr_digits`, `padded_decimal`, `part_and_section`, `pr_appendix_evidence`, `range_member`, `renumbered_provision`, `renumbered_range`, `renumbered_rule`, `renumbered_title`, `restated_rule`, `roman_section`, `set_label`, `slash_for_hyphen`, `snapshot_numbering`, `source_table`, `source_table_split`, `statute_cited_as_regulation`, `tex_statute_under_rule_label`, `title_chapter_form`, `title_dropped`, `title_inferred`, `title_moved`, `trailing_rule`, `transposed_chapter`, `truncated_section`, `usc_appendix_range_point`, `usc_appendix_unique_act`, `usc_cfr_miscite`, `usc_patent_rule_miscite`, `usc_state_code_miscite`, `wrong_rule_set_same_state`, `zero_padded_rule`, `zero_padded_section`, `zero_padding`. The set grows as repairs are added, so treat `kind` as an open string, not a closed enum; `interpretedAs` always says in words what was read.
      - `cited` string, required: The part of your citation we corrected.
      - `interpretedAs` string, required: What we read it as.
      - `alternatives` ResolveRepairAlternative[]: Other sections the name you wrote could also have meant. Empty when the repair was the only reading.
        - `actId` string, required: Another held section the cited name could also have meant.
        - `citation` string, nullable: That section's own citation.
    - `registerReference` ResolveRegisterReference
      - `citation` string, required: The register citation, as we read it.
      - `state` string, required: Two-letter state code of the register.
      - `kind` 'page' | 'range' | 'issue' | 'filing', required: How the citation matched the rules' history notes. `page`: a note cites exactly this volume and page. `range`: a note cites a page range that contains it. `issue`: the citation names a register issue (Colorado, Michigan). `filing`: it names a filing identifier (Washington WSR, Nevada LCB file, Indiana LSA document, Wisconsin register number).
      - `ruleCount` integer, required: How many held rules cite it. Always exact, even when `rules` is cut.
      - `rules` string[]: Their act_ids in document order, starting with the one returned as `section`.
      - `registerItemHeld` boolean: False when `section` is a RULE whose history cites the item (the item itself is not held for this state). True when `section` IS the register item, held under `corpusType=STATE_REGISTER`; then `rules` is that one item and `kind` is `page` (the cite names the page the item starts on) or `range` (a later page of the item).
  - `processingTimeMs` number: Server-side time for this request in milliseconds, excluding network transit. Useful for spotting a slow query; not billed on.
  - `creditsConsumed` number: Credits actually charged for this call, after any refund. Failed work bills 0 and batch endpoints charge per item returned.

## Other responses

- `401`: Missing, invalid or revoked API key.
- `402`: Insufficient credits (`insufficient_credits`, never retry). `creditsRequired` and `creditsAvailable` say how short you are when known; top up, then repeat the call.
- `404`: Section not found. `reason` says why.
- `409`: Idempotency conflict. `idempotency_in_progress`: the original request with this key is still running (retry after `Retry-After`). `idempotency_replay_unavailable`: it completed but its response was too large to replay; nothing is charged again, so check the credit balance instead of retrying.
- `422`: Validation error: `detail` plus one `errors` entry per rejected field. `idempotency_key_reused`: the `Idempotency-Key` was already used with a different request.
- `429`: Rate limit exceeded.
- `500`: Internal error (`internal_error`, retryable). Any credits charged for the call are refunded; retry with backoff and quote `requestId` to support if it persists.

## Changes

- **2026-11-07** `340c0d24d0b6`: 3 warning, 190 info
  - added the new `response_size_cap` enum value to the `next/items/bodyNote/anyOf[subschema #1]/` response property for the response status `200`
  - added the new `response_size_cap` enum value to the `previous/items/bodyNote/anyOf[subschema #1]/` response property for the response status `200`
  - added the new `response_size_cap` enum value to the `section/bodyNote/anyOf[subschema #1]/` response property for the response status `200`
  - added the non-success response with the status `500`
  - …189 more

[Operation history](https://skmtc.dev/vaquill/apis/vaquill-developer-api/changes/api/v1/us/statutes/section/:act_id/related/get.md)

---

[API](https://skmtc.dev/vaquill/apis/vaquill-developer-api.md) - [All operations](https://skmtc.dev/vaquill/apis/vaquill-developer-api/llms.txt) - [OpenAPI document](https://skmtc.dev/vaquill/apis/vaquill-developer-api/revisions/340c0d24d0b6?raw)