Skip to main content
Dated changes to the Vaquill Developer API: new endpoints, new corpora, fixes and behavior changes. Newest first. Every entry carries tags (Corpus, Endpoint, Fix, Breaking, SDK, Docs), and each entry is an item in this page’s RSS feed. Counts in an entry are the counts on its date. For current numbers call GET /us/statutes/coverage. Older entries may name bare routes such as /statutes/laws that are deprecated but still live. The documented routes are under /us/statutes/.

Change policy

  • Write clients to ignore response fields and enum values they do not know.
  • A key documented as conditional is omitted when it does not apply. See Treat a missing optional key as not applicable.
  • A Breaking entry has a Changed heading that says what to do, and an entry that deprecates a route says so.
  • SDK releases are announced here with the SDK tag. See SDKs.
  • To be told when the law changes, not when the API changes, use Law change alerts.
BreakingEndpointFix
Null policy, error codes, per-key limits, refunds

Changed: statute rows omit conditional fields that do not apply

This is the change most likely to affect clients. Statute responses now follow one null policy.
  • Core fields: always present, and null when the value is unknown (for example citation, state and effectiveDate).
  • Conditional extras: omitted from the response when they do not apply, such as a note or diagnostic that explains an unusual outcome and the blocks of fields that only one corpus carries. Before this change some of these keys were sent as null.
  • What to do: treat a missing conditional key as “not applicable” and do not require it. A client that reads row["note"] without a default now fails on rows where it used to get null. Each field’s description in the API reference says which kind it is.
See Treat a missing optional key as not applicable.
statesCovered on GET /us/statutes/section/{actId}/cross-state is the number of other states actually examined, meaning their own search held something to consider. It counts a state whether or not that state appears in neighbors. Historical editions and dead law are excluded from every search, so they never count. A response with rankingDegraded: true is refunded (creditsConsumed 0).See multi-state comparison.
On GET /us/statutes/section/{actId}/cited-by, total is now the true count of citing sections across all pages (the same number as totalCiters) and no longer the size of the page. The new returned field is the number of rows on this page.See section intelligence.
  • Spans: each row carries charStart and charEnd, the span of its first mention in your text, so text[charStart:charEnd] == raw. Both are null when the row has no span of its own.
  • Ranges: a range such as 18 U.S.C. §§ 2510 through 2523 returns its two ends as two rows, marked rangeRole (start or end) with rangePartner naming the other end. The sections between come back as interior rows, described below, and are never charged.
  • Counts: counts.distinctSections is the number of distinct sections, the unit the price and the per-call cap count in. counts.found still counts rows.
  • Outage: when the corpus is unavailable, or half or more of the citations cannot be read, the call answers 503 and the whole charge is refunded.
See pinpoints in a document.
  • Charged: a search with noGoodMatch: true is still charged, because the ranking ran.
  • Refunded: a filtered search whose page is empty, because no section matches the filters or the offset is past the last result, is refunded with a note naming the filters. An empty page with no filters set is charged.
  • Ranking degraded: a page served with rankingDegraded: true has its search charge refunded and says so in notes. Bodies already delivered by includeBody on that page stay charged.
  • includeBody: it adds the body price for each row that returns text. A row whose text cannot be resolved, an image-only section, or a row your balance cannot cover comes back without a body and is not charged for it.
  • Pinpoints: includePinpoint lookups are never charged on their own, on any page.
  • Read the charge: use creditsConsumed for what was billed.
  • excerptChars: the range is 100 to 600, and a value outside it is a 422.
  • fields: includeBody: true now always adds body to fields, and notes says “body was added to fields because includeBody=true.”
  • rankingPartial: a page served from a ranking built from only part of the candidate pool carries rankingPartial: true, including pages 2 and later. Such a ranking is not cached, so repeating the call may return the full one.
See what a search costs.
  • API keys: POST /api-keys with scopes: [] is a 422, where an empty list used to be passed through. allowedIps is removed and is a 422, because the allowlist is no longer supported.
  • Batch sections: POST /us/statutes/sections rejects unknown request fields with a 422 naming the field you probably meant. Inline bodies in one response are capped at 4,000,000 characters in total. Bodies past the cap come back null with bodyNote: response_size_cap and are not charged.
  • Section body: asOf in the future is a 422, and structured combined with asOf is a 422.
  • Session laws list: order accepts asc (default) or desc, and anything else is a 422. A blank jurisdiction is a 422. A date filter the data cannot satisfy answers an empty page with coverage.status: filter_unavailable, naming unavailableFilters, and is not charged.
  • Resolve: a proposed Treasury regulation (Prop. Treas. Reg. or a notice of proposed rulemaking) answers missReason: out_of_scope_corpus with a missReasonHint, because a proposed rule is a Federal Register document and not Code of Federal Regulations text.
  • Interior rows: the sections between the two ends of a range written with a word, such as §§ 101 through 105, come back as rows with rangeRole: "interior", skipped: "range_interior" and rangePartner set to the citation of the range start. A range written with a hyphen stays two ends.
  • Limits: a range lists at most 25 interior sections, and one call returns at most 500. A wider range returns its two ends only, with an entry in notes.
  • Billing: interior rows are never resolved and never billed. Resolve one with GET /us/statutes/resolve if you need it.
  • Counts: counts.interior is the number of interior rows, and they are not counted in counts.found.
See pinpoints in a document.
GET and POST /us/statutes/resolve answer 422 with code invalid_citation_input for a corpusType or state they do not accept. This was a 400 that refunded the charge. Nothing is charged now.
  • GET /us/statutes/coverage: an unknown state is a 422 and no longer an empty 200.
  • GET /us/statutes/divisions: a backend outage answers 503 and is not charged.
  • POST /us/statutes/count: a backend outage answers 503 and is refunded, and a count of zero is refunded.
  • New codes: method_not_allowed (405, with an Allow header listing the right methods), payload_too_large (413), unsupported_media_type (415) and upstream_timeout (504).
  • Renamed defaults: a generic 400 has code bad_request, a session-law 404 has code section_not_found, and the watch-cap 429 has code quota_exceeded with retryable: false.
  • Every 404 and 405: the body carries code and requestId.
  • Test delivery: the cooldown 429 sends Retry-After: 30.
  • 402: the body adds creditsRequired, creditsAvailable and topUpHint when the shortfall is known.
See Errors.
  • Own bucket: a valid API key has its own bucket at your plan limit, and no longer shares it with everyone behind the same IP address.
  • IP backstop: a per-address ceiling of 10 times that limit also applies.
  • Invalid keys: a key that does not validate falls into the shared per-address bucket.
  • New header: X-RateLimit-Scope is key or ip and says which bucket the other X-RateLimit-* numbers describe. It is sent on API-key requests only.
See Rate limiting.
  • Exact charge: a refund reverses one specific charge, so it can never repeat and never exceed what that charge took.
  • Same bucket: refunded credits return to the bucket they came from.
  • Expired bucket: credit whose bucket has expired returns as a new bucket that lasts 30 days.
On GET /us/session-laws/changes, a change of kind merged now carries mergedInto, the sessionLawId of the law it was merged into. It was always null.See session laws.
  • Stored: only a response with a 2xx, 400 or 422 status is stored, and it is replayed for 24 hours.
  • Not stored: any other 4xx, and any response whose call was refunded, is not stored, so a retry with the same key runs again.
  • Disconnects: if you hang up after the call was charged, the charge is refunded automatically and the key is released, so a retry runs again.
See Idempotency.
  • Published values: corpusType on POST /watches now publishes the list of boards that can be watched.
  • Accepted forms: the board key (state_regulation) or the search-style token for the same body of law (REGULATION becomes state_regulation, USC becomes usc). Case does not matter.
  • Anything else: a 422 that lists the allowed values.
  • Not watchable: constitution, executive_action and agency_action, and also cfr_annual, usc_annual, federal_rules_annual, federal_rules_proposed, us_treaty, state_session_law, state_register and federal_bill.
See Law Change Alerts.
  • Refunded: an empty page of GET /us/rulemaking/dockets/list, an empty page of GET /us/rulemaking/dockets/{docketId}/documents for a docket we hold, and an empty page of GET /us/rulemaking/committee-records/list answer creditsConsumed: 0 with a note naming the filters.
  • Past the end: a pageFrom past the last page of a committee record sets textNotice.
See rulemaking.
  • Refunded: a filtered POST /us/session-laws/search whose first page is empty is refunded, with a note naming the filters.
  • Charged: an unfiltered search that finds nothing stays charged, and carries a note.
  • session: the filter now applies to text, phrase and citation searches too. It used to reach only title, bill and code-section searches.
See searching the text.
  • Section lookup: if the Federal Register related-documents scan fails on GET /us/statutes/section, the call is not charged (creditsConsumed 0) and the note says to repeat it.
  • Neighbours: GET /us/statutes/section/{actId}/related now finds siblings whose records lack a state or a title number.
  • Alone: when a wider scan was cut before it could rule out a sibling, the note says that “alone in its container” is not proven.
  • Boolean search: a page with selective filters now comes back full, using up to 5 extra candidate reads. hasMore is false once every candidate has been judged.
  • Required fields: the published StatuteResult schema lists its 49 core fields as required. Each is nullable where the value can be null.
  • fields: with a fields projection, only the keys you requested come back.
  • amendmentsCount: it is capped at the length of amendmentYears. eCFR, state regulations, and state and federal court rules are the exception, because they count amendment events.
  • Refused: GET /us/statutes/section/{actId}/definitions refuses a definitions section scoped to a different chapter, subchapter or part than the section you asked about. The call is not charged and the note names the kind of container that differs.
  • Unverified: when the container on either side is unknown, the terms are kept and a note says the scope could not be verified.
  • Errors: when the scan fails, the call answers 500 and is refunded. It used to keep the credits.
See definitions.
  • Cross-references: crossReferencesUsc and crossReferencesCfr were re-extracted from the section text on 20,274 US Code sections and 14,567 eCFR sections. References that were missing, cut off by an old list cap, filed under the wrong key or stored with trailing punctuation are now correct, and GET /us/statutes/section/{actId}/cited-by reads the corrected lists.
  • Temporary Treasury regulations: Temp. Treas. Reg. cited without the T suffix resolves to the held, current T section as a repaired match. When no current T section is held, the answer stays not_held.
  • Chapter cites: a chapter cite such as M.G.L. c. 265 or Minn. Stat. ch. 609 answers matchLevel: container again, where dated edition records of the same chapter made it answer multiple.
  • Georgia JQC rules: Ga JQC R 17 and Ga JQC R 17(a) resolve to the Judicial Qualifications Commission rule, and no longer to a 1910 code edition.
  • Search reference: the corpusType description on POST /us/statutes/search names every value in its enum, with a one-line description of each.
CorpusEndpointFix
Federal Rules past texts, pending amendments, committee notes

New: FEDERAL_RULES_ANNUAL and FEDERAL_RULES_PROPOSED

Two opt-in tokens hold the Federal Rules’ past texts and their pending amendments. Neither is part of an unscoped search, and neither is watchable.
  • FEDERAL_RULES_ANNUAL: 1,125 superseded texts of 510 Federal Rules, taken from the GPO annual editions of the US Code appendices. The actId is the current rule’s actId plus _E and the year, for example {actId}_E2015. Read goodLawStatus and use FEDERAL_RULES for the rule in force.
  • asOf on a Federal Rule: GET /us/statutes/section/{actId}/body?asOf=YYYY-MM-DD with the current actId now answers from these texts. The record begins 1998-01-26. A date before that returns the earliest text we hold with asOf.isBounded: true, not the text in force on that date.
  • FEDERAL_RULES_PROPOSED: 49 pending or proposed amendment documents on 36 current rules. The actId is the current rule’s actId plus _P and the cycle year. A proposal is not law: actStatus is proposed.
  • pendingAmendments on a rule: a statute result for a Federal Rule lists its pending amendments with id, status, cycle, effectiveDate, commentPeriodEnd, sourceUrl, textComplete and commentDocketIds. It is absent on every other section and on a rule with nothing pending.
  • Refresh: pending amendments are re-read weekly.
See Corpus types, Point-in-time law and Federal coverage.
GET /us/statutes/section/{actId}/body on a Federal Rule now returns its Committee Note one amendment at a time, and for the Civil Rules it adds the original 1937 note as Congress printed it.
  • committeeNotes: a list in print order. Each entry has year, kind, heading, text, effectiveDate and subdivisionsDiscussed. The entries rebuild notes exactly, and notes is unchanged.
  • committeeNote1937Print: the Advisory Committee note of a Federal Rule of Civil Procedure as printed in H.R. Doc. No. 588, 75th Cong., 3d Sess. (1938), with a verdict against the compiled 1937 note in notes: agrees, differs, print_only or none_printed.
  • Text status: printTextStatus is verified only when the print agrees with the compiled note. Every other print text is unverified_ocr: quote the scanned page, not the string. The field also carries page numbers, the source PDF URL with its sourceSha256, and the OCR method and mean confidence.
  • format=operative: both fields are dropped, like notes. A null there means not sent.
Which of the 81 Civil Rules in the print agree, differ or have no printed note, and why Rules 72 to 76 carry no 1937 note, is on Federal coverage.
A watch on a Federal Rule now fires when a pending amendment to that rule moves a stage, even though the rule’s own text has not changed.
  • New optional keys: lifecycleStage and relatedActId on a change in the change feed (GET /watches/{watchId}/changes), on changes[] in a board.updated webhook, and on GET /us/statutes/section/{actId}/changes. They are present only on lifecycle events.
  • What fires: changeKind is amended, lifecycleStage is one of published_for_comment, approved_by_standing_committee, approved_by_judicial_conference, transmitted_to_supreme_court, adopted_by_supreme_court, transmitted_to_congress, in_force or withdrawn, and relatedActId is the actId of the proposed amendment (a _P document).
  • Counts: a lifecycle event is not counted in sectionsAmended.
  • Unchanged: the changeKind enum is still added, amended and removed. Branch on lifecycleStage to tell a stage move from a text change.
See Law change alerts and pending amendments.
Two metered routes under /us/rulemaking/committee-records/ serve the records of the Judicial Conference Rules Committees from uscourts.gov: meeting minutes, agenda books, committee reports, rules packages, preliminary drafts, public comments and rules suggestions.
  • Endpoints: GET /us/rulemaking/committee-records/list (1 credit per page) and GET /us/rulemaking/committee-records/{recordId} (2 credits, with a window of page text).
  • Filters: committee, docType, year, ruleSet, rule (needs ruleSet) and docketId.
  • Links: each record names the comment dockets and the Federal Rules it is linked to, with the method and confidence of every link.
  • Withheld text: for public comments and rules suggestions, title, filename and page text are null and textWithheld is true, because they name private individuals. The record, its date, its dockets and its rule links are served, and sourceUrl points at the original.
  • Still loading: a missing record may not be loaded yet, so it is not proof that none exists.
See US Rulemaking.
The Civil, Criminal, Evidence, Appellate and Bankruptcy Rules and the Supreme Court Rules now serve corrected text for 114 rules.
  • Removed from rule bodies: footnote text and reference digits that had leaked in, running heads, and broken line-end hyphens (thirdparty is now third-party).
  • Restored: printed errata, and em dashes that had been joined with a space.
  • Supreme Court Rules: 35 rules read fled and offcial for filed and official because of a dropped ligature. They now read correctly.
  • actStatus of dead rules: the US Code appendix copies of Civil Rules 74, 75, 76 and 84, Appellate Rules 3.1, 5.1 and 35 and Criminal Rule 54 reported in_force, so excludeRepealed=true still returned them. Abrogated rules now report repealed on both copies. Appellate Rule 35 and Criminal Rules 22 and 54 were transferred, not abrogated, and now report transferred on both copies. excludeRepealed=true drops both values.
  • No change events: the rules themselves did not change, so no change events were emitted and a watch did not fire.
CorpusBreaking
US_TREATY corpus type and treaty citations

New: US_TREATY corpus type and treaty citations

The Senate treaty record has its own corpusType, and treaty citations are now recognised as treaties.
  • New token US_TREATY: the Senate record for 782 treaties considered since 1949 (senate_treaty, senate_treaty_resolution, senate_treaty_document), 1,492 documents. Treaty Document text runs from 1995 (the 104th Congress) on. The us_treaty and senate_executive_report sources belong to the token but have no documents yet.
  • Treaty citations: S. Treaty Doc. No. 98-9 resolves to the Senate record we hold. 20 U.S.T. 361, T.I.A.S. No. 6638, T.S. No. 993, E.A.S. No. 12, 1 Bevans 631 and 658 U.N.T.S. 163 are recognised and return missReason: "not_held" with a missReasonHint that says what treaty material we hold. They no longer come back as ambiguous_jurisdiction or with a hint to cite a U.S. Code section or Public Law. A miss on a Statutes at Large page in volumes 1 to 64 now says the page may be a treaty.
  • Label fix: the tax treaty source name no longer says “Income and Estate”. We hold income tax treaties only.

Changed: US_TAX_TREATY no longer holds the Senate record

The US_TAX_TREATY token now holds only the IRS income tax treaties and their Treasury technical explanations (us_tax_treaty, us_tax_treaty_technical_explanation, 173 documents). The Senate record moved to US_TREATY, so an existing corpusType: "US_TAX_TREATY" filter no longer returns it. To keep the old result set, send both: corpusType accepts a list, as in ["US_TAX_TREATY", "US_TREATY"].
See Federal coverage and treaty citations.
Endpoint
US Rulemaking API

New: US Rulemaking API

Six GET routes under /us/rulemaking/ serve Regulations.gov dockets and documents, Unified Agenda history, OIRA review and Congressional Review Act links, tied together by the RIN.
  • Endpoints: GET /us/rulemaking/dockets/{docketId} (2 credits), GET /us/rulemaking/dockets/list (1 per page), GET /us/rulemaking/dockets/{docketId}/documents (1 per page), GET /us/rulemaking/rins/{rin} (3), GET /us/rulemaking/rins/{rin}/agenda (1 per page) and GET /us/rulemaking/coverage (free).
  • Link quality: every cross-link to the Federal Register, the CFR, public laws and related RINs carries a quality of verified, candidate or ambiguous.
  • Known gaps: few dockets carry a RIN, comment counts are mostly null (not measured), and the GAO listing is partial.
See US Rulemaking.
Endpoint
State regulation browse levels

New: state regulation browse levels

GET /us/statutes/divisions lists the agency level that some state regulation codes print above their chapters.
  • New filters: umbrella, agency and program, for state regulations only. Each needs code.
  • New node kinds: umbrella, agency, program and subpart, which you pass back as the filter of the same name.
  • Maine groups agencies under a department umbrella (10 is Health and Human Services, with agency 144 under it). Virginia and Wyoming list agencies, and Wyoming also lists a program between the agency and its chapters.
  • subpart now also drills into Louisiana and Mississippi regulation codes, with code and the part it sits in.
  • Repeated chapter numbers open the right chapter. Naming the agency (and the program in Wyoming) lists one chapter, so these codes no longer answer a repeated chapter number as a pooled list with a note.
  • Pricing is unchanged. 1 credit per level that returns rows.
See Browse the statute hierarchy for a worked Maine example.
SDK
Official Python and TypeScript SDKs

New: official Python and TypeScript SDKs

Typed clients for the US Data API are now published.
  • Python: pip install vaquill (Python 3.11 or later), with a sync and an async client.
  • TypeScript: npm install @vaquill-ai/sdk (Node 20 or later).
  • CLI: the Python package ships a vaquill command for searches, citation resolution and credit checks from the shell.
  • Built in: retries with backoff, typed errors, pagination iterators, an optional spend guard and Standard Webhooks signature verification.
Before 1.0 the API surface of the SDKs may change in minor versions. See SDKs.
CorpusFix
Fuller section text for Iowa and Wisconsin

Changed: fuller section text for Iowa and Wisconsin

Two groups of sections now return more of what the publisher prints.
  • Iowa: sections that print units at a third level now keep their (n) labels in the returned text (2,390 sections).
  • Wisconsin: sections now keep their tables, forms, See-PDF lines and effective-date text (245 sections).
  • Text offsets changed with the text. charStart and charEnd for these sections index into the new text. If you cached offsets, refresh them: structure.textSha256 is the SHA-256 of the text the offsets belong to, so a stored copy whose hash differs is out of date.
See Pinpoints for the offsets and structure.textSha256.
Endpoint
Pinpoint lookups

New: pinpoints

A citation such as 625 ILCS 5/11-601(c) now returns the text of subsection (c) itself, not only the parent section. No second model call and no parsing on your side.
  • GET and POST /us/statutes/resolve: a pinpoint in the citation adds a pinpoint object beside section, on each item of a batch too. It carries the unit’s own text, the leadIn it completes, its children, its siblings, its character offsets, and structure, which says how far to trust the outline.
  • GET /us/statutes/section/{actId}/body: pass pinpoint=(c)(1) to get one unit beside the full body.
  • POST /us/statutes/extract-citations: a resolved row that carried a pinpoint gets pinpointMatch.
  • POST /us/statutes/search: set includePinpoint: true and the response names the subsection each hit matched, in pinpoints, keyed by actId.
  • Labels that contain a hyphen or a dot are one label. (d-1), (a-5) and (f)(1.5) resolve. Before this, a citation with an inserted subsection such as 625 ILCS 5/11-601(d-1) came back as not held.
  • Misses are explicit. A pinpoint the section does not have returns matched: false with matchLevel, unmatched and available, not the whole section. A section whose outline we could not recover says no_structure.
  • Pricing is unchanged. The same credits as the call without a pinpoint, and includePinpoint adds nothing to a search.
See Pinpoints for the citation forms, what a miss looks like, and how to read structure.quality.
Endpoint
Boolean terms-and-connectors search

New: Boolean search (matchType: "boolean")

POST /us/statutes/search accepts a terms-and-connectors expression when you send matchType: "boolean", in the syntax of the major legal research services.
  • Every result satisfies the expression, judged over the section’s full text, and results are ranked by relevance among the matches.
  • Operators: AND, OR, NOT, same sentence /s, same paragraph /p, within N words /N (1 to 255), the ordered forms +s, +p and +N, atleastN(term), atmN(term), exact phrases ("..." or words side by side), the wildcards *, ! and ?, and grouping with ( ). Word operators are UPPERCASE; lowercase and, or and not are ordinary words.
  • Other services’ spellings are accepted and read as the operator they mean, for example w/5, NEAR/5, ADJ, AND NOT and BUT NOT. See Also accepted.
  • Field restrictions search one part of a section, for example title( ) and cite( ).
  • New response fields, present only in Boolean mode:
    • parsedQuery shows exactly how your expression was read, with every grouping that could be in doubt parenthesized. Send it back as the query to run the same search.
    • queryWarnings lists plain-English warnings about a valid expression that may not mean what you intended, such as AND and OR mixed without parentheses.
  • In any mode, queryHint tells you when a query looks like a Boolean expression, so you can switch to matchType: "boolean".
  • Invalid input is rejected. A malformed expression, an unsupported operator or a value out of bounds is a 422 naming the problem and its character position, and it is not charged.
  • Pricing: the same as any search, 4 credits per call. A 503 from a temporary backend outage is refunded.
See Boolean Search for precedence, limits, recall and errors.
Corpus
US Virgin Islands and American Samoa

New: the US Virgin Islands and American Samoa

state now accepts vi and as, which brings the jurisdictions to 56. Both are kind: "territory" on GET /us/statutes/coverage.
  • Virgin Islands: the Virgin Islands Code (cited V.I. Code Ann. tit. 14, § 1, an unofficial copy with its source link withheld), the Virgin Islands Rules and Regulations (from the Department of Planning and Natural Resources) and court rules in 22 sets.
  • American Samoa: its Code, Constitution and court rules are read from the American Samoa Bar Association’s site, and its Administrative Code from the Office of the Secretary of American Samoa.
  • Citations that resolve: Am. Samoa Code Ann. § 46.4810, A.S.C.A. § 46.4810, Am. Samoa Admin. Code § 4.2126, 12 V.I. R. & Regs. § 803-52 and V.I. R. Civ. P. 6-3.

Changed: state law loads of 2026-10-07 and 2026-10-08

The per-jurisdiction counts are in the coverage matrix.
  • Maryland regulations now cover all 36 titles of COMAR, 29,433 sections, where 23 titles were held before. Cite COMAR 36.04.02.02.
  • Nebraska statutes gained about 9,400 sections, among them the comma-numbered ones and the Uniform Commercial Code.
  • Rhode Island statutes gained sections missing from 1,065 chapters and lost 47 duplicates.
  • Texas statutes gained the Revised Civil Statutes (Vernon’s), 266 articles, as Tex. Vernon's Civil Statutes § 6243n, and the missing Code of Criminal Procedure articles, among them Tex. Code Crim. Proc. art. 38.22.
  • Missouri court rules are served: 1,536 sections, cited Mo. Sup. Ct. R. 55.03.
  • Nevada ADR rules are split by instrument. Nev. R. ADR n now names only the General Provisions, and the arbitration and mediation rules are Nev. Arb. R. n and Nev. Med. R. n.
  • West Virginia carries the Rules of Lawyer Disciplinary Procedure (W. Va. R. Law. Disc. P. 6.3) and the Rules of Judicial Disciplinary Procedure (W. Va. R. Jud. Disc. P. 7.1).
  • Florida carries the admissions rules (Fla. Bar Admis. R. 3-23.3).
  • Montana carries the Code of Judicial Conduct (Mont. Code Jud. Conduct R. 2.9) and the Sentence Review Division Rules (Mont. Sent. Rev. Div. R. 4).
  • Massachusetts juvenile and probate court rules are cited under their own families, for example Mass. Juv. Ct. Care & Prot. Rule 5, Mass. Prob. & Fam. Ct. Rule 4-09 and Mass. Supp. Prob. & Fam. Ct. Rule 201.
  • Hawaii evidence rules are served rule by rule, as sections of HRS chapter 626: Haw. R. Evid. 404.
  • Pennsylvania serves the Constitution’s Schedule apart from Article V (Pa. Const. sched. art. V, § 4), and holds 54 sections of the unconsolidated statutes (35 P.S. ch. 780, for example 35 P.S. § 780-102). The rest of the unconsolidated statutes are not held.
  • Puerto Rico carries Reorganization Plan No. 2-2011 (Plan Reorg. Núm. 2-2011 P.R. art. 14) and the 1930 Civil Code, 1,811 articles all marked repealed (Cód. Civ. 1930 P.R. art. 481), beside the 2020 Civil Code.
  • Maine carries the MaineCare manual (10-144 C.M.R. ch. 101, ch. II, § 25), and New Hampshire the Department of Environmental Services rules, among them N.H. Admin. Rules, Env-Wq 403.17.
Corpus
State register notices

New: state register notices

corpusType=STATE_REGISTER holds the proposed, adopted and emergency rule notices that a state printed in its official register: 144,876 items across 24 jurisdictions, mostly Pennsylvania (60,304) and New York (23,739).
  • Not codified law. Items carry goodLawStatus: "unknown", year is the year of the issue, and they are never ranked as primary law.
  • Register citations: a state register page cited by volume and page resolves with matchLevel: "register_reference", described in the next entry.
See State administrative registers.
Endpoint
matchLevel flag on resolve answers

New: a flag on answers that are not the exact section you cited

GET and POST /us/statutes/resolve carry an optional matchLevel when section is not the exact unit you cited, with a companion field that says what happened. An exact match carries none of them and is unchanged.
  • A register citation resolves only on an exact volume and page, a range that contains the page, or an exact filing identifier.
  • A citation that resolved to nothing before and resolves now only through one of these readings is not pinned to rank 1 by search.
See matchLevel.
Corpus
County and district trial-court rules

New: county and district trial-court rules

38 trial courts’ local rules, 5,363 rules (4,868 in force), under corpusType=STATE_RULES with the county or district in the actId. Citations such as Cook Cnty. Cir. Ct. R. 2.1, LRSF 16.15, KCLCMR 7 and Phila. R.J.A. 4008 resolve.
Eight California superior courts, Cook, Winnebago and Lake in Illinois, Philadelphia, Allegheny, Lancaster and Bucks in Pennsylvania, Harris, Travis and Bexar in Texas, Cuyahoga and Franklin in Ohio, King in Washington, Wayne in Michigan and fifteen Arizona counties.
See Court rules from county and district trial courts.
Corpus
Additions to existing corpora, corpusType enum

Changed: the corpusType enum and recounted totals

  • The OpenAPI corpusType enum now carries 23 tokens: the 22 on Corpus types and USC_ANNUAL, a retired GPO edition of the US Code that is not a token to search. state accepts 56 jurisdictions.
  • The statutes, regulations, court rules and constitutions totals on API Coverage were re-measured on this date: 2,010,030, 1,496,499, 71,880 and 13,016. For current totals call GET /us/statutes/coverage.

Not covered

State session laws are served by their own endpoints and cover the 2025 sessions only. See State Session Laws.
  • Maryland regulations: all 36 titles of COMAR, 29,433 sections, where 23 titles were held before.
  • Missouri court rules: 1,536 sections. Missouri is no longer listed as a gap.
  • Vermont court rules: 833 rules, cited Vt. R. Civ. P. 26 and Vt. R. Evid. 803, with their source link withheld. Every jurisdiction now carries court rules.
  • Federal local court rules: recounted at 6,234 rules (5,936 in force) from 52 courts in 112 rule sets. The 32 district sets cover 33 districts, because the Southern and Eastern Districts of New York share one set.
  • Professional-conduct and bar rules for California, Oregon, Virginia, the District of Columbia, Georgia, Idaho, Florida and Texas are read from the bar association’s own site. See Where bar associations supply the text.
  • Court rules: West Virginia’s lawyer and judicial disciplinary rules, Florida’s admissions rules, Montana’s Code of Judicial Conduct and Sentence Review Division Rules, and the Massachusetts juvenile and probate families under their own names (Mass. Juv. Ct. Care & Prot. Rule 5).
  • Nevada ADR rules are split by instrument: Nev. R. ADR n is now the General Provisions only, and arbitration and mediation are Nev. Arb. R. n and Nev. Med. R. n.
  • Puerto Rico: Reorganization Plan No. 2-2011 and the 1930 Civil Code (1,811 articles, all repealed).
  • Maine carries the MaineCare manual and New Hampshire the Department of Environmental Services rules.
Corpus
Federal local rules, Guam, Northern Mariana Islands

New: federal local court rules

corpusType=FEDERAL_LOCAL_RULES searches a federal court’s own rules, as distinct from the national Federal Rules of Procedure (FEDERAL_RULES). It holds 6,234 rules from 52 courts: the 13 courts of appeals, the habeas rules, six national courts (Armed Forces, Federal Claims, Tax Court, International Trade, Veterans Claims, Courts-Martial) and 32 district courts. See Federal coverage for what is held and what is not.
  • Citations such as 3d Cir. L.A.R. 26.1, Fed. Cl. R. 59, Mil. R. Evid. 803 and S.D.N.Y. Local Civ. R. 7.1 resolve through /us/statutes/resolve.
  • A bare number that does not name a court, or a district with separate civil and criminal sets that the citation does not name, is refused rather than guessed.

New: Guam and the Northern Mariana Islands

state now accepts gu and mp, which brings the jurisdictions to 54.
  • Citations such as 9 Guam Code Ann. § 16.10, 2 N. Mar. I. Code § 7222 and 165 N. Mar. I. Admin. Code § 165-30.1-101 resolve.
  • Court rules are held one rule per document, except six Guam sets and 21 Northern Mariana Islands sets that are held as one document per set, so a citation to one rule in those sets returns the whole set. See State and territory coverage.

Changed

The OpenAPI corpusType enum now carries 22 tokens, and state accepts 54 jurisdictions.
  • Nebraska: about 9,400 sections that were missing, among them the comma-numbered sections (the DUI statute 60-6,197, the State Tort Claims Act 81-8,209) and the Uniform Commercial Code.
  • Maryland court rules: 277 rules that were missing, among them the judicial-conduct rules (Title 18) and the attorney professional-conduct rules (Title 19).
  • Rhode Island: sections that were missing from 1,065 chapters, and 47 duplicate sections removed.
  • Texas: the Revised Civil Statutes (Vernon’s), 266 articles, and the missing Code of Criminal Procedure articles, among them art. 38.22.
  • Court rules: Nevada, Ohio, Mississippi and Montana gained rules a parser had dropped. Pennsylvania gained its unconsolidated acts (54 sections of 35 P.S. ch. 780), and the Pennsylvania Constitution’s Schedule is now served apart from Article V.
  • Citation resolution: about 250 more citation forms are read, including publisher abbreviations, parallel citations and each state’s own court-rule style.
Endpoint
State session law search, multi-value filters

New: search state session laws

POST /us/session-laws/search finds state session laws by what they say: a question in plain words, words from a title, a quoted phrase, a citation, a code section or a bill number. It returns the laws best first, each with the passage that matched and a snippet around your words. See Searching the text.
  • It searches the enacted text. Language an act strikes out is never searched and never appears in a snippet.
  • Ranking uses keyword relevance only, so a question has to share vocabulary with the act. Each result says how it matched (matchType, matchedBy); there is no “no good match” flag.
  • Filters: jurisdiction, session, series, instrumentType, approvedFrom, approvedTo. limit is 1 to 25 and offset plus limit reaches at most the 60 best matches.
  • An empty result is charged. A request that fails validation is a 422 and is not charged.

Changed

  • series and instrumentType on GET /us/session-laws/list now take several values (repeat the parameter; they combine with OR). A value outside the published list is a 422 and is not charged, where it used to return an empty, charged page. A cursor issued before this change still resumes.
  • The OpenAPI document now publishes the allowed values of every field that takes one value or a list (state, corpusType, source, fields, actStatus and others) on each value rather than on the field as a whole. Generated clients and the playground offer them as pickers, and a list is no longer rejected by a strict client. actStatus is now published on POST /us/statutes/count and GET /us/statutes/divisions as well.
CorpusEndpoint
State session laws

New: state session laws

State session laws as enacted, from the 2025 sessions: 20,604 acts across 50 jurisdictions, 18,704 with text. See State Session Laws.
  • GET /us/session-laws/{sessionLawId} also takes a citation in place of the id, for 2 more credits.
  • GET /us/session-laws/list requires jurisdiction and filters by session, series, instrument type, approval date and effective date.
  • Each law carries its approval date, effective dates, veto outcome, sources and, in 11 jurisdictions, the code sections it changed.
  • Laws with a known text defect are returned with textStatus: "withheld" and the reason; their text is not served.
  • POST /us/session-laws/batch returns up to 50 laws by id or citation in one call; includeBody: true adds each law’s first page of text at 6 credits per page.
  • GET /us/session-laws/changes is a cursor feed of every law served, corrected, withdrawn or merged.
  • GET /us/statutes/section/{actId}/enactments lists the session laws a publisher’s tables print against a code section, in CA, DC, HI, KY, MO, MS, NE, UT and WA.
  • POST /us/statutes/resolve recognises a state session law citation that names no code section: the response carries matchedCorpus: "session_law" and a sessionLaw block (resolved stays false, section stays null). No extra charge.
  • GET /us/statutes/coverage gains a sessionLaws block per jurisdiction: sessions with status, counts, the series and instrumentTypes held and the span of approval dates.
EndpointFix
Browse and search inside containers

New: three more corpora you can walk as a tree

GET /us/statutes/divisions now browses CONSTITUTION, STATE_CONSTITUTION and FEDERAL_RULES.
  • corpusType=CONSTITUTION lists the Preamble, the seven articles and the 27 amendments, in reading order. Pass one back as article (article=Amendment XIV) for its sections.
  • corpusType=STATE_CONSTITUTION&state=nm lists a state constitution’s articles the same way.
  • corpusType=FEDERAL_RULES lists the rule sets (FRCP, FRE, FRCrP, FRAP, FRBP, Supreme Court Rules and the FRCP supplemental rules), and code=frcp lists the rules in one. The same rule sets are also published as an appendix to the U.S. Code, and those are listed as their own sets (uscapp_t28a_fre), so no rule appears twice under one heading.
New York codes are divided by article, not chapter, and browse listed those articles without any way to open one. Passing an article back as chapter returned nothing. The new article parameter opens it: corpusType=STATE&state=ny&code=ny_jud&article=2.
Every entry in the corpusTypes legend of GET /us/statutes/coverage now carries browsable, so you can tell which corpora /divisions accepts without sending a request to find out.
A /divisions request whose filters do not fit the corpus (an unbrowsable corpusType, a missing state, a filter the corpus does not use) is now rejected with 422 before any credit is taken. These used to be charged and refunded in the same call, which cost nothing but left a charge and a refund on your ledger for each one. A filter naming a container that does not exist is still refunded, as before.
corpusType=CFR&titleNumber=17&chapter=II&part=240 used to be rejected because CFR browse is organized by part. With a part, chapter is now accepted and ignored, since part numbers are unique within a title, and the response says so in note. Without a part, it is still a 422, because a chapter cannot narrow a title’s part list.
Every browsable corpus can now be searched inside a container. POST /us/statutes/search takes a new article filter, and code takes a federal rule set.
  • {"corpusType": "CONSTITUTION", "article": "Amendment XIV"} searches the Fourteenth Amendment.
  • {"corpusType": "STATE_CONSTITUTION", "state": "nm", "article": "Article IV"} searches one article of a state constitution.
  • {"corpusType": "STATE", "state": "ny", "code": "ny_jud", "article": "2"} searches one article of a New York code.
  • {"corpusType": "FEDERAL_RULES", "code": "frcp"} searches the Federal Rules of Civil Procedure, and code=uscapp_t28a_fre the Federal Rules of Evidence as the U.S. Code appendix prints them. source=frcp still covers the FRCP together with its supplemental rules; code is the finer scope.
Search results from these corpora now carry a parent too, with article or the rule-set code, so a hit can be spread straight back into a search or a browse of its container. POST /us/statutes/count takes the same article and rule-set code. A shape that cannot be answered (an article without a matching corpusType, a state constitution without state, a New York article without its code) is a 422 before anything is charged. See Search within a container.
code compared the lowercase id that /divisions hands out against the publisher’s own casing, so a code the publisher stores in upper or mixed case matched nothing. code=ny_jud returned no results because New York stores JUD, and code=ca_pen none because California stores PEN. 1,591 of the 8,929 state statute and regulation codes were affected on search and on /count, including every New York code and California’s statute codes. Codes now match however the publisher cases them; codes stored in lowercase, such as Texas’s, return exactly what they did before.
POST /us/statutes/search already refused a titleNumber without corpusType USC or CFR, and a chapter or part without its container, but only after charging and refunding. Both are now 422 before any credit is taken. POST /us/statutes/count now applies the same rules: {"titleNumber": 28} used to count title 28 of every corpus that numbers its titles, including the appendix court rules and state codes, and is now refused with the same message search gives.
GET /us/statutes/coverage used to publish its 200 response as an empty schema, so generated clients and MCP tools got no field types for it. It now publishes the full shape of data and meta. The response itself is unchanged, byte for byte. Its description no longer mentions freshness or currency, which the response stopped carrying on 2026-09-08; for the age of a source, read GET /boards, and for what a section is current through, read currentThrough on the section.
Endpoint
Scope counting, batch full text, truncated listings

New: size a scope before you walk it

POST /us/statutes/count takes the scoping filters and returns an exact section count. No query, no ranking, 1 credit, and a scope that matches nothing is refunded.Use it to size a job before building a corpus. Texas regulations are 43,638 sections; 26 TAC chapter 554 is 279. Count the scope, enumerate it with /divisions, then rank within it with /search.It counts SECTIONS. Long sections are stored as several passages and are counted once.
POST /us/statutes/sections now accepts includeBody. Each section comes back with its text on body instead of metadata only.Priced from the ordinary body rate per row that returns text, so it saves a round trip but not credits, and rows whose text cannot be resolved come back null and are not charged. Read creditsConsumed rather than computing it.
A search with changedSince set returns changedSectionCount: how many sections changed in that window, before ranking.Compare it against count. changedSince filters a RANKED search, so a window holding more sections than one query can return is normal, and what you get back is the most relevant slice rather than the whole window. When the number is larger than you can page to, treat the filter as a trigger and take the inventory from a board watch, which is complete and costs no credits.
GET /us/statutes/divisions now returns truncated, and nextCursor alongside it. The level that lists sections walks a bounded number of points; a container past that bound used to return a short list with nothing saying so, and no way to reach the rest.Check truncated before treating a listing as complete. When it is true, pass nextCursor back as cursor and keep going until it comes back null. California’s 22 CCR walks to 11,602 sections across two pages, which matches the parent’s own sectionCount.Rows are sorted into statutory order within a response and pages are walked in storage order, so sort the union yourself once you hold every page.The same endpoint now accepts excludeRepealed and actStatus, so you can enumerate only operative law instead of filtering after you have paid to fetch it.
renumberedTo and transferredTo are raw publisher pointers (self:4651), not identifiers of ours, and passing one to a section endpoint is a 404. They now come with renumberedToLabel and transferredToLabel, the same pointer written out (section 10105 of Title 34), and their descriptions state that the raw form is not an actId.
Corpus
Colorado court rules

New: STATE_RULES for Colorado

1,194 rules, 58,447 sections across 50 jurisdictions. Colorado is the one jurisdiction here whose court rules are not a single consolidated fetch.Colorado’s Office of Legislative Legal Services stopped publishing after the 2023 edition and now routes current court-rules access to a paid commercial product. The Supreme Court, separately, publishes every adopted rule change as a free order carrying the amended text. So the 2023 volume is the base and every adopted order issued after it is applied forward on top.Per rule, readable from the response:
  • 180 rules carry an amendment adopted in 2024 to 2026.
  • 958 rules have not been touched by any adopted order since the compilation, so their 2023 text is the current law. The order series is contiguous with no gaps, so that statement can be checked.
  • 45 rules could not be updated automatically. They serve their 2023 text and say so in sourceNote, naming the order, its adoption date and its effective date. Read that field before relying on one of these.
  • 11 rules are suspended, not in force. The Colorado Rules of ICWA Procedure (Chapter 28.3) were adopted effective 2024-01-01 and suspended by the Supreme Court on 2025-11-06. They carry actStatus=suspended and are served for reference.
Coverage spans Chapters 1 to 38: civil, criminal, appellate, juvenile, probate and county-court procedure, evidence, professional conduct, judicial conduct and discipline, magistrates, water courts and public access to records. The statewide Practice Standards under C.R.C.P. 121 are addressable individually, cited as C.R.C.P. 121 § 1-15.Per-jurisdiction counts and the full note are on state coverage.
Corpus
State Attorney General opinions, September 8 to 12

New: STATE_AG_OPINION, September 8 to 12

A new corpusType: a formal written opinion in which a state’s chief legal officer construes that state’s own statutes, constitution and regulations for a state officer, legislator or local government who asked. It is often the only interpretive authority for a provision no court has reached. It rolled out jurisdiction by jurisdiction, like STATE_AGENCY_GUIDANCE.
Persuasive authority, not binding law. Every section in this corpus is served with goodLawStatus: "unknown", in every jurisdiction. Only three of the 52 jurisdictions publish any supersession signal at all, so we do not certify that an opinion still stands. Read it as “we make no claim”, not as “probably still current”. See Status and currency.
The per-state table, with each jurisdiction’s scope limit, is on state coverage. Counts in the table are the totals on each date. Where a jurisdiction runs more than one series, the series field carries the publisher’s own label, so Washington’s formal AGO and its AGLO letter opinions, and Georgia’s Official and Unofficial, filter apart. series is also part of the actId.
  • Montana, 3,527 opinions, volumes 15 to 44. These carry no issue date. Montana publishes by volume and prints no date on an opinion, so unlike every other jurisdiction here they do not answer an asOf query. They are reachable by citation, volume and search. Volumes 1 to 14 are excluded: the leading number on those is a page in the bound volume, not an opinion number, so there is nothing stable to cite them by.
  • North Carolina, 1,106 opinions, 1976-2010. The state prints no opinion number, so these are keyed on issue date plus the official who asked.
Montana, previously excluded, is now held. Documents on the one host whose operator restricts access remain excluded and are not held.At the time, corpus-wide coverage was 5,095,028 sections across 53 jurisdictions, indexed as 19,288,724 retrieval passages. For current figures call GET /us/statutes/coverage.
Ohio, 1,406 opinions, 1993 to 2026, is live with state=oh. The count is the total the Attorney General’s own index prints, and every one of those opinions is held.
  • The modern era only. Ohio’s archive reaches back to 1846. The 33,659 opinions of 1920 to 1992 are book scans the state does publish, and they are not yet held.
  • No issue date. Ohio prints a year for each opinion and no day, so these carry a year and do not answer an asOf query.
  • 1846 to 1919 is not held. That era is 73 bound year-volumes whose opinions the state says were not numbered, or not numbered sequentially, so there is no citable identifier for them.
  • Overruled opinions. Ohio publishes a list of overruled opinions. It names 47 of the 1,406 opinions held, of which 20 are dead. That list is not yet applied to goodLawStatus.
Seven jurisdictions are added, bringing the corpus to 68,874 opinions across 34 jurisdictions. All seven are subscribable as change-alert boards.
  • Alabama, 11,928 opinions, 1979 to present. The state’s own archive begins in 1979. Earlier opinions exist but Alabama does not publish them itself, so they are a stated coverage limit.
  • West Virginia, 151 opinions, 2007-2026. The state prints no opinion number, so these are cited by date and requester surname.
  • Texas, 2,914 opinions, 1983-2026. The seven post-1983 series only. Roughly 14,800 earlier opinions sit behind paths the state restricts access to, so we do not hold them.
  • Massachusetts, 529 opinions, 1968-1993, split out of the Attorney General’s annual reports. Only that era carries citable opinion numbers.
  • Mississippi, 520 opinions, 2020-2026. The state’s pre-2020 opinion database is no longer published anywhere by the state.
  • Nevada, 41 opinions, 2017-2026, the modern per-opinion era only. The bound annual compendia are not yet split into individual opinions.
  • District of Columbia, 37 opinions, 1982-2026, formal opinions only. Advisory Neighborhood Commission letters are a different instrument and are excluded.
Three of these publish no opinion number at all. West Virginia, Mississippi and the District of Columbia identify an opinion by its issue date, and where a date carries more than one, by the official who asked. Those identifiers are ours, derived from what the publisher prints.At the time, corpus-wide coverage was 5,089,670 sections across 53 jurisdictions, indexed as 19,239,374 retrieval passages, measured 2026-09-11.

Counts corrected on the coverage tables

Four published figures had gone stale against the live corpus and were restated: Statutes at Large 425,427, CFR 222,333, agency guidance 96,785 across 53 named sources, and state agency guidance 13,350. The agency guidance source page previously showed a total that did not match its own table. It states the named-source total, 51,427, with the corpus-type total kept on the federal page, because the token also covers guidance that carries no filterable source.
Twenty-two jurisdictions are added at once, bringing the corpus to 52,754 opinions across 27 jurisdictions. The larger additions: Missouri 8,449, North Dakota 5,550, Washington 4,428, Tennessee 2,650, California 1,961, South Dakota 1,652, Illinois 1,451 and Nebraska 1,191.Four scope limits, each recorded on the coverage page:
  • Missouri runs 1962 to present. The 1933-1961 era is not served: the number printed on those opinions is a requester-alphabetical folder position, not a document identifier, so there is nothing stable to cite them by.
  • Maine serves its numbered era, 832 opinions. The earlier material carries no opinion number in the state’s own archive and is not served for the same reason.
  • Pennsylvania, 653 opinions, is split out of bound volumes. Its 1895-1930 volumes print no per-opinion number and are not served.
  • Illinois is served from our own OCR. Roughly 1,450 of its 1,456 opinions are scans with no text layer at all, so the text you get is machine-read from the state’s page images and gated for readability before it is served. Anything that failed that gate is excluded and counted, not served degraded.
California moved to the corpus-wide identifier scheme. Its 23 legacy CA_AG_OP_* identifiers are retired and the jurisdiction is re-served complete at 1,961 opinions under AGOP_CA_*, with four series (OP, CV, CR, SO) filterable on series. If you stored a CA_AG_OP_ identifier, re-resolve it by citation.
Arkansas (10,295), Indiana (9,759), Idaho (151) and Oklahoma (68) are live, adding 20,273 opinions. Arkansas and Indiana are now the two deepest jurisdictions in this corpus.
  • Arkansas lists 334 further opinions its own index carries a row for and whose document it has never published. Those are recorded as a coverage limit, not counted, so 10,295 is what we hold. They cluster in 1985-1998.
  • Indiana reaches back to 1906 and publishes in two citation forms, both carried as the state prints them: numbered opinions from 1944, and page cites into the annual and biennial report volumes before that. In the scanned eras Indiana cut its bound volumes into per-opinion PDFs by page, so an opinion running past its page cut is severed in the state’s own file. We serve everything Indiana publishes, but for those the text is the opening pages. The 1960s, 1970s and 2000 onward are unaffected. Every Indiana opinion also carries the statutes it construes, the Attorney General who signed it, and the state’s own summary.
  • Idaho is opinions only. The Guidelines, Certificates of Review, Annual Reports and Tables of Citations that share its feed are a different instrument and are not here. Pre-1985 opinions exist only inside annual report volumes.
  • Oklahoma is 2023 onward. Its older opinions are published on a network whose publisher restricts access, so we do not hold them.
Delaware, 843 opinions, 1995-2026.
  • Delaware runs one numbered series and does not separate its opinion types. Only about 17 of the numbered items are substantive Attorney General opinions; the rest are FOIA opinion letters interleaved in the same numbering. Both are formal opinions of the Attorney General under Delaware law, so both are here.
  • 173 of the 843 are the state’s letter recovered from a reporter print. Delaware publishes those posts in a commercial reporter’s rendering. The opinion underneath is a government work, so we remove that publisher’s citation and page marks and serve the letter itself. 150 of the 173 exist in no other form in Delaware’s archive and span 1995-2011.
  • 50 further posts carry no opinion number and are excluded: press releases, job postings and notices sharing the same archive.
Corpus
FTC HSR interpretations and advocacy filings

New: FTC HSR interpretations and advocacy filings

Two new source codes under corpusType=AGENCY_GUIDANCE, both from ftc.gov.
  • ftc_hsr_interpretation: 4,589 documents, 1978-2025. The Hart-Scott-Rodino premerger notification interpretations, both halves under one code. The 20 formal interpretations are the Commission’s own authoritative construction of a Premerger Notification Rule under 16 C.F.R. 803.30, a closed series issued 1978 to 2000. The 4,569 informal interpretations are the Premerger Notification Office answering a practitioner’s question about the same rules. Filter the two apart with documentSubtype, and join them on the new construedRule field, which carries the rule number on 99.0% of documents, with respondingStaff naming who answered on 99.4%.
  • ftc_advocacy_filing: 860 documents, 1985-2026. Comments and letters the Commission and its staff address to state legislatures, state supreme courts, governors and other federal agencies on the competition effects of a proposed measure. They have their own forum (ftc_advocacy) so they can be scoped out in one parameter.
goodLawStatus is unknown on both. See Status and currency.
  • Weight: an informal interpretation is staff views, not Commission action, and is not binding on the Commission. Advocacy filings bind nobody: they decide no case, construe no FTC rule, and the recipient is free to ignore them. Every document says so in its own coverageNote.
  • 1997 gap: the FTC serves no HSR informal interpretation from 1997 at all, against 141 in 1996 and 83 in 1998, so roughly 100 to 140 interpretations from that year are missing from the source, not from this corpus.
  • Dates: the Commission publishes no date field for the formal series, so effectiveDate is absent on 13 of those 20 documents rather than guessed. They print dates only inside their own argument, where the document’s own date cannot be told apart from the dates it cites.
  • Supersession: the Commission states a supersession in one formal interpretation’s identifier and publishes three dated versions of another. Those relations are served as supersedes and supersededBy, and no document is marked dead on the strength of them.
Corpus
NLRB Board decisions, full archive

Changed: NLRB Board decisions widen to the full archive

The NLRB slice was a 15-year window of 2,762 decisions. It is now the full published archive: 66,597 decisions, 1935-12-30 to date, under source=nlrb_board_decision. That is 24x the previous coverage, and 1,705,304 retrievable passages.
  • What it holds: the Board’s entire body of unfair-labour-practice and representation decisions, the ones that bind later Board panels and the administrative law judges beneath them.
  • Count: the publisher’s own. The volume listing enumerates 66,600 decisions across volumes 0 to 375, and 66,597 are served.
  • Citation forms: both are served and neither is normalized into the other: NNN NLRB No. N while a decision is a slip opinion, NNN NLRB NNNN once the bound volume closes and assigns it a page. Across the full archive the balance shifts toward the bound form, because most of the archive is closed volumes.
  • Totals: corpusType=AGENCY_ADJUDICATION now serves 100,920 sections across its seven bodies, up from 37,085.
goodLawStatus is unknown on every decision. See Status and currency.
  • Why currency is not asserted: the Board publishes no overruling or supersession signal, and its CITENET Classified Index is a subject digest rather than a citator, with no reverse edge from an overruled decision to the one that overruled it. A decision is served as issued, and the older it is, the more that matters, because Board doctrine moves with Board composition. Each point carries a coverageNote saying so.
  • Two decisions are excluded: 227 NLRB 427, where the publisher’s PDF contains only the case caption and no body (two independent extractors agree), and 321 NLRB 10, a file no OCR engine will accept. Both are re-tried if the Board re-issues them.
Corpus
IRS written determinations, not precedent

New: IRS written determinations under AGENCY_GUIDANCE

corpusType=AGENCY_GUIDANCE now also covers IRS written determinations released under 26 U.S.C. § 6110 (source=irs_written_determination), coverage 1999-01-08 to 2026-09-04 across 28 distinct years. The IRS lists 45,431 determinations and 45,358 are ingested (99.84%). 35,485 are reachable through the API (78.1%). The other 9,873 are OCR-read scans and are not currently served. See Agency guidance coverage for the served count.
A written determination binds one taxpayer and may not be cited as precedent. 26 U.S.C. § 6110(k)(3) provides that it “may not be used or cited as precedent”. Every one therefore carries actStatus: "non_precedential" rather than in_force, and says so again in currencyNote. Read one as evidence of how the Service analysed one taxpayer’s facts, never as a rule of general application.
  • Fields from the IRS: each carries the publisher’s own Number, UILC code list, Subject and Release Date, so effectiveDate, effectiveYear and the UILC issue codes come from the IRS rather than from inference.
  • Currency: goodLawStatus is unknown. See Status and currency.
  • Held: the 45,358 ingested documents hold 402,546 retrieval passages and break down as 28,641 Private Letter Rulings, 5,573 Chief Counsel Advice memoranda, 5,482 Tax Exempt and Government Entities determination letters and 842 Technical Advice Memoranda, plus 4,820 the IRS does not type on the document itself. This makes it the largest source in the token by documents held.
  • OCR: the IRS publishes much of this series as scans of signed paper rather than as typeset text. Documents read by OCR carry extractionMethod: "ocr" and the rest carry "text_layer". The section symbol survives scanning less reliably than the words around it, so a passage may read section 501(c)(3) where the page prints § 501(c)(3), so search for either form. A stamped control number in a letterhead can lose a digit, which is why actId and citation are taken from the IRS index rather than from the scanned text.
  • Not served: 73 determinations are withheld: 56 are scans no OCR could read, 14 failed a legibility check, and 3 are not PDFs at the publisher’s end. A document that could not be read is withheld rather than served as fragments.
CorpusEndpoint
Coverage total and filterable corpus types

New: every counted corpus type is filterable

Checked against the deployed OpenAPI document on 2026-09-07: the published corpusType enum carries all 19 tokens, CFR_ANNUAL, FEDERAL_REGISTER_NOTICE, STATUTE_COMPILATION and AGENCY_ADJUDICATION among them. Every corpus that /us/statutes/coverage counts can be used as a search scope. The six per-body source values are live in the same document: nlrb_board_decision, sec_commission_opinion, bia_precedent, ag_precedent, cfpb_enforcement_action and irs_irm.

Changed: coverage at 4,983,685 sections on this date

Counts are on the definition GET /us/statutes/coverage publishes as sectionCount, across all 52 jurisdictions. For current figures call that endpoint.Two counting units are used, and they are not interchangeable. A section is one provision or document, which is what sectionCount reports. A retrieval passage is one indexed chunk, and a long document has many. The CFR annual editions enter the total at their section count, 312,132, not at their stored versions, because these are editions over time of the same regulations, not additional distinct ones.
  • Federal Register notices are 17,616 of the 766,073 published in the period, 2.30%, four operative classes by design. That is not notice coverage and is never described as such.
  • The Internal Revenue Manual is agency procedure, not law. It is the IRS’s own instruction manual for its employees and does not bind the agency against a taxpayer.
  • The adjudication corpora (FTC Part 3, NLRB, MSPB, BIA, SEC, OLC, CFPB) carry no verified doctrinal currency. goodLawStatus is unknown on all but the CFPB slice, and a live corpusType=AGENCY_ADJUDICATION search returns nlrb_board_decision hits with goodLawStatus: "unknown", which is the intended answer and not a gap.
  • Statutes at Large is law as enacted. It carries goodLawStatus: "unknown" and is a historical record rather than a statement of current law; for what the law says today, use corpusType=USC.
Corpus
CMS Medicare Internet-Only Manuals

New: CMS Medicare Internet-Only Manuals under AGENCY_GUIDANCE

source=cms_iom: 11,018 sections across 21 publications, 26,153 retrieval passages, addressed at CMS’s own section numbering and cited Medicare Claims Processing Manual (Pub. 100-04), Ch. 12 SS 20.1. Pub. 100-04 says what a provider may bill and how, Pub. 100-02 says what Medicare covers, and Pub. 100-08 is what a MAC reads before it opens an audit.
  • Revision stamps: CMS prints (Rev. N, Issued, Effective, Implementation) on each revised section, so amendmentYears, lastAmendedYear, effectiveDate and transmittalNumber come from the publisher rather than from inference. 98.4% of sections carry at least one stamp, spanning 2000 to 2026 across 27 distinct years.
  • New field: GET /us/statutes/coverage returns sourceScopeNotes on each corpusTypes entry, keyed by the source value you can filter on. It carries a per-source declaration for a token that fans out to many unrelated sources, where the whole-token scopeNote cannot describe any one of them.
  • asOf: CMS replaces manual chapters in place and publishes no superseded editions, so asOf is not bounded for this corpus and every passage states the date we captured it.
These manuals are agency procedure, not law. They instruct CMS’s own Medicare administrative contractors on how to administer the program. Courts have repeatedly held that manual provisions are not binding substantive rules; the binding requirements are in the Social Security Act and 42 C.F.R. Do not read a billing instruction here as a regulation.
goodLawStatus is unknown on all of them, and every passage carries the statement above in currencyNote. See Status and currency.
Five of CMS’s 25 publications hold nothing or almost nothing. These are gaps at the publisher. Pub. 100-12 (State Medicaid Manual), 100-13 (Medicaid CHIP) and 100-23 (Payment Error Rate Measurement) publish no chapters at all; 100-21 is titled Reserved; and 100-18, the Medicare Prescription Drug Benefit (Part D) Manual, is a two-page table of contents whose own text states that several chapters “have not been disseminated via HPMS or Pub. 100-18”. Pub. 100-14 does not exist.
Corpus
FTC Part 3 administrative filings

New: FTC Part 3 administrative filings under AGENCY_ADJUDICATION

source=ftc_administrative_decision: 18,023 documents from the Federal Trade Commission’s Part 3 adjudicative docket, 1995 to date. It holds the Section 5 doctrine on unfair and deceptive acts and unfair methods of competition: administrative complaints, initial decisions, Commission opinions, consent agreements and the orders that modify them, across the Franchise Rule, the Telemarketing Sales Rule, COPPA, Made in USA, HSR and the Safeguards Rule. Cited by docket (FTC Docket 9436) where the record prints one, and always by the Commission’s permanent File Number in caseNumber.
  • The unit is a filing, not a decision. A Part 3 docket is mostly documents written by the parties: measured on the corpus, 21% of passages are the operative instruments (complaints, decisions and orders, consent agreements) and the rest are motions, notices of appearance, exhibits and public-comment analyses. The whole docket is served; nothing is dropped on that basis.
  • Labels not exposed yet: each filing is stored with the Commission’s own label (“Complaint”, “Decision and Order”, “Agreement Containing Consent Order”) and a normalised class. Neither is a response field or a search filter yet, so a retrieval returns operative and procedural filings together.
  • Scope: the Part 3 administrative body only. The FTC’s 2,039 federal-court records and about 2,636 records carrying neither action type are not held, and FTC rules are served under corpusType=CFR because they are codified at 16 C.F.R. The FTC’s ADVISORY opinions decide no case and remain under corpusType=AGENCY_GUIDANCE.
  • Record-type fields: caseStatus and docketNumber are record-type dependent (88.2% and 73.6% respectively), not extraction gaps.
goodLawStatus is unknown on every filing. See Status and currency.
Corpus
OFAC FAQs and their prior versions

New: OFAC Frequently Asked Questions, and their revision history

source=ofac_faq under corpusType=AGENCY_GUIDANCE. 989 current FAQs, cited OFAC FAQ 401, covering all 38 sanctions programs the Office of Foreign Assets Control administers. This is the interpretive layer over 31 C.F.R. chapter V: how the 50 Percent Rule reaches through an ownership chain (FAQ 401), whether a non-U.S. person is exposed for a transaction a General License authorizes (FAQ 1247), whether an institution may wait for its screening vendor’s overnight report (FAQ 43). None of it is in the CFR.
361 prior versions are served as their own citable documents with actStatus: "superseded", taken from OFAC’s own FAQ Archive and stamped with the publisher’s timestamps, so the earlier text is retrievable. A superseded version never competes with the current answer in search; ask for it by act_id.238 FAQs (24.1%) carry at least one observed revision; the deepest is FAQ 999 with 12. A version whose text is byte-identical to the one before it is not counted as a revision. OFAC re-saves FAQs without changing them, and 183 of its 1,533 archive rows are exactly that.
The revision trail begins 2023-03-22 and goes no further back. OFAC migrated its FAQs to a new website that day and states that FAQs active at the time display the migration date rather than the date it first published that version. Those 860 version records carry observedDate and no effectiveDate, because that date is when we observed the text and not when OFAC published it.279 FAQ numbers have been rescinded and OFAC publishes nothing for them: no text, no date, no reason. A rescinded FAQ is absent from this corpus and not marked withdrawn, so a gap in the numbering is a rescission and not a gap in our coverage. Both bounds are in currencyNote and coverageNote on every passage.
GET /us/statutes/section/{act_id}/body?asOf=2026-04-01 returns the version OFAC published on that date, verbatim, with asOf.source = stored_edition. There is no diff walk and no basisChangeId: the earlier text is a document we hold, so we serve it as stored.Three answers are distinguished:In the last row, isBounded: true means the text is the earliest we hold and not the text in force on your date. Presenting it as point-in-time law claims more than the API does. isBounded has a different meaning on the stored_edition engine used by CFR_ANNUAL; check engine first.Sanctions lists (SDN, consolidated) and General Licenses are not included. General License links are served as cross-references.
Corpus
FinCEN AML Act material

New: FinCEN Anti-Money Laundering Act of 2020 implementation material

source=fincen_amla_material adds 13 documents across 159 retrieval passages: the AML/CFT National Priorities and the interagency statements issued with them, the Arts and Antiquities notice, threat-pattern and trend reports, the Section 6305 Report to Congress on no-action letters, the whistleblower bulletin, and the AML/CFT program NPRM fact sheets. Cited as FinCEN, Statement for Banks (AML Act of 2020 Sec. 6101, June 30, 2021).The AML Act rulemakings themselves are not duplicated here. The NPRMs and final rules implementing each section are Federal Register documents and are already served under corpusType=FEDERAL_REGISTER. This source carries only FinCEN’s own standalone publications.Completes the FinCEN Corporate Transparency Act and AML Act batch begun in the previous entry.
Corpus
State financial-institutions bulletins

New: state financial-institutions regulator bulletins (Arizona, Oregon, New Jersey and Vermont)

STATE_AGENCY_GUIDANCE now has two named sources and takes a source filter:155 new documents across 584 retrieval passages, from four regulators that each share an index with their state’s insurance regulator: New Jersey DOBI banking (81), Arizona DIFI (35, covering banks, credit unions, trust companies, escrow agents, consumer lenders, money transmitters, loan originators, collection agencies and sales finance), Vermont DFR banking and securities (29), and Oregon DFR financial services (10, covering investment advisers, collection agencies and pawnbrokers, student loan servicers, income share agreements and debt management).New Jersey and Vermont show how the scope was drawn. DOBI runs one numbered series across insurance, banking and the Real Estate Commission; the real-estate bulletins are in neither corpus, because licensing brokers is neither insurance nor a financial institution. Vermont runs a separate series per division, so Banking Bulletin #50 and Insurance Bulletin #50 are different documents and each carries its series in its identifier.Nothing you already query changes. Existing insurance-bulletin results keep their citations, their actId values and their counts, and a search with no source filter now spans both. A search for insurance guidance will never be handed a credit-union bulletin: the two are separate categories, and each document’s source says which it is.This is not coverage of state banking law. These four states are served because their banking regulator is combined with their insurance regulator and publishes both series on one index, under numbers we can cite. Most states’ financial regulators publish no numbered series at all, so source=state_financial_bulletin returns nothing for any other state and no wider rollout is planned.state_financial_bulletin is served goodLawStatus: "unknown". Neither the Arizona nor the Oregon regulator has rescinded anything we hold (0 of 35 in Arizona, 0 of 10 in Oregon), so there is no measured rescission signal to certify against. Arizona’s insurance bulletins keep good_law on their own signal, which is 15 of 199 marked (same state and corpusType, different publishers). Read unknown as “we make no claim”, not as “probably still current”.Every document carries an issuedDate from the publisher’s own index, and both sources refresh weekly alongside the rest of the state-guidance registry.
Corpus
FinCEN beneficial-ownership guidance

New: FinCEN Corporate Transparency Act beneficial-ownership guidance

Three new AGENCY_GUIDANCE sources, 145 documents across 220 retrieval passages, all from fincen.gov:This takes AGENCY_GUIDANCE to 40 named sources, 23,921 documents.Two of the three predate the current rule, and we serve them anyway, labeled. On August 11, 2026 FinCEN issued a final rule that permanently narrowed BOI reporting: entities created in the United States and their beneficial owners are exempt, and only certain companies formed under foreign law and registered to do business in a US State or tribal jurisdiction still report. The FAQs (issued 2023-2024) and the compliance guide (March 2025) both predate it, and FinCEN’s own pages say some of their content is outdated.We do not drop them, because they remain the authoritative FinCEN text and much of it is untouched by the scope change: the beneficial-owner and substantial-control definitions in FAQ category D read the same either way. Instead, every passage from these sources carries FinCEN’s own notice verbatim in currencyNote, with currencyYear: 2026. Disregard any statement in them that US companies or their beneficial owners must report BOI, that BOI must be reported for US persons, that US persons must update or correct FinCEN ID information, or that reports were due before April 25, 2025.For the current position, use source=fincen_boi_rule_qa. The 12 final-rule Q&As are current. The 10 interim-rule Q&As are served with actStatus: "superseded" and are excluded from good-law retrieval, because FinCEN’s own final-rule Q&A states the final rule adopted the interim changes permanently.These sources are not offered as a change-alert board; they refresh weekly with the rest of the agency-guidance registry.
Corpus
CFR annual editions

New: CFR annual editions, 1996 to 2026

corpusType=CFR_ANNUAL covers GPO’s officially published annual editions of the Code of Federal Regulations: 31 editions across all 49 titles. The corpus is indexed and counted by /us/statutes/coverage; the corpusType filter itself ships with the next API deploy.The headline number counts section versions, not sections. A section is stored once per distinct run of text, not once per edition. A section whose wording never changed between 1996 and 2026 is ONE record whose editionsObserved lists every year it was observed in, rather than thirty-one near-identical copies.editionsObserved is an enumeration, never a range. A version observed in 1998, 1999 and 2003 lists exactly those three years. It does not imply 2000 to 2002, and a date falling in an unobserved gap is answered with asOf.isBounded: false rather than served from the nearest year we happen to hold.Citation years are each volume’s own <REVISED> year, not the folder GPO filed it under. GPO reprints unchanged volumes into later folders without re-dating them, so only the date inside the volume is authoritative. That is why 167 versions in title 26 (parts 502, 503 and 509) carry 1990 while sitting in the 1997 folder.This corpus is not offered as a change-alert board. The existing cfr board already carries the daily change signal for the same regulations, so a second board would fire once a year on a whole edition and repeat what subscribers had already been told the day each change happened.CFR_ANNUAL and the asOf parameter are both point-in-time routes and are not interchangeable. The corpus serves an edition as published; asOf=YYYY-MM-DD on GET /us/statutes/section/{actId}/body reconstructs a section from observed change history against the current CFR.
Corpus
Federal Register notices corpus type

New: FEDERAL_REGISTER_NOTICE, and what it does not hold

Federal Register notices, 1994 to present, under the new corpusType=FEDERAL_REGISTER_NOTICE. 17,612 documents, 128,564 retrieval passages.This is a curated slice, not the notice series. The Federal Register published 766,073 notices in this period and we hold 2.3% of them.What is held is the four classes of notice that act on a rulemaking:
  • withdrawal of a proposed rule,
  • extension or reopening of a comment period,
  • publication of significant agency guidance,
  • announcement of negotiated rulemaking.
Every point names the rule that admitted it in frNoticeClass, so the scope is readable from the data rather than only from this page.What is not held is everything else, which is mostly Paperwork Reduction Act information collections, meeting notices, permits and applications, antidumping proceedings and Privacy Act system-of-records notices. None of those states or changes a legal obligation. The other 748,461 documents in the period are not held.This is a separate token from FEDERAL_REGISTER. Rules and proposed rules are held whole, and a partial-scope statement would be wrong for the 5.5M points that are not partial.Notices carry an empty CFR cross-reference graph. crossReferencesCfr and frTopics are 0% and frRegulationIdNumbers is 2%, against 100% and 94% on rules, so a notice is not reachable by a CFR-citation filter. frDocketIds, at 73.5%, is the join key that works.amendmentYears is empty by design and goodLawStatus is unknown: a notice amends nothing, and the publisher prints no amendment credit for one, so there is no claim to make either way.The token takes no source filter. It has one internal source, so the value would be an exact synonym for the corpusType itself.
Corpus
NLRB Board decisions, 15-year window

New: NLRB Board decisions under AGENCY_ADJUDICATION

The unfair-labor-practice and representation cases decided by the five-member National Labor Relations Board itself, which bind later Board panels and the administrative law judges beneath them. 2,762 decisions, 2012 to date, under source=nlrb_board_decision. This was a bounded 15-year window of a 90-year, 66,612-decision archive. A full backfill was planned that day and shipped on 2026-09-07.
  • Two citation forms, both served, neither normalized into the other. A Board decision is cited NNN NLRB No. N as a slip opinion and NNN NLRB NNN once the bound volume closes and assigns it a page. These are different identifiers, not variants, because the page number does not exist until the volume closes: 57.45% carry a slipOpinionNumber and 42.55% a pageNumber, which shows where a decision is in its lifecycle. 56.07% carry the Board’s own notice that the opinion “is subject to formal revision before publication in the bound volumes”.
  • Fields: every decision carries caseName, caseNumber (the Board’s own docket, for example 28-CA-230115), volume and issuedDate at 100%, plus the source PDF and extracted text.
  • Out of scope: unpublished Board decisions are summary dispositions with no independent precedential value and are published as a separate series.
goodLawStatus is unknown on every decision. See Status and currency.
Board doctrine shifts with Board composition, and the NLRB publishes no overruling or supersession signal for its decisions. Its CITENET Classified Index is a subject digest rather than a citator: it records an overruling only as editorial prose on the decision doing the overruling, with no reverse edge on the decision that was overruled. No decision in the corpus carries a dead status. Every decision is served as the Board issued it, with a coverageNote stating the limit.
Corpus
SEC Commission opinions

New: SEC Commission opinions under AGENCY_ADJUDICATION

The Securities and Exchange Commission’s own adjudicated rulings: appeals from an administrative law judge, review of a self-regulatory organization’s disciplinary action (FINRA, an exchange), and applications for review. 5,790 documents, 1996-04-05 to 2026-09-01, under source=sec_commission_opinion. These bind the Commission’s own later adjudications and the ALJs beneath it. Cited by release number: Exchange Act Release No. 34-106254. One action issued under several securities statutes at once carries every release number it was given in citableAs.
  • File-Number proceeding graph: every document carries its Administrative Proceeding File Number in fileNumber (99.6%; 112 documents name more than one, because the Commission consolidates proceedings). Documents sharing a File Number are one proceeding and are linked in date order through supersedes and supersededBy: 2,353 proceedings, 65.4% of them holding more than one document, 3,641 links across 86.7% of the series.
  • Links are a sequence, not a currency verdict. No SEC document is served with a dead actStatus because of one.
goodLawStatus is unknown for the series. See Status and currency.
Corpus
BIA and Attorney General precedent decisions

New: the I&N Dec. reporter under AGENCY_ADJUDICATION

The Board of Immigration Appeals’ published precedent decisions, the Attorney General’s decisions reviewing the Board, and the legacy INS and USCIS administrative decisions the same reporter carries. 3,292 decisions across volumes 8 to 30, 1958 to 2026. A published Board decision binds every immigration judge and every DHS officer nationwide under 8 C.F.R. 1003.1(g) unless and until it is overruled. This is the body of immigration law between the statute and the circuit courts.Three sources under the existing token, filterable with source:
  • decidedBy: carries the deciding authority verbatim as EOIR prints it, across 37 distinct authorities, and a decision the Board decided and the Attorney General then reviewed carries both.
  • Overruling graph: the Board states its own effect on earlier decisions in the holdings prose beside each entry. 343 of those statements resolve into supersedes and supersededBy links, with the publisher’s own verb in dispositionVerb and the sentence itself in history. overruled_in_part is stored distinctly and does not carry a dead actStatus. 70 decisions are served dead on this evidence; the corpus as a whole stays goodLawStatus: "unknown". See Status and currency.
  • Volumes 1 to 7 are not published on EOIR’s precedent page.
  • Holdings prose begins at volume 19, so an overruling of a pre-1984 decision by a pre-1984 decision is invisible.
  • A court of appeals can reject a precedent for its own circuit while it remains in force elsewhere, and EOIR publishes nothing about that.
  • Unpublished single-member Board orders are not precedent and are out of scope.
  • Every point states these in its own coverageNote.
Corpus
CFPB compliance guidance

New: CFPB compliance guidance under AGENCY_GUIDANCE

The other half of the Bureau’s output, alongside the enforcement actions in the next entry. 111 documents across two new sources:
  • cfpb_circular (16): Consumer Financial Protection Circulars, cited Circular 2023-01. They state how the Bureau reads a statute, for enforcers and firms alike.
  • cfpb_supervisory_guidance (95): bulletins, policy statements, interpretive rules and rescissions.
This adds the federal consumer-finance regulator to the existing agency guidance sources, which already include OCC bulletins and interpretive letters, FDIC FILs, Federal Reserve SR letters and FinCEN guidance. Both series are served as full text. A circular publishes its full text on its page, while a supervisory-guidance page is a landing stub whose real document is the linked PDF. Circular 2023-03 is absent: the Bureau archived it, publishes no text for it, and leaves only a third-party mirror.goodLawStatus is unknown on both sources, because neither publishes a structured rescission signal. See Status and currency.
The Bureau’s enforcement actions are adjudications and live under corpusType=AGENCY_ADJUDICATION: an enforcement action binds one named respondent, while a circular addresses the whole market. Folding them together would make an AGENCY_GUIDANCE search mean two different things.
Corpus
CFPB enforcement actions

New: CFPB enforcement actions under AGENCY_ADJUDICATION

386 Consumer Financial Protection Bureau enforcement actions, filterable with source=cfpb_enforcement_action. This adds the federal consumer-finance regulator alongside the OCC bulletins, FDIC FILs, Federal Reserve SR letters and FinCEN guidance already held. New fields on this corpus: forum, court and relatedDocuments.
  • Both forums are included and are separable on forum. 225 actions are administrative proceedings carried on a Bureau File No. such as 2024-CFPB-0002. 162 are civil actions the Bureau files in federal district court, which carry the court’s own number in caseNumber and no Bureau citation, because that identifier belongs to the court rather than to the Bureau. One action carries both labels.
  • The unit is the action, not the filing. A consent order and the stipulation consenting to it are one record, because a stipulation is not a separate legal instrument from the order it stipulates to. relatedDocuments names every filing whose text a record carries: 993 documents in total, a mean of 2.6 per action and a maximum of 17. Twelve actions are served with the Bureau’s own summary alone, because it posts no document for them.
  • 185 of the 386 are excluded from ordinary search. The Bureau publishes its own three-value status enum. An action it marks Expired/Terminated/Dismissed is served with a dead actStatus and is therefore outside ordinary search results, which covers close to half the set.
  • A real goodLawStatus. The CFPB is the first AGENCY_ADJUDICATION source with a real verdict, because its status enum is defined, complete and published. MSPB and OLC records stay goodLawStatus: "unknown". See Status and currency.
The Bureau defines Expired/Terminated/Dismissed as a matter that “did not result in, or is no longer subject to, ongoing compliance obligations”. That is correct for an order that no longer binds anyone. It covers three different endings, and the Bureau does not separate them: a matter it lost or withdrew differs from an order that ran its term. Every record therefore carries the Bureau’s own status string verbatim in history.
Corpus
STATUTE_COMPILATION corpus type

New: STATUTE_COMPILATION

A federal corpus token for a public law’s own text as amended through a stated later public law: GovInfo’s official compilations, from its COMPS collection. 80,276 sections across 2,680 compilations.This fills a citation gap. A section like “Section 210 of the Public Utility Regulatory Policies Act” has no USC address, because it was never codified into a positive-law title; STATUTE_COMPILATION is where it resolves.
  • Currency is stated per document. Each section carries currentThrough (for example Public Law 117-58), naming the amending law the compilation reflects. Across the collection that ranges from Public Law 96-308 (1980) to Public Law 119-75 (2026). 2.6% of compilations state no currency at all, and those carry compilationCurrencyState: "unstated" with currentThrough: null rather than a guessed date. STATUTE_COMPILATION does not carry a goodLawStatus certification.
  • The join into USC is captured, not resolved. Where GovInfo publishes a structured cross-reference into the Code (16 U.S.C. 2603, for example), it is served as crossReferencesUsc.
  • Full text is served by GET /us/statutes/section/{actId}/body, like every other corpus.
USC is the codified, subject-organized arrangement, and only for provisions that were codified at all. SESSION_LAW (the Statutes at Large) holds the same acts as enacted, a frozen historical record that carries actStatus: "enacted" and goodLawStatus: "unknown". STATUTE_COMPILATION makes the opposite claim: “this is the act as it reads today, amended through Public Law 117-58.” Merging it into either would risk a decades-old snapshot being read as current law.
Corpus
AGENCY_ADJUDICATION corpus type: OLC and MSPB

New: AGENCY_ADJUDICATION

A federal corpus token for administrative adjudication: matters decided by a federal body through a formal process, carrying precedential weight on its later decisions. It is separate from AGENCY_GUIDANCE, which is interpretive and not adjudicative, so a corpusType=AGENCY_GUIDANCE search keeps meaning one thing. It launched with two bodies, and goodLawStatus is unknown on both. See Status and currency.
OLC opinions are the executive branch’s own controlling legal advice: an opinion binds executive agencies unless the Attorney General or the President overrides it. Sourced entirely from the Department’s own official bound volumes at justice.gov.
  • Fields: each opinion carries its volume and starting page, the canonical citation, the requester it was addressed to, the signing official, its date, and the statutes and regulations it cites. Full text is served by GET /us/statutes/section/{actId}/body.
  • Coverage ends with volume 44 (2020). Opinions issued in 2021 and later have not yet been published in a bound volume and are not included; every section states this in its own coverageNote. Supplemental volume 1 (NN Op. O.L.C. Supp. NNN) adds opinions written 1933-1977 and published later.
  • Currency: an opinion is superseded by a later opinion rather than amended in place, and the publisher ships no structured overruling field. Where OLC printed an editor’s note that an opinion was withdrawn, superseded or reversed, that note is served in currencyNote and the section carries actStatus: "superseded".
5,455 decisions, November 2018 to September 2026, sourced from the Board’s own site, mspb.gov. The MSPB adjudicates federal-employee appeals: removals, suspensions, demotions, reduction-in-force challenges, Individual Right of Action whistleblower claims under the Whistleblower Protection Act, and USERRA cases.
  • Two series, separately filterable. 106 precedential decisions bind administrative judges across the Board’s regional offices. 5,349 nonprecedential orders do not: the Board states in the orders themselves that they “do not add significantly to the body of MSPB case law”. Filter with source=mspb_precedential or source=mspb_nonprecedential, or on the precedential boolean carried by every decision.
  • Fields: each decision carries its docket number, the respondent federal agency, the appellant caption, its issue date, and the Title 5 statutes and regulations it cites (5 U.S.C. 7513, 2302, 1221 and 5 C.F.R. 1201 are the common ones). Only the precedential series has a citation. A nonprecedential order is identified by its docket number, the only identifier the Board assigns it; nothing is synthesized to fill the gap.
  • Supersession links: where two decisions share a docket they are linked with supersedes and supersededBy, which records the sequence only. The Board does not say whether the later decision affirmed, modified or reversed the earlier one, so neither do we.
  • One gap: MSPB decisions are reviewable by the Federal Circuit under 5 U.S.C. 7703, and a reversed decision is no longer good law. The Board publishes nothing about this, and a decision cannot mention its own later appeal, so a decision reversed on appeal is not marked as such here. Every section says so in its currencyNote.
Corpus
State regulations reach all 52 jurisdictions

New: state regulations for every US jurisdiction

State regulations now cover all 52 jurisdictions, 50 states plus DC and Puerto Rico: about 1.51M rules, up from 48 states and about 1.22M.Three are entirely new, each from the jurisdiction’s own publisher:DC’s online edition is the official copy by its own rule, 1 DCMR 300.7. Puerto Rico’s reglamentos are published in Spanish, the language they are enacted in, and language_code is set accordingly; free access is required by LPAU 2.10, 3 L.P.R.A. 9620.
Each of these now comes from the jurisdiction’s own official publisher, with amendment history and a resolvable sourceUrl on every section:Oklahoma, Pennsylvania and Massachusetts are not yet re-sourced and are documented as such.
New Mexico was serving 9 of the 22 NMAC titles. All 22 are now live, at 3,116 parts and 36,310 sections, up from 1,074 parts.Colorado was serving 610 of the 1,155 CCR rules its publisher lists. All 1,155 are now live, including Medicaid, workers’ compensation, taxation, water quality and election rules, which were absent entirely. Colorado amendment coverage goes from none to 99%.
lastAmendedYear and amendmentYears are now populated for Idaho, Illinois, Minnesota, Ohio, South Carolina, Virginia, Washington and Wisconsin, where the publisher records them. Roughly 350,000 sections gained derived amendment history. Texas and Iowa are unchanged: their publishers do not record an amendment for every rule, and the API reports null rather than inferring one.
Over 4.1M distinct sections, indexed as over 11.9M retrieval passages, up from 3.9M and 11.1M.
At the time, Rhode Island and Colorado were keyed one section per Part and per rule respectively, rather than per subsection. Citation lookup and search are unaffected; a finer-grained key for both was in progress.
Corpus
Tennessee regulations

New: Tennessee regulations

Tennessee regulations are live: 11,608 rules, taking state regulations to 49 states, about 1.23M rules. Source is the Official Compilation Rules and Regulations (Tennessee Secretary of State).
Metadata coverage: 98.5% statutory authority, 98.4% amendment years and history, 97.6% effective date. priorEffectiveDates is populated where the publisher records more than one.Watchable as a law-change board (corpusType=STATE_REGULATION, state=tn), refreshing monthly.
Section numbers are zero-padded as Tennessee cites them (0880-05-.01, not 0880-5-.01). Filter sectionNumber with the padded form.
Corpus
SESSION_LAW corpus type

New: read a law as Congress enacted it

A fifteenth corpusType is added: SESSION_LAW, the US Statutes at Large. 5,256 public and private laws, 110,287 sections, 1999 to 2026.The US Code is a compilation. It reorganizes enacted text by subject and drops the structure the enacting Congress used, so a US Code section does not tell you what the act it came from said. SESSION_LAW does.
A US Code section’s publicLawCites resolve directly into this corpus, giving one hop from codified text to enacting text. The join resolves for every US Code section we serve.
These are laws as enacted, a historical record rather than a statement of current law, so they carry actStatus: "enacted" and goodLawStatus: "unknown" by design. For what the law says today, use corpusType=USC.
Corpus
State regulations and court rules expand

Changed: regulations and court rules move onto official sources

State regulations now cover 48 states, about 1.22M rules, with Utah and Kansas joining the corpus.State court rules now cover 46 jurisdictions, about 47.6K rules, with New Mexico (3,462 rules across 47 rule sets), New Jersey and Kentucky added. New Mexico, New Jersey and Kentucky are also now watchable as law-change boards.Re-read counts from GET /us/statutes/coverage instead of carrying them forward. A re-source can move a jurisdiction’s count in either direction.
Fix
GET /boards catalogue fix

Fixed: /boards truncated its catalogue

GET /boards defaulted to limit=200 and returned no total, so with 216 watchable sources every client was reading a truncated list with nothing in the response to say so. Sources sorting last were invisible, including usc, the US Code.The response now carries a total, and paging is explicit. If you built a source picker from this endpoint, re-fetch it. Sources you did not see before were already present.GET /watches also gained filters, so a large watch list can be narrowed server-side instead of client-side.
Endpoint
Five section-level endpoints

New: five endpoints that answer a question about a section

Each takes an actId and answers one question a section lookup could not./changes removes a workaround. Every change our refreshes have observed to a section: when it was added, each time its text was replaced, and whether it has since been removed. Answering that used to require creating a board watch and waiting, because a watch can only show changes that postdate it. This reads the captured history directly./related returns the sections a reader is likely to need, instead of the numerically adjacent row, which in most codes belongs to an unrelated part.Not-found and failed lookups are not charged. An empty result for a section that exists is the answer, and is charged.
Endpoint
Retrieval dates in coverage

New: coverage reports how old each jurisdiction’s data is

GET /us/statutes/coverage gained a retrieval array covering every (jurisdiction, corpusType) pair, maintained ones included:
  • lastRetrievedAt: when we last pulled that body of law from its publisher and finished cleanly
  • cadence: how often we do
  • status: current, stale, failing, or never_retrieved
Read it alongside a section count. It records when we last checked, not when the law last changed, and it does not claim the text is current as of that date. Where a publisher states its own currency, that appears on the section itself as currentThrough.The freshness array lists only the pairs that are not being updated, each with a plain-language reason.
Endpoint
Scoped alerts

New: scoped alerts, watch a citation

POST /watches and PATCH /watches/{watchId} now accept an optional scope so an alert can follow one title, chapter, part or section instead of an entire corpus. Watching cfr meant every change to every federal regulation; now it can mean 21 CFR part 314.
A scoped alert stays quiet when nothing inside its scope changed, rather than sending an empty “the source was updated” on every refresh. Deliveries carry the scope, changes contains only what falls inside it, and GET /watches/{watchId}/changes applies the same filter so the read-back agrees with what we sent.GET /boards gained scopable (whether that source accepts a scope) and scopeBrowseCorpus (the corpusType to pass to GET /us/statutes/divisions to enumerate its titles and parts). Sources whose documents are numbered items rather than citations, such as the Federal Register, are not scopable.Existing alerts are unchanged. An omitted scope means the whole source, and watches created before this change behave as before. See Alerts.
Endpoint
Nine new response fields

New: follow a superseded section to the text that replaced it

Sections now return stored provenance in nine additive, optional fields. Nothing in existing integrations changes.supersededBy points a superseded section to its replacement. Before this change a section with actStatus=superseded was known not to be current law, but nothing in the response identified what replaced it. Example:
Point-in-time research is one hop in either direction.currentThrough is set on every US Code section, so a currency check no longer depends on the publisher having written prose. ruleSet tells court rule families apart: rule numbers repeat across families, and a Civil Rule 12 and a Criminal Rule 12 both exist in most states.Every field is omitted when the publisher does not record it. Absence means the source is silent.
Corpus
State court rules expand

New: court rules grow from 10 jurisdictions to 43

corpusType=STATE_RULES now covers 43 jurisdictions and about 43,500 rules, up from 10 states and roughly 13,000. Added: AK, AL, CT, DC, DE, GA, HI, IA, ID, IN, KS, LA, MA, ME, MI, MS, MT, NC, ND, NE, NH, OH, OR, PR, RI, SC, TN, UT, VA, WA, WI, WV, WY.Every jurisdiction’s rules come from its own court system or legislature (New York’s from nycourts.gov). Coverage spans civil, criminal, appellate, evidence, professional conduct and local rules; the District of Columbia alone carries 21 separately numbered rule families across its Superior Court divisions.Rules are refreshed monthly and carry actStatus, goodLawStatus, amendmentYears, amendmentsCount and lastAmendedYear where the publisher prints them. Amendment coverage varies by source and depends on the publisher: some courts print a dated credit under every rule, others print none at all.A state absent from this list is usually not pending. Some publish no consolidated rules text from a government source, and several codify their rules into the statute book, where they are already served under corpusType=STATE (Nebraska’s evidence rules sit in the statutes as Neb. Rev. Stat. 27-401 and are not duplicated here). At least one restricts access by published court policy. Call GET /us/statutes/coverage for the live per-jurisdiction picture.
Corpus
State insurance guidance expands

New: state agency guidance covers 40 jurisdictions

STATE_AGENCY_GUIDANCE holds each state insurance regulator’s own bulletins and circular letters: the interpretive and enforcement guidance that sits between the statute and the regulation. It is the state-level analog of federal AGENCY_GUIDANCE and is queried with corpusType=STATE_AGENCY_GUIDANCE and a state.Coverage is now 8,986 documents across 40 jurisdictions, up from 5 states. Per-jurisdiction counts are in API Coverage, and GET /us/statutes/coverage always returns the live figures.Every document is sourced from the issuing regulator’s own government site. Where a state’s official index is itself incomplete, the confirmed subset ships and the gap is recorded.A small number of states publish no browsable bulletin archive at all; those are documented as such.
Fix
Search ranks current law first

Changed: dead law no longer competes with live law on relevance alone

Search now ranks a provision’s current text above superseded or rescinded versions of the same provision.Eight actStatus values carried no ranking penalty, so 44,199 passages were ordered as though they were current law: 29,901 superseded, 12,041 rescinded, and smaller counts of revoked, expired, deleted, recodified, unconstitutional and rejected. The effect was largest where a corpus keeps prior versions as their own addressable records, such as a court rule with a version history or a rescinded state regulation. A superseded version is near-identical to the live one, so a relevance score cannot separate the two.Dead law is still returned and searchable. Research often needs the text that was in force when the events happened, so a repealed section is a valid result. It now ranks below live law of comparable relevance instead of being hidden, and every result carries actStatus and goodLawStatus for filtering.No request or response shape changed. If you were relying on the previous ordering to reach prior versions, filter on actStatus explicitly.
Corpus
NLRB memoranda

New: NLRB memoranda join agency guidance

corpusType=AGENCY_GUIDANCE now also covers the National Labor Relations Board’s two guidance vehicles. General Counsel Memoranda (300 memos, the full archive back to 1973) are citable as NLRB General Counsel Memorandum GC 22-04; a rescinded memo carries actStatus=rescinded and a supersededBy pointer to the memo that rescinded it, and the rescinding memo itself lists every memo it rescinded. Division of Advice Memoranda (339 memos) are citable as NLRB Division of Advice Memorandum, Case No. 13-CA-182757 (Savage Fueling); this is a rolling 10-year window, not the full ~2,500-2,600-document archive back to 1969, which remains a future addition. Filter to either with source=nlrb_gc_memo or source=nlrb_advice_memo.
Endpoint
Law change alerts

New: subscribe to a jurisdiction or corpus

A new, free capability: GET /boards lists every source you can watch (a jurisdiction’s statutes, a corpus like the Federal Register or the eCFR), and POST /watches subscribes you to one on a webhook, an email address, or both. When that source refreshes with real changes, you get a signed webhook delivery (X-Vaquill-Event: board.updated, X-Vaquill-Signature when a secret is set) and/or an email naming the exact sections that were added, amended, or removed, not just a count.GET /watches/{watchId}/changes lists that same detail on demand, scoped to your watch’s own lifetime. For any amended section where hasDiff is true, GET /watches/{watchId}/changes/{changeId}/diff returns the section’s text before and after that specific change, so you can show what changed.PATCH /watches/{watchId} pauses, resumes, or rotates a destination. POST /watches/{watchId}/test fires a one-off test delivery before you rely on it. GET /watches/{watchId}/deliveries is webhook delivery history. See the Law Change Alerts guide for the full walkthrough, payload shape, and signature verification.
Corpus
Agency guidance sources added, FAR and DFARS citations

New: agency guidance sources under AGENCY_GUIDANCE

These sources joined corpusType=AGENCY_GUIDANCE on this date, each filterable with its own source value. For current counts see Coverage.The FDIC letters span both the active and the inactive FIL indexes, so superseded letters are held and carry actStatus: "superseded". The DOJ and FTC Merger Guidelines (2023), the DOJ Antitrust Division Leniency Policy and US Copyright Office Circulars also joined, each independently filterable and citation-labeled under the same token.

New: FAR and DFARS citations, and Supreme Court Rules

  • FAR and DFARS: the Federal Acquisition Regulation (48 C.F.R. ch. 1) and the Defense FAR Supplement (ch. 2) were already in the corpus as part of CFR (Title 48). /us/statutes/resolve and citation-shaped search queries now accept the forms practitioners use (FAR 52.219-14, DFARS 252.225-7001, with or without periods or a pinpoint subsection) and resolve them straight to the existing CFR record. Filter to just FAR or just DFARS within corpusType=CFR with source=far or source=dfars.
  • Supreme Court Rules: /us/statutes/resolve and corpusType=FEDERAL_RULES search now cover the Rules of the Supreme Court of the United States (Sup. Ct. R. N), taken from the official supremecourt.gov committee print alongside the five Federal Rules of Procedure sets already served.
See Corpus types for the full source list.
  • FERC Policy Statements are FERC’s generally applicable interpretive vehicle, narrower than the docket-based eLibrary universe of case-specific orders.
  • FCC Declaratory Rulings were discovered from the FCC’s own EDOCS “Commission Documents” listing and resolve a petitioner’s request for the Commission to state its interpretation of a statute, rule or order in a specific factual context.
  • DOE documents the source itself marks “draft” are excluded. The guidance interprets the Energy Policy and Conservation Act program DOE administers.
  • BIS Advisory Opinions interpret the Export Administration Regulations and are a curated, agency-discretion archive.
  • DDTC rulings are ITAR/USML-versus-EAR determinations. Both DDTC sources come directly from DDTC’s own public portal. The 7 policy guidance documents include Guidelines for Preparing Agreements and the ITAR Compliance Program Guidelines and Risk Matrix.
  • CPSC Advisory Opinions are a historical interpretive archive: 139 opinions with a legible text layer, and the program has not issued a new public opinion in over a decade, so they are not presented as current guidance. The Small Entity Compliance Guides are actively maintained per-rule guides required under SBREFA and track new safety-standard final rules as CPSC publishes them. CPSC recall notices (product recalls, safety alerts) are news and safety-communication content, not legal-interpretive text, and remain out of scope.
  • FinCEN: Corporate Transparency Act beneficial-ownership guidance and Anti-Money Laundering Act of 2020 material were not covered on this date because they live on separate FinCEN hub pages. They were added on 2026-09-05 and 2026-09-06.
  • Banking regulators: the FDIC letters span both the active and inactive FIL indexes, so superseded letters stay queryable with actStatus=superseded. The 448 OCC Interpretive Letters are those reachable online from 1996 on.
  • CFTC: pre-2008 letters are not covered, because CFTC’s own site does not browse them separately.
  • DFARS PGI (Procedures, Guidance, and Information) is DoD’s own non-codified procedural companion to the DFARS.
Endpoint
Catalog of bodies of law

New: GET /statutes/laws

A catalog of the distinct bodies of law available, each a whole corpus within a jurisdiction (a state’s statutes, a state’s regulations, the US Code, the US Constitution, federal court rules, …). Every entry carries a stable key, its corpusType (pass straight to /us/statutes/search), a lawType (statutes, regulations, constitution, court rules, …), a human name, and a sectionCount.
  • GET /statutes/laws lists every jurisdiction.
  • GET /statutes/laws?jurisdiction=ca (or federal) scopes the list.
Use it to build a picker of what is queryable or to ground an LLM in the available bodies of law. To drill a state’s statutes into its individual codes (Penal, Civil, …), call GET /statutes/codes?state=XX. Free (an API key, rate-limited, no credits).
Endpoint
Citation resolver covers more forms

New: resolve constitutions, court rules and more citation forms

GET /us/statutes/resolve (and citation-as-query search) now resolves several citation families it previously missed:
  • US and state constitutions: U.S. Const. art. I, § 8, U.S. Const. amend. XIV, § 1, U.S. Const. pmbl., Cal. Const. art. I, § 7.
  • Federal court rules: Fed. R. Civ. P. 12 (incl. a pincite like Fed. R. Civ. P. 12(b)(6)), Fed. R. Crim. P. 11, Fed. R. Evid. 702, Fed. R. App. P. 4, Fed. R. Bankr. P. 9011, and the compact FRCP 12 form.
  • Annotated / prefixed federal statutes: the annotated 42 U.S.C.A. § 1983 and 42 U.S.C.S. § 1983 forms, Title 42 U.S.C. § 1983, and a doubled §§.
This is additive. A Bluebook citation names one exact section and remains the most reliable way to reach or verify one. See Resolve and verify a citation.
Endpoint
Scope a search to a chapter or part

New: search within a hierarchy subtree

POST /us/statutes/search gains two filters that scope a search below a title or code, additive and optional:
  • chapter (USC/state) and part (CFR): confine results to one or more chapters or parts, e.g. titleNumber: 42, chapter: "21" or titleNumber: 17, part: "240". Both accept a single value or a list.
These are the search-side of the parent object on every result: take a hit’s parent and pass it straight back to search that section’s neighbors. Because a chapter number repeats across every title, chapter/part must be paired with titleNumber or code (which parent always carries); an unpaired one is rejected with 422. See Search within a container.
Endpoint
Search controls and deeper paging

New: control what search matches and returns

POST /us/statutes/search gains two request options, both additive:
  • matchType: any (default) is intent-ranked hybrid search. all requires every query term to appear; phrase requires the exact phrase. Use the stricter modes when you need precision over recall.
  • excerptChars: how much matching text each result carries in excerpt (default 500, range 100 to 4000). Raise it for more inline context.

New: every result points to its neighbors

Each result carries a parent object: the ready-made GET /us/statutes/divisions query that lists the section’s siblings (its containing chapter or part). Walk up the hierarchy from any hit without constructing the query yourself.

New: amendment provenance on statute results

Statute results now surface amendment history already in the corpus: sourceCredit (the source’s credit line), amendmentYears, lastAmendedYear, amendmentsCount, publicLaws (e.g. ['Pub. L. 102-166']), and federalRegisterCitations. All are nullable and additive; existing fields are unchanged.

Changed: deeper paging

The offset cap on POST /us/statutes/search is raised from 40 to 70, so with the largest page size you can reach the entire reranked candidate pool. See Pagination.
Endpoint
Structured body

New: /body can now return a structured subsection tree

GET /us/statutes/section/{actId}/body?structured=true adds two fields to the body response, at no extra cost:
  • markdown: the section rendered as nested Markdown lists, one level per subsection depth.
  • subsections: a tree parsed by the drafting convention ((a) subsection, (1) paragraph, (A) subparagraph, (i) clause). Each node carries its label, a pincite path (e.g. (b)(2)), a full pinpoint citation (e.g. 42 U.S.C. § 1983(b)(2)), its own text, and nested children.
Use it to address, deep-link, or quote a specific subsection. It is additive: the default /body response is unchanged. See Response Formats.
Endpoint
Citation resolver and hierarchy browse

New: two endpoints, resolve a citation and browse the hierarchy

  • GET /us/statutes/resolve (2 credits): resolve a Bluebook citation string (42 U.S.C. § 1983, 16 C.F.R. § 444.1, Del. Code Ann. tit. 13, § 1301) straight to the exact section, confirmed, with an official source link. A pinpoint subsection resolves to the parent section and is echoed in subsection. resolved reports whether the citation is real, so it is the one-call way to verify a citation an LLM produced. See the citation recipe.
  • GET /us/statutes/divisions (1 credit): walk the statutory hierarchy one level at a time, in statutory order. Pass the deepest level you know (corpusType, titleNumber, chapter/part, or a state code) and get the children below it, down to sections with their actId. Supports USC, CFR, STATE, and REGULATION. See the browse recipe.
Both are additive and use the existing API key and credit model.
Endpoint
Richer statute results

Changed: statute results carry status, currency and fuller metadata

Every statute result (from POST /us/statutes/search, GET /us/statutes/section/{actId}, and POST /us/statutes/sections) now includes additional fields that were already in the corpus. This is additive: existing fields are unchanged, so no client change is required.
  • Status and currency: actStatus (in_force, repealed, renumbered, transferred, omitted, reserved, vacant, unconstitutional), a derived goodLawStatus (good_law / not_good_law / not_operative / unknown), currencyNote (the source’s “current through …” line), and renumberedTo / transferredTo pointers.
  • Fuller hierarchy: subchapter / subchapterName, part / partName, subpart / subpartName, and popularName (e.g. “Truth in Lending Act”).
  • Provenance: issueDate, crossReferencesCfr (parsed CFR references as a list of section strings, e.g. ['1.6011-4']), and govinfo granuleId / packageId.
goodLawStatus is conservative: jurisdictions without a reliable repeal signal report unknown instead of asserting that a section is current.
CorpusEndpointDocs
Regulations, coverage discovery, pagination

New: regulations, Federal Register and agency guidance are queryable

Three new corpusType tokens make existing corpora filterable:
  • REGULATION: state administrative regulations (176K+ rules across 12 states at launch; all 52 jurisdictions since 2026-08-27).
  • FEDERAL_REGISTER: Federal Register agency rules, final and proposed (100K+ documents).
  • AGENCY_GUIDANCE: agency guidance, including SSA rulings and IRS notices, revenue rulings, and procedures.
Scope a search to any of them with the corpusType filter (pair REGULATION with a state). See Corpus Types.
A self-describing coverage matrix. It returns a legend of every corpusType token (its meaning and whether it is federal or state scoped) plus, for each jurisdiction, the per-corpusType counts.Call it to see what is queryable where, then pass a token as corpusType. See Jurisdictions and State Codes and the coverage monitoring recipe.
Each jurisdiction row now includes a corpora object, for example {"STATE": 176778, "REGULATION": 51142, "STATE_CONSTITUTION": 179}, so you can see which corpora a jurisdiction has without a separate call.
Search now accepts an offset parameter (0-40) alongside limit, and the response includes offset and a hasMore flag so you can page through results. total is the count returned on the current page. See Pagination.
The STATE_RULES (state court rules) corpus is now served. Court rules are available for a handful of states, discoverable via /us/statutes/coverage.
A full developer guide: Quickstart, Core Concepts, Pagination, Rate Limits, Best Practices, a Grounding LLMs guide, eight Recipes, and a Use Cases catalog.
Last modified on November 8, 2026