> ## Documentation Index > Fetch the complete documentation index at: https://vaquill.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. # Search US statutes, constitutions, court rules, and executive actions > Search across federal and state law and get back the most relevant sections with citations and links to official source documents. State session laws (acts as enacted) are at /us/session-laws. **Corpora (`corpusType`):** - `USC`: United States Code - `CFR`: Code of Federal Regulations - `STATE`: State statutory codes. Call `/us/statutes/coverage` for live coverage and `/us/statutes/divisions` (`corpusType=STATE&state=XX`) for a state's codes; see the [Coverage page](https://www.vaquill.ai/docs/coverage) for the full breakdown. - `CONSTITUTION`: U.S. Constitution (Articles I-VII + 27 Amendments) - `FEDERAL_RULES`: FRCP, FRCrP, FRE, FRAP, FRBP - `STATE_CONSTITUTION`: state constitutions. Call `/us/statutes/coverage` for live coverage. - `STATE_RULES`: state court rules. Call `/us/statutes/coverage` for live coverage; see the [Coverage page](https://www.vaquill.ai/docs/coverage) for the full breakdown. - `EXECUTIVE_ACTION`: Federal Register Presidential Documents (Executive Orders, Proclamations, Memos; 2015 to today, refreshed daily) - `REGULATION`: state administrative regulations (pair with `state`; call `/us/statutes/coverage` for coverage) - `FEDERAL_REGISTER`: Federal Register agency rules, final and proposed - `AGENCY_GUIDANCE`: sub-regulatory federal agency guidance, 53 named sources across the tax, banking, securities, labor, immigration, health-privacy, export-control, intellectual-property, antitrust, energy and communications agencies. Scope to one with `source` (which lists every code and name), or see the [Coverage page](https://www.vaquill.ai/docs/api-guide/coverage#federal) for the per-source table. - `STATE_AGENCY_GUIDANCE`: state-issued regulatory guidance, currently state Department of Insurance bulletins and circular letters (pair with `state`; call `/us/statutes/coverage` for coverage) - `SENTENCING_GUIDELINES`: US Sentencing Guidelines Manual - `US_TAX_TREATY`: US income tax treaties and protocols **Authentication**: API key via `Authorization: Bearer vq_key_...` **Cost**: 4 credits per call (see `/api-credits/pricing`). Failed calls are not charged. Set `includeBody: true` to get each hit's full text inline on `body`, instead of a follow-up `/section/{actId}/body` call per result. That adds the ordinary 6-credit body price for each row that actually returns text, so it buys round trips and latency rather than a discount; rows we cannot resolve come back `body: null` and are not charged. Read `creditsConsumed`. **Pagination**: use `limit` (page size, max 50) with `offset` (max 70); check `hasMore` in the response to page forward. `count` is the size of the CURRENT page, not a corpus-wide match total -- ranking runs over a bounded window, so no such total exists. (`total` is a deprecated alias for `count`.) Every page of a given query slices one ranking, so results never repeat or go missing across pages. Returns relevant sections with full metadata: citation, title hierarchy, and direct links to official source documents where available. **Matching (`matchType`)**: search is hybrid semantic + keyword by default (`any`), which suits natural-language questions. For strict keyword or exact-phrase lookups, use `matchType: "all"` or `"phrase"` -- there is no separate keyword-only mode to reach for. To jump straight to one section, pass its citation as the `query` (e.g. `42 U.S.C. § 1983`) and it resolves to rank 1. ## Examples ```python # Search SEC regulations requests.post(url, headers=h, json={ "query": "insider trading material nonpublic information", "corpusType": "CFR", "titleNumber": 17, "limit": 5, }) # Search California state statutes requests.post(url, headers=h, json={ "query": "shareholder derivative action standing", "corpusType": "STATE", "state": "ca", }) # Search Executive Orders on a topic requests.post(url, headers=h, json={ "query": "AI safety federal agency adoption", "corpusType": "EXECUTIVE_ACTION", }) # Search Federal Rules of Civil Procedure requests.post(url, headers=h, json={ "query": "personal jurisdiction long-arm statute", "corpusType": "FEDERAL_RULES", }) # Cross-corpus search (no corpusType filter) requests.post(url, headers=h, json={ "query": "due process equal protection fourteenth amendment", }) ``` ## Parameters Every filter below accepts a single value OR a list, so one call can span several jurisdictions or corpora. - `query` (required): natural-language or keyword query, 2 to 500 characters. - `corpusType` (optional, string or list): one of the corpus tokens above, e.g. `"CFR"` or `["USC", "CFR"]`. Case-insensitive. Omit to search every corpus. - `state` (optional, string or list): a 2-letter jurisdiction code (50 states + DC + PR), or `federal` to scope to USC / CFR / Constitution / federal rules in one call. `["ca", "ny", "tx"]` searches three at once. Case-insensitive. An unrecognized value is rejected with 422 rather than silently matching nothing. - `code` (optional, string or list): restrict to specific state statutory codes, e.g. `"tx_pe"` for the Texas Penal Code. Values are the `identifier`s returned by `GET /us/statutes/divisions?corpusType=STATE&state=XX`. This is the only way to scope BELOW a jurisdiction: `state=tx` alone searches every Texas code. With `corpusType=FEDERAL_RULES`, a value can be a rule set from `GET /us/statutes/divisions?corpusType=FEDERAL_RULES` instead (`"frcp"`, `"uscapp_t28a_fre"`). - `article` (optional, string or list): scope to an article. On `CONSTITUTION` / `STATE_CONSTITUTION`, the article label browse lists (`"Amendment XIV"`, `"Article IV"`); on a `STATE` / `REGULATION` code divided by article rather than chapter (New York), its article number (`"2-A"`). Needs a `corpusType` from one of those families, plus `state` on `STATE_CONSTITUTION` and `code` on `STATE`/`REGULATION`; a missing pairing is a 422 before anything is charged. - `titleNumber` (optional, integer): restrict to a USC/CFR title (e.g. 17 for SEC, 42 for civil rights). Applies only to `USC`/`CFR`; state titles are alphabetic or collide across states, so use `code` for those. - `chapter` / `part` (optional, string or list): scope BELOW a title/code to a chapter (USC/state) or part (CFR), e.g. `chapter="21"` or `part="240"`. This is the search-side of the `parent` object on each result: feed a hit's `parent` back to search its neighbors (a constitution, federal-rules or New York hit's `parent` carries `article` or a rule-set `code` for the same purpose). Must be paired with `titleNumber` or `code`, which `parent` always carries; an unpaired chapter/part is rejected with 422. - `matchType` (optional): `any` (default) intent-ranked hybrid, `all` requires every query word, `phrase` requires the query's words in order. Both match WHOLE words, case-insensitively, ignoring punctuation (`act` does not match `fact`; `10b-5` matches `10b 5`; `§ 1983` matches `section 1983`). - `yearFrom` / `yearTo` (optional, integer): bound results by version year. A section matches on its credited amendment year, else its effective year, else (for corpora dated by publication rather than amendment: Federal Register proposed rules, agency guidance, adjudications, the treaty record) the document's own publication year. Sections carrying none of the three are excluded once either bound is set. - `limit` (optional, default 10, max 50): page size. - `offset` (optional, default 0, max 70): results to skip. See Pagination below. ## Tips - Provide `corpusType` whenever you know it. Unscoped queries can surface keyword matches from unrelated corpora; a corpus filter sharply improves precision. - Take a returned `actId` and call `/us/statutes/section/{actId}` for metadata or `/us/statutes/section/{actId}/body` for the full text. To enrich a whole page at once, POST up to 50 ids to `/us/statutes/sections` instead of looping. - `relevanceScore` ranks results within one response; do not compare it across different queries. A recognized citation (e.g. `"Cal. CIV § 1952"`, `"42 USC 1983"`) always resolves its exact section to the top result at `relevanceScore: 1.0`; if you already know the citation, `GET /us/statutes/resolve` is a cheaper way to get the same section without paying for a search. ## OpenAPI ````yaml https://api.vaquill.ai/external/openapi.json post /api/v1/us/statutes/search openapi: 3.1.0 info: title: Vaquill Developer API description: >- Public API for legal statutes and legislation. **Authentication**: Pass your API key as `Authorization: Bearer vq_key_...` (preferred) or in the `X-API-Key` header. The `api_key` query parameter also works where a header cannot be set, but a URL ends up in logs and browser history. Sending two different keys in one request is rejected with a 401. **Credits**: Each call costs API credits. See `GET /api/v1/api-credits/pricing` for the full pricing matrix. ## Jurisdictions | Jurisdiction | Coverage | `countryCode` | |---|---|---| | **United States** | USC and the Statutes at Large, the CFR and its annual editions, all 56 state and territory statutory codes (50 states, DC and five territories), state administrative regulations, court rules, federal and state constitutions, federal agency guidance and adjudications, the Federal Register, the Sentencing Guidelines and US tax treaties. | `US` | See the full [Coverage page](https://www.vaquill.ai/docs/api-guide/coverage) for the jurisdiction-by-jurisdiction breakdown, or call `/us/statutes/coverage` for live counts. Coverage is per (jurisdiction, corpusType) pair, so treat that endpoint as the authoritative list rather than this summary. ## Endpoints - **US Statutes**: Search and retrieve any of the corpora above with full text, resolve a citation to its exact section, browse the statutory hierarchy, read a section as it stood on a past date, and follow its change history, cross-references and defined terms - **Board Watches**: Subscribe to a corpus source and get a webhook or email when it refreshes with real changes (free, API key required) - **Pricing**: Credit costs per endpoint (no auth required) ## Rate limits Limits are enforced per API key and scale with your plan. A `429` response includes a `Retry-After` header. | Plan | Per minute | Per hour | Per day | |---|---|---|---| | Vaquill API Pro | 60 | 1,000 | 2,000 | | Vaquill API Business | 150 | 2,500 | 10,000 | For full documentation, visit the [API Reference](https://www.vaquill.ai/docs/api-reference/). version: 1.0.0 contact: name: Vaquill API Support url: https://www.vaquill.ai email: support@vaquill.ai license: name: Proprietary url: https://www.vaquill.ai/terms termsOfService: https://www.vaquill.ai/terms servers: - url: https://api.vaquill.ai description: Production security: - ApiKeyAuth: [] - ApiKeyHeader: [] - ApiKeyQuery: [] tags: - name: US Statutes description: >- Search and retrieve US primary law. Covers the United States Code and the Statutes at Large, the Code of Federal Regulations and its annual editions, state statutory codes and administrative regulations, federal and state constitutions, court rules, Federal Register rules and Presidential documents, federal and state agency guidance, agency adjudications, state Attorney General opinions, the Sentencing Guidelines and US tax treaties. Scope a search with the `corpusType` filter, and call `/us/statutes/coverage` for the live jurisdiction-by-corpusType list. - **Search**: Search across all USC, CFR, state, and regulatory sections - **Section**: Get metadata, citation, hierarchy, and source links for a specific section - **Body**: Get the full text of a section - **Enactments**: Which state session laws a publisher's own tables list against a section (supported jurisdictions only, never a complete history) - name: US Session Laws description: >- State session laws: the acts of each legislature as they were enacted, chapter by chapter, before they are folded into a code. A session law is what the governor signs. It carries the act's own text, including the language it strikes and inserts, its approval and effective dates, and, where the publisher prints one, the code sections it changes. That makes it the source for "which act changed this section, and when did it take effect". Every act has a permanent `sessionLawId` (for example `SSL_MN_2025R_G_Y2025_C1`, Minnesota Laws 2025, regular session, chapter 1) whether or not we hold its text, and a citation or bill number such as `S.F.No. 1552` is accepted where an id goes. v1 serves STATE acts only. Federal session laws (the Statutes at Large, `SAL_` ids) are served by `/us/statutes/section`, and `/us/statutes/resolve` points a session-law citation here. **Start here**: check `/us/statutes/coverage` (free) for what we hold per state: each jurisdiction's `sessionLaws` block lists its sessions, which are complete or only partly collected, and the `series` and `instrumentTypes` that exist. Then **List** a session or a date range to get ids, **Get** one act for its record, then **Body** for its text. A law missing from a partly collected session is a free 404 (`session_not_fully_collected`), not proof it does not exist. - **List**: everything enacted in a state's session, approved in a window, or taking effect on a date - **Get**: one act by id or by citation; dates (`effectiveDates` is always a list), sources and the code sections it affects - **Body**: the act's text as printed, paged by cursor, with amendatory markup preserved where the publisher printed it - **Batch**: up to 50 ids or citations in one call, the same record as Get, billed per law served, with every miss listed and its reason - **Changes**: a sync feed of the registry over an integer cursor (`sinceId`): what began to be served, was corrected, withdrawn or merged The reverse link, from a code section to the acts a publisher's own tables list against it, is `GET /us/statutes/section/{actId}/enactments`. - name: Board Watches description: >- Law-change alerts. Subscribe to a **board** (a tracked corpus source, identified by `corpusType` plus an optional `state`) and get a webhook or email whenever it refreshes with real changes, naming the exact sections that changed. Fetch old-vs-new text for any amended section via the change diff. Boards refresh on their own existing cadence; watching one does not change how often it refreshes. Every endpoint here is **free**: authenticated by API key and rate-limited, but not credit-metered. See the [Law Change Alerts guide](https://www.vaquill.ai/docs/api-guide/alerts) for the full walkthrough. - name: Pricing description: >- Credit pricing and conversion rates. No authentication required. 1 credit = $0.01 USD. - name: Credits description: >- Your own credit balance: what is spendable right now, where it came from, and what is about to expire. Free and never charged, so it is safe to poll for low-balance alerting or to pre-flight a batch job. externalDocs: description: Full API Reference url: https://www.vaquill.ai/docs/api-reference/ paths: /api/v1/us/statutes/search: post: tags: - US Statutes summary: Search US statutes, constitutions, court rules, and executive actions description: >- Search across federal and state law and get back the most relevant sections with citations and links to official source documents. State session laws (acts as enacted) are at /us/session-laws. **Corpora (`corpusType`):** - `USC`: United States Code - `CFR`: Code of Federal Regulations - `STATE`: State statutory codes. Call `/us/statutes/coverage` for live coverage and `/us/statutes/divisions` (`corpusType=STATE&state=XX`) for a state's codes; see the [Coverage page](https://www.vaquill.ai/docs/coverage) for the full breakdown. - `CONSTITUTION`: U.S. Constitution (Articles I-VII + 27 Amendments) - `FEDERAL_RULES`: FRCP, FRCrP, FRE, FRAP, FRBP - `STATE_CONSTITUTION`: state constitutions. Call `/us/statutes/coverage` for live coverage. - `STATE_RULES`: state court rules. Call `/us/statutes/coverage` for live coverage; see the [Coverage page](https://www.vaquill.ai/docs/coverage) for the full breakdown. - `EXECUTIVE_ACTION`: Federal Register Presidential Documents (Executive Orders, Proclamations, Memos; 2015 to today, refreshed daily) - `REGULATION`: state administrative regulations (pair with `state`; call `/us/statutes/coverage` for coverage) - `FEDERAL_REGISTER`: Federal Register agency rules, final and proposed - `AGENCY_GUIDANCE`: sub-regulatory federal agency guidance, 53 named sources across the tax, banking, securities, labor, immigration, health-privacy, export-control, intellectual-property, antitrust, energy and communications agencies. Scope to one with `source` (which lists every code and name), or see the [Coverage page](https://www.vaquill.ai/docs/api-guide/coverage#federal) for the per-source table. - `STATE_AGENCY_GUIDANCE`: state-issued regulatory guidance, currently state Department of Insurance bulletins and circular letters (pair with `state`; call `/us/statutes/coverage` for coverage) - `SENTENCING_GUIDELINES`: US Sentencing Guidelines Manual - `US_TAX_TREATY`: US income tax treaties and protocols **Authentication**: API key via `Authorization: Bearer vq_key_...` **Cost**: 4 credits per call (see `/api-credits/pricing`). Failed calls are not charged. Set `includeBody: true` to get each hit's full text inline on `body`, instead of a follow-up `/section/{actId}/body` call per result. That adds the ordinary 6-credit body price for each row that actually returns text, so it buys round trips and latency rather than a discount; rows we cannot resolve come back `body: null` and are not charged. Read `creditsConsumed`. **Pagination**: use `limit` (page size, max 50) with `offset` (max 70); check `hasMore` in the response to page forward. `count` is the size of the CURRENT page, not a corpus-wide match total -- ranking runs over a bounded window, so no such total exists. (`total` is a deprecated alias for `count`.) Every page of a given query slices one ranking, so results never repeat or go missing across pages. Returns relevant sections with full metadata: citation, title hierarchy, and direct links to official source documents where available. **Matching (`matchType`)**: search is hybrid semantic + keyword by default (`any`), which suits natural-language questions. For strict keyword or exact-phrase lookups, use `matchType: "all"` or `"phrase"` -- there is no separate keyword-only mode to reach for. To jump straight to one section, pass its citation as the `query` (e.g. `42 U.S.C. § 1983`) and it resolves to rank 1. ## Examples ```python # Search SEC regulations requests.post(url, headers=h, json={ "query": "insider trading material nonpublic information", "corpusType": "CFR", "titleNumber": 17, "limit": 5, }) # Search California state statutes requests.post(url, headers=h, json={ "query": "shareholder derivative action standing", "corpusType": "STATE", "state": "ca", }) # Search Executive Orders on a topic requests.post(url, headers=h, json={ "query": "AI safety federal agency adoption", "corpusType": "EXECUTIVE_ACTION", }) # Search Federal Rules of Civil Procedure requests.post(url, headers=h, json={ "query": "personal jurisdiction long-arm statute", "corpusType": "FEDERAL_RULES", }) # Cross-corpus search (no corpusType filter) requests.post(url, headers=h, json={ "query": "due process equal protection fourteenth amendment", }) ``` ## Parameters Every filter below accepts a single value OR a list, so one call can span several jurisdictions or corpora. - `query` (required): natural-language or keyword query, 2 to 500 characters. - `corpusType` (optional, string or list): one of the corpus tokens above, e.g. `"CFR"` or `["USC", "CFR"]`. Case-insensitive. Omit to search every corpus. - `state` (optional, string or list): a 2-letter jurisdiction code (50 states + DC + PR), or `federal` to scope to USC / CFR / Constitution / federal rules in one call. `["ca", "ny", "tx"]` searches three at once. Case-insensitive. An unrecognized value is rejected with 422 rather than silently matching nothing. - `code` (optional, string or list): restrict to specific state statutory codes, e.g. `"tx_pe"` for the Texas Penal Code. Values are the `identifier`s returned by `GET /us/statutes/divisions?corpusType=STATE&state=XX`. This is the only way to scope BELOW a jurisdiction: `state=tx` alone searches every Texas code. With `corpusType=FEDERAL_RULES`, a value can be a rule set from `GET /us/statutes/divisions?corpusType=FEDERAL_RULES` instead (`"frcp"`, `"uscapp_t28a_fre"`). - `article` (optional, string or list): scope to an article. On `CONSTITUTION` / `STATE_CONSTITUTION`, the article label browse lists (`"Amendment XIV"`, `"Article IV"`); on a `STATE` / `REGULATION` code divided by article rather than chapter (New York), its article number (`"2-A"`). Needs a `corpusType` from one of those families, plus `state` on `STATE_CONSTITUTION` and `code` on `STATE`/`REGULATION`; a missing pairing is a 422 before anything is charged. - `titleNumber` (optional, integer): restrict to a USC/CFR title (e.g. 17 for SEC, 42 for civil rights). Applies only to `USC`/`CFR`; state titles are alphabetic or collide across states, so use `code` for those. - `chapter` / `part` (optional, string or list): scope BELOW a title/code to a chapter (USC/state) or part (CFR), e.g. `chapter="21"` or `part="240"`. This is the search-side of the `parent` object on each result: feed a hit's `parent` back to search its neighbors (a constitution, federal-rules or New York hit's `parent` carries `article` or a rule-set `code` for the same purpose). Must be paired with `titleNumber` or `code`, which `parent` always carries; an unpaired chapter/part is rejected with 422. - `matchType` (optional): `any` (default) intent-ranked hybrid, `all` requires every query word, `phrase` requires the query's words in order. Both match WHOLE words, case-insensitively, ignoring punctuation (`act` does not match `fact`; `10b-5` matches `10b 5`; `§ 1983` matches `section 1983`). - `yearFrom` / `yearTo` (optional, integer): bound results by version year. A section matches on its credited amendment year, else its effective year, else (for corpora dated by publication rather than amendment: Federal Register proposed rules, agency guidance, adjudications, the treaty record) the document's own publication year. Sections carrying none of the three are excluded once either bound is set. - `limit` (optional, default 10, max 50): page size. - `offset` (optional, default 0, max 70): results to skip. See Pagination below. ## Tips - Provide `corpusType` whenever you know it. Unscoped queries can surface keyword matches from unrelated corpora; a corpus filter sharply improves precision. - Take a returned `actId` and call `/us/statutes/section/{actId}` for metadata or `/us/statutes/section/{actId}/body` for the full text. To enrich a whole page at once, POST up to 50 ids to `/us/statutes/sections` instead of looping. - `relevanceScore` ranks results within one response; do not compare it across different queries. A recognized citation (e.g. `"Cal. CIV § 1952"`, `"42 USC 1983"`) always resolves its exact section to the top result at `relevanceScore: 1.0`; if you already know the citation, `GET /us/statutes/resolve` is a cheaper way to get the same section without paying for a search. operationId: search_statutes_api_v1_us_statutes_search_post requestBody: content: application/json: schema: $ref: '#/components/schemas/StatuteSearchRequest' required: true responses: '200': description: Ranked sections for the query. content: application/json: schema: $ref: '#/components/schemas/StatuteSearchResponse' example: results: - actId: CFR_T17_P240_S240_10b5_1 citation: 17 C.F.R. § 240.10b5-1 (2026) citationShort: 17 C.F.R. § 240.10b5-1 title: >- Trading on the basis of material nonpublic information in insider trading cases corpusType: CFR state: federal year: 2026 relevanceScore: 0.91 excerpt: >- The manipulative and deceptive devices prohibited by section 10(b)... titleNumber: 17 sectionNumber: 240.10b5-1 displayPath: Title 17 CFR > Chapter II > Part 240 > Section 240.10b5-1 htmlUrl: https://statutes-us.vaquill.ai/ecfr/... externalUrl: https://www.ecfr.gov/... sourceUrl: https://www.ecfr.gov/... total: 1 query: insider trading material nonpublic information processingTimeMs: 412.3 creditsConsumed: 4 '402': description: Insufficient API credits. content: application/json: schema: $ref: '#/components/schemas/ApiDetailError' example: detail: Insufficient credits '422': description: >- Invalid request body (e.g. query too short, limit over 50, bad corpusType). content: application/json: schema: $ref: '#/components/schemas/ApiDetailError' example: detail: Invalid request parameters errors: - loc: - body - limit msg: Input should be less than or equal to 50 type: less_than_equal components: schemas: StatuteSearchRequest: properties: query: type: string maxLength: 500 minLength: 2 title: Query description: Search query in natural language. examples: - insider trading penalties corpusType: anyOf: - type: string enum: - USC - CFR - STATE - CONSTITUTION - FEDERAL_RULES - FEDERAL_LOCAL_RULES - STATE_CONSTITUTION - STATE_RULES - EXECUTIVE_ACTION - REGULATION - FEDERAL_REGISTER - FEDERAL_REGISTER_NOTICE - AGENCY_GUIDANCE - SENTENCING_GUIDELINES - US_TAX_TREATY - STATE_AGENCY_GUIDANCE - STATE_AG_OPINION - STATE_REGISTER - SESSION_LAW - STATUTE_COMPILATION - AGENCY_ADJUDICATION - CFR_ANNUAL - USC_ANNUAL - items: type: string enum: - USC - CFR - STATE - CONSTITUTION - FEDERAL_RULES - FEDERAL_LOCAL_RULES - STATE_CONSTITUTION - STATE_RULES - EXECUTIVE_ACTION - REGULATION - FEDERAL_REGISTER - FEDERAL_REGISTER_NOTICE - AGENCY_GUIDANCE - SENTENCING_GUIDELINES - US_TAX_TREATY - STATE_AGENCY_GUIDANCE - STATE_AG_OPINION - STATE_REGISTER - SESSION_LAW - STATUTE_COMPILATION - AGENCY_ADJUDICATION - CFR_ANNUAL - USC_ANNUAL type: array - type: 'null' title: Corpustype description: >- Restrict to one corpus, or to several by passing a list (`"corpusType": ["USC", "CFR"]`). One of: `USC` (United States Code), `CFR` (Code of Federal Regulations), `STATE` (state statutory codes; call `/us/statutes/coverage` for the list of ingested jurisdictions), `CONSTITUTION` (U.S. Constitution), `FEDERAL_RULES` (FRCP / FRCrP / FRE / FRAP / FRBP), `STATE_CONSTITUTION` (state constitutions; call `/us/statutes/coverage` for the current jurisdiction list), `STATE_RULES` (state court rules; see `/us/statutes/coverage`), `EXECUTIVE_ACTION` (Federal Register Presidential Documents), `REGULATION` (state administrative regulations; pair with `state`), `FEDERAL_REGISTER` (Federal Register agency rules, final and proposed), `AGENCY_GUIDANCE` (sub-regulatory federal agency guidance, 53 named sources spanning the tax, banking, securities, labor, immigration, health-privacy, export-control, intellectual-property, antitrust, energy and communications agencies; each is independently filterable with `source`, which lists them all), `STATE_AGENCY_GUIDANCE` (state-issued regulatory guidance, currently state Department of Insurance bulletins and circular letters; pair with `state`, and see `/us/statutes/coverage`), `SENTENCING_GUIDELINES` (US Sentencing Guidelines Manual), `US_TAX_TREATY` (US income tax treaties and protocols), `SESSION_LAW` (US Statutes at Large: federal public and private laws AS ENACTED, 1789 to date. This is the source the US Code is compiled from, so a section's `publicLawCites` resolve here to the enacting text; call `/us/statutes/coverage` for the live section count). Omit to search across all corpora. The `enum` on this field is the complete token list, and `/us/statutes/coverage` serves a one-line description of each in its legend. examples: - CFR state: anyOf: - type: string enum: - federal - al - ak - as - az - ar - ca - co - ct - de - dc - fl - ga - gu - hi - id - il - in - ia - ks - ky - la - me - md - ma - mi - mn - ms - mo - mt - ne - nv - nh - nj - nm - ny - nc - nd - mp - oh - ok - or - pa - pr - ri - sc - sd - tn - tx - ut - vt - vi - va - wa - wv - wi - wy - items: type: string enum: - federal - al - ak - as - az - ar - ca - co - ct - de - dc - fl - ga - gu - hi - id - il - in - ia - ks - ky - la - me - md - ma - mi - mn - ms - mo - mt - ne - nv - nh - nj - nm - ny - nc - nd - mp - oh - ok - or - pa - pr - ri - sc - sd - tn - tx - ut - vt - vi - va - wa - wv - wi - wy type: array - type: 'null' title: State description: >- Jurisdiction filter. A 2-letter code for one of the 52 supported US jurisdictions (50 states + DC + PR), or `federal` to scope to USC / CFR / Constitution / federal rules. Pass a LIST to search several at once (`"state": ["ca", "ny", "tx"]`), which is one call instead of one per jurisdiction. Case-insensitive: `ca` and `CA` both work. An unrecognized value is rejected with 422 rather than silently matching nothing. Omit to search every jurisdiction. examples: - ca code: anyOf: - type: string - items: type: string type: array - type: 'null' title: Code description: >- Restrict to specific state statutory codes, e.g. `tx_pe` for the Texas Penal Code. Values are the `identifier`s returned by `GET /us/statutes/divisions?corpusType=STATE&state=XX`, so the browse output can be fed straight back in. Pass a list to search several codes, across states if you like (`["tx_pe", "ca_pen"]`). This is the only way to scope below a whole jurisdiction: `state=tx` alone searches every Texas code at once. With `corpusType=FEDERAL_RULES`, a value can instead be a federal rule set as `GET /us/statutes/divisions?corpusType=FEDERAL_RULES` lists it: `frcp`, `fre`, `frcpsuppadm`, or an appendix copy such as `uscapp_t28a_fre`. Without that corpusType a bare `frcp` is refused, because it cannot be told apart from a state code missing its state. examples: - tx_pe article: anyOf: - type: string - items: type: string type: array - type: 'null' title: Article description: >- Scope a search to one or more articles. On `CONSTITUTION` and `STATE_CONSTITUTION` this is the article label as `GET /us/statutes/divisions` lists it (`Amendment XIV`, `Article IV`, `Preamble`). On `STATE` / `REGULATION` it is the article of a code divided by article instead of chapter, such as New York (`2-A` in `ny_jud`). This is the search side of `parent.article`: pass a hit's `parent` straight back to search within its article. Pass the `identifier` exactly as the listing returned it; a case slip such as `amendment xiv` also matches. Article labels repeat, so `article` needs a `corpusType` from one of those two families, `STATE_CONSTITUTION` also needs `state`, and `STATE` / `REGULATION` need the `code`. A request missing one is refused with 422 before anything is charged. String or list. examples: - Amendment XIV yearFrom: anyOf: - type: integer maximum: 2100 minimum: 1700 - type: 'null' title: Yearfrom description: >- Only return sections dated in or after this year. Combine with `yearTo` for a window. A section matches on the first of three years it carries: the most recent amendment the publisher credits in its own history note; else its effective year, for a section adopted once and never amended; else, for corpora dated by publication rather than amendment (Federal Register proposed rules, agency guidance, adjudications, the treaty record), the document's own publication or issue year. Every one of those tracks the LAW or the document, never when we last rebuilt the corpus. A section carrying none of the three is excluded once either bound is set, so an unbounded search returns strictly more. examples: - 2020 yearTo: anyOf: - type: integer maximum: 2100 minimum: 1700 - type: 'null' title: Yearto description: >- Only return sections dated in or before this year, on the same three years `yearFrom` describes. Note it filters the LAST such date, so a section amended in 2025 is excluded by `yearTo=2024` even though it existed in 2024. This is a currency filter, not point-in-time retrieval: the corpus holds one current text per citation. examples: - 2026 excludeRepealed: type: boolean title: Excluderepealed description: >- Drop sections whose own status says they are no longer operative: repealed, renumbered, transferred, recodified, rescinded, revoked, expired, superseded, omitted, reserved, and the rest of the dead and not-operative vocabulary (the full set is the one behind each result's `goodLawStatus`). **This removes what we KNOW is dead. It does not promise the remainder is good law.** A section survives this filter when its status is `in_force` OR when we hold no trustworthy repeal signal for its jurisdiction, and those two are not the same thing. Read `goodLawStatus` on each surviving result to tell them apart: `good_law` is checked, `unknown` is unchecked. Filtering on the status we store and reporting the verdict we derive are deliberately separate, because only the first is indexable. **The United States Code is served from a stored annual edition** (`year` 2024, `currentThrough` 2025-01-06), so a section repealed after that edition closed still carries `actStatus: in_force` and survives this filter. Every USC result therefore reports `goodLawStatus: unknown`, which is the honest answer and the one this field's second paragraph tells you to read. Use `/section/{actId}/changes` for the timeline on a section you depend on. default: false examples: - true actStatus: anyOf: - type: string enum: - abolished - deleted - expired - in_force - inactive - non_precedential - not_funded - not_yet_effective - omitted - proposed - recodified - recompiled - rejected - relocated - removed - renumbered - repealed - rescinded - reserved - revoked - superseded - terminated - transferred - unconstitutional - vacant - vacated - vetoed - withdrawn - items: type: string enum: - abolished - deleted - expired - in_force - inactive - non_precedential - not_funded - not_yet_effective - omitted - proposed - recodified - recompiled - rejected - relocated - removed - renumbered - repealed - rescinded - reserved - revoked - superseded - terminated - transferred - unconstitutional - vacant - vacated - vetoed - withdrawn type: array - type: 'null' title: Actstatus description: >- Positively scope to one or more raw publisher statuses, e.g. `"repealed"` to find only dead law, or `["in_force"]` for only sections affirmatively marked current. This is the inverse of `excludeRepealed` and is what you want for a compliance diff that asks what was LOST rather than what remains. Values are the `actStatus` returned on each result. Combining a dead status here with `excludeRepealed: true` contradicts itself and is rejected with 422 rather than silently returning nothing. examples: - repealed changedSince: anyOf: - type: string pattern: ^\d{4}-\d{2}-\d{2}$ - type: 'null' format: date title: Changedsince description: >- Only return sections we have OBSERVED change on or after this date (`YYYY-MM-DD`). This is the sync filter: it turns a lookup API into something a nightly job can poll, without creating a board watch per jurisdiction. **These are observed changes, not effective dates.** A refresh compared the publisher against the copy we held and found it different; the date is when we SAW it, an upper bound on when it took effect. It is the same event stream `GET /us/statutes/section/{actId}/changes` serves per section, so a hit here has a history there. **Coverage is bounded by capture, not by the age of the law.** Change capture began long after the corpus did, it is per-source, and events are swept at 5 years. An empty result means no captured change in the window, never that nothing was amended. Narrow with `corpusType` and `state` for a tighter window: the change set is resolved to concrete sections before the search runs, and a window matching too many sections is rejected with a 422 that says so rather than silently truncating your answer. examples: - '2026-08-01' agency: anyOf: - type: string - items: type: string type: array - type: 'null' title: Agency description: >- Federal Register agency slug, e.g. `environmental-protection-agency`. The agency's full name (`Environmental Protection Agency`) or its Federal Register acronym (`EPA`, `e.p.a.`) resolves to the same slug; an acronym the Federal Register gives to more than one agency (`FS`) or a value naming no agency the corpus holds is a 422, never a charge. Pass a list to match any of several. Applies to `FEDERAL_REGISTER` and `EXECUTIVE_ACTION`; other corpora carry no agency, so combining this with them returns nothing. examples: - environmental-protection-agency documentType: anyOf: - type: string enum: - final - proposed - presidential - type: 'null' title: Documenttype description: >- Federal Register document stage: `final` (a rule in force), `proposed` (an NPRM), or `presidential` (a Presidential Document, the `EXECUTIVE_ACTION` corpus). The same distinction appears in each row's `actId` prefix (`FR_RULE_` vs `FR_PRORULE_`). examples: - final publishedFrom: anyOf: - type: string pattern: ^\d{4}-\d{2}-\d{2}$ - type: 'null' format: date title: Publishedfrom description: >- Only return Federal Register documents published on or after this date (`YYYY-MM-DD`). This is the PUBLICATION date, which is not the same as `yearFrom`: that filters the version year of a section. examples: - '2024-01-01' publishedTo: anyOf: - type: string pattern: ^\d{4}-\d{2}-\d{2}$ - type: 'null' format: date title: Publishedto description: >- Only return Federal Register documents published on or before this date. examples: - '2024-12-31' titleNumber: anyOf: - type: integer minimum: 1 - type: 'null' title: Titlenumber description: >- Filter by USC/CFR title number (e.g., 17 for SEC, 42 for civil rights). Only meaningful for `USC`/`CFR`; ignored for state corpora whose titles are alphabetic (e.g. Texas `pe` = Penal Code). examples: - 17 chapter: anyOf: - type: string - items: type: string type: array - type: 'null' title: Chapter description: >- Scope a search to one or more chapters within a title or code, e.g. `21` for USC Title 42 Chapter 21. This is the search-side of the `parent` object on each result: pass a hit's `parent.chapter` straight back to search that hit's neighbors. Chapter numbers repeat across titles, so pair it with `titleNumber` (USC) or `code` (state); an unpaired chapter is rejected. String or list. examples: - '21' part: anyOf: - type: string - items: type: string type: array - type: 'null' title: Part description: >- Scope a search to one or more parts within a title, e.g. `240` for 17 C.F.R. Part 240. The CFR counterpart to `chapter`: pass a hit's `parent.part` straight back to search within that part. Pair it with `titleNumber`; an unpaired part is rejected. String or list. examples: - '240' source: anyOf: - type: string enum: - administrative_guidance - ag_precedent - agency_guidance - bia_precedent - bis_advisory_opinion - cfpb_circular - cfpb_enforcement_action - cfpb_supervisory_guidance - cftc_staff_letter - cms_iom - copyright_circular - copyright_compendium - cpsc_advisory_opinion - cpsc_secg - ddtc_commodity_jurisdiction - ddtc_guidance - dfars - dfars_pgi - doe_appliance_guidance - doj_business_review - doj_justice_manual - doj_leniency - eeoc_guidance - far - fcc_declaratory_ruling - fdic_fil - ferc_policy_statement - fincen_amla_material - fincen_boi_compliance_guide - fincen_boi_faq - fincen_boi_rule_qa - fincen_guidance - fincen_ruling - frap - frb_sr_letter - frbp - frcp - frcrp - fre - ftc_administrative_decision - ftc_advisory_opinion - ftc_advocacy_filing - ftc_hsr_interpretation - ftc_policy_statement - hhs_ocr_hipaa_faq - hhs_ocr_hipaa_guidance - hhs_ocr_resolution_agreement - immigration_admin_precedent - irs_announcement - irs_irm - irs_notice - irs_rev_proc - irs_rev_rul - irs_written_determination - merger_guidelines - mpep - mspb_nonprecedential - mspb_precedential - nlrb_advice_memo - nlrb_board_decision - nlrb_gc_memo - occ_bulletin - occ_interpretive_letter - ofac_faq - olc_opinion - sct - sec_commission_opinion - senate_treaty - senate_treaty_document - senate_treaty_resolution - ssa_ruling - state_financial_bulletin - state_insurance_bulletin - tmep - us_tax_treaty - us_tax_treaty_technical_explanation - uscis_policy_manual - whd_foh - whd_opinion_letter - items: type: string enum: - administrative_guidance - ag_precedent - agency_guidance - bia_precedent - bis_advisory_opinion - cfpb_circular - cfpb_enforcement_action - cfpb_supervisory_guidance - cftc_staff_letter - cms_iom - copyright_circular - copyright_compendium - cpsc_advisory_opinion - cpsc_secg - ddtc_commodity_jurisdiction - ddtc_guidance - dfars - dfars_pgi - doe_appliance_guidance - doj_business_review - doj_justice_manual - doj_leniency - eeoc_guidance - far - fcc_declaratory_ruling - fdic_fil - ferc_policy_statement - fincen_amla_material - fincen_boi_compliance_guide - fincen_boi_faq - fincen_boi_rule_qa - fincen_guidance - fincen_ruling - frap - frb_sr_letter - frbp - frcp - frcrp - fre - ftc_administrative_decision - ftc_advisory_opinion - ftc_advocacy_filing - ftc_hsr_interpretation - ftc_policy_statement - hhs_ocr_hipaa_faq - hhs_ocr_hipaa_guidance - hhs_ocr_resolution_agreement - immigration_admin_precedent - irs_announcement - irs_irm - irs_notice - irs_rev_proc - irs_rev_rul - irs_written_determination - merger_guidelines - mpep - mspb_nonprecedential - mspb_precedential - nlrb_advice_memo - nlrb_board_decision - nlrb_gc_memo - occ_bulletin - occ_interpretive_letter - ofac_faq - olc_opinion - sct - sec_commission_opinion - senate_treaty - senate_treaty_document - senate_treaty_resolution - ssa_ruling - state_financial_bulletin - state_insurance_bulletin - tmep - us_tax_treaty - us_tax_treaty_technical_explanation - uscis_policy_manual - whd_foh - whd_opinion_letter type: array - type: 'null' title: Source description: >- Scope to one or more of the following. The named source within `corpusType`, for corpora that fold several independently filterable bodies of law into one token. `FEDERAL_RULES` sources: `frcp` (Federal Rules of Civil Procedure), `frcrp` (Federal Rules of Criminal Procedure), `fre` (Federal Rules of Evidence), `frap` (Federal Rules of Appellate Procedure), `frbp` (Federal Rules of Bankruptcy Procedure), `sct` (Rules of the Supreme Court of the United States). `CFR` sources: `far` (Federal Acquisition Regulation (48 C.F.R. ch. 1)), `dfars` (Defense Federal Acquisition Regulation Supplement (48 C.F.R. ch. 2)) (both are already part of `CFR`; this only splits the existing Title 48 data by chapter, it does not add new sections). `AGENCY_GUIDANCE` sources: `administrative_guidance` (Synthesized administrative guidance (e.g. SALT cap, CTC, 401(k) limits)), `ssa_ruling` (Social Security Administration Rulings), `irs_rev_proc` (IRS Revenue Procedures), `irs_notice` (IRS Notices), `irs_rev_rul` (IRS Revenue Rulings), `irs_announcement` (IRS Announcements), `irs_irm` (Internal Revenue Manual (IRS internal procedure)), `merger_guidelines` (DOJ & FTC Merger Guidelines (2023)), `doj_leniency` (DOJ Antitrust Division Leniency Policy), `doj_business_review` (DOJ Antitrust Division Business Review Letters (1991-2021)), `cms_iom` (CMS Medicare Internet-Only Manuals (instruction to Medicare contractors, not a regulation)), `copyright_circular` (US Copyright Office Circulars), `copyright_compendium` (Compendium of U.S. Copyright Office Practices, Third Edition (2014, 2017 and 2021 editions)), `doj_justice_manual` (DOJ Justice Manual), `uscis_policy_manual` (USCIS Policy Manual), `mpep` (USPTO Manual of Patent Examining Procedure (MPEP)), `tmep` (USPTO Trademark Manual of Examining Procedure (TMEP)), `cftc_staff_letter` (CFTC Staff Letters (no-action, exemptive, interpretative; 2008-present)), `fincen_ruling` (FinCEN Administrative Rulings), `fincen_guidance` (FinCEN Guidance (alerts, advisories, notices, bulletins, fact sheets)), `fincen_boi_faq` (FinCEN Beneficial Ownership Information FAQs), `fincen_boi_rule_qa` (FinCEN BOI Rulemaking Q&As (final rule and interim final rule)), `fincen_boi_compliance_guide` (FinCEN Small Entity Compliance Guide (Beneficial Ownership Information Reporting)), `fincen_amla_material` (FinCEN Anti-Money Laundering Act of 2020 Implementation Material), `frb_sr_letter` (Federal Reserve Supervision and Regulation (SR) / Consumer Affairs (CA) Letters), `occ_bulletin` (OCC Bulletins), `occ_interpretive_letter` (OCC Interpretive Letters), `fdic_fil` (FDIC Financial Institution Letters (FILs)), `cfpb_supervisory_guidance` (CFPB Supervisory Guidance), `cfpb_circular` (CFPB Consumer Financial Protection Circulars), `dfars_pgi` (DFARS PGI (Procedures, Guidance, and Information)), `ftc_advisory_opinion` (FTC Advisory Opinions), `ftc_policy_statement` (FTC Policy Statements (1967-present)), `ftc_hsr_interpretation` (FTC HSR Premerger Notification Interpretations: the Commission's formal interpretations under 16 C.F.R. 803.30 (1978-2000, a closed series) and the Premerger Notification Office's informal interpretations (1983-present; the publisher serves none from 1997)), `ftc_advocacy_filing` (FTC Advocacy Filings: comments and letters to state legislatures, state courts, governors and other federal agencies on the competition effects of a proposed measure (1985-present). Advisory only: they bind nobody and decide no case), `nlrb_gc_memo` (NLRB General Counsel Memoranda), `nlrb_advice_memo` (NLRB Division of Advice Memoranda (rolling 10-year window, not the full archive)), `cpsc_advisory_opinion` (CPSC Office of General Counsel Advisory Opinions (historical, 1970s-2012)), `cpsc_secg` (CPSC Small Entity Compliance Guides), `whd_opinion_letter` (DOL Wage and Hour Division Opinion, Ruling and Administrator Interpretation Letters (FLSA, FMLA, DBRA, SCA, CCPA, MSPA; 1993-present)), `whd_foh` (DOL Wage and Hour Field Operations Handbook (WHD internal enforcement procedure, not law; 22 chapters)), `bis_advisory_opinion` (BIS (Bureau of Industry and Security) Advisory Opinions), `ddtc_commodity_jurisdiction` (DDTC (Directorate of Defense Trade Controls) Commodity Jurisdiction Determinations), `ddtc_guidance` (DDTC (Directorate of Defense Trade Controls) Policy Guidance Documents), `ofac_faq` (OFAC (Office of Foreign Assets Control) Frequently Asked Questions), `hhs_ocr_hipaa_faq` (HHS Office for Civil Rights HIPAA FAQs), `hhs_ocr_hipaa_guidance` (HHS Office for Civil Rights HIPAA Guidance Materials), `hhs_ocr_resolution_agreement` (HHS Office for Civil Rights HIPAA Resolution Agreements and Civil Money Penalties), `fcc_declaratory_ruling` (FCC (Federal Communications Commission) Declaratory Rulings), `ferc_policy_statement` (FERC (Federal Energy Regulatory Commission) Policy Statements), `doe_appliance_guidance` (DOE Appliance Standards Guidance and FAQs), `eeoc_guidance` (EEOC (Equal Employment Opportunity Commission) Enforcement and Policy Guidance, including Compliance Manual sections), `irs_written_determination` (IRS Written Determinations under 26 U.S.C. § 6110: Private Letter Rulings (PLR), Technical Advice Memoranda (TAM) and Chief Counsel Advice (CCA). Each is directed only to the taxpayer who requested it and, by § 6110(k)(3), may not be used or cited as precedent). `US_TAX_TREATY` sources: `us_tax_treaty` (U.S. Bilateral Income and Estate Tax Treaties), `us_tax_treaty_technical_explanation` (Treasury Technical Explanations (article-by-article commentary on a tax treaty)), `senate_treaty` (Senate Treaty Records (transmittal, parties and proceedings)), `senate_treaty_resolution` (Senate Resolutions of Advice and Consent, including the reservations, understandings and declarations that narrow a treaty's effect in US law), `senate_treaty_document` (Treaty Documents (CDOC TDOC series): the President's message transmitting a treaty to the Senate, with the instrument's text). `STATE_AGENCY_GUIDANCE` sources: `state_insurance_bulletin` (State Department of Insurance Bulletins), `state_financial_bulletin` (State Financial-Institutions Regulator Bulletins (banking, credit unions, trust companies, escrow agents, consumer lenders, money transmitters; AZ and OR only, where that regulator shares an index with the insurance regulator)). `AGENCY_ADJUDICATION` sources: `mspb_precedential` (MSPB Precedential Decisions), `mspb_nonprecedential` (MSPB Nonprecedential Orders), `olc_opinion` (DOJ Office of Legal Counsel Opinions (official bound volumes, 1933-2020)), `cfpb_enforcement_action` (CFPB Enforcement Actions), `sec_commission_opinion` (SEC Commission Opinions and Adjudicatory Orders), `bia_precedent` (BIA Precedent Decisions (I&N Dec.)), `ag_precedent` (Attorney General Immigration Decisions (I&N Dec.)), `immigration_admin_precedent` (INS and USCIS Administrative Precedent Decisions (I&N Dec.)), `nlrb_board_decision` (NLRB Board Decisions (bounded window; see coverage.mdx for the exact years covered)), `ftc_administrative_decision` (FTC Part 3 Administrative Decisions). Every result carries its own `source`, so you can pass a hit's value straight back. An unrecognized value is rejected with 422. examples: - sct fields: anyOf: - items: type: string enum: - abstract - actId - actStatus - action - adoptedAfterCurrentThrough - adoptingCitations - agencies - agencySlugs - alternateCitations - amendmentHistory - amendmentNote - amendmentYears - amendmentsCount - articleName - articleNumber - audience - body - breadcrumb - caseName - chapter - chapterName - citation - citationShort - committeeNote - corpusType - court - crossReferencesCfr - crossReferencesUsc - currencyNote - currencyYear - currentThrough - datesText - displayLabel - displayPath - documentNumber - documentSubtype - documentTypeLabel - docxUrl - edition - effectiveDate - effectiveDateRaw - excerpt - expirationDate - expirationDateRaw - externalUrl - federalRegisterCitations - forum - frCommentsCloseOn - frCorrectionOf - frCorrections - frDocketIds - frEffectiveOn - frEndPage - frRegulationIdNumbers - frRegulationsDotGovUrl - frRelatedDocuments - frSignificant - frStartPage - frVolume - goodLawStatus - govInfoHtmlUrl - govInfoPdfUrl - granuleId - history - historyEffectiveDate - htmlUrl - implementingRegulations - issueDate - issueDateRaw - issuingAgency - languageCode - lastAmendedDate - lastAmendedDateRaw - lastAmendedYear - lawImplemented - licenseNote - originalEnactmentDate - originalEnactmentDateRaw - packageId - parent - part - partName - pdfUrl - pendingAdoptions - popularName - president - priorEffectiveDates - program - publicLawCites - publicLaws - publicationDate - publicationDateRaw - publisherKey - referencedShortTitles - relatedCitations - relatedDocuments - releaseDate - releaseDateRaw - relevanceScore - renumberedTo - renumberedToLabel - requesters - rescindedOn - rescindedOnRaw - reviewDate - reviewDateRaw - ruleSet - ruleSetCode - sectionNumber - sectionTitle - settlementAmount - signingDate - signingDateRaw - source - sourceCharEnd - sourceCharStart - sourceCredit - sourceNote - sourcePageEnd - sourcePageStart - sourceUrl - state - stateHtmlUrl - statutoryAuthority - subchapter - subchapterName - subject - subjectNumber - subpart - subpartName - subtitle - subtitleName - supersededBy - supersedes - supersessionActions - textUrl - title - titleName - titleNumber - topLevelTitle - topics - transferredTo - transferredToLabel - versionId - volume - wordCount - xmlUrl - year type: array uniqueItems: true - items: type: string enum: - abstract - actId - actStatus - action - adoptedAfterCurrentThrough - adoptingCitations - agencies - agencySlugs - alternateCitations - amendmentHistory - amendmentNote - amendmentYears - amendmentsCount - articleName - articleNumber - audience - body - breadcrumb - caseName - chapter - chapterName - citation - citationShort - committeeNote - corpusType - court - crossReferencesCfr - crossReferencesUsc - currencyNote - currencyYear - currentThrough - datesText - displayLabel - displayPath - documentNumber - documentSubtype - documentTypeLabel - docxUrl - edition - effectiveDate - effectiveDateRaw - excerpt - expirationDate - expirationDateRaw - externalUrl - federalRegisterCitations - forum - frCommentsCloseOn - frCorrectionOf - frCorrections - frDocketIds - frEffectiveOn - frEndPage - frRegulationIdNumbers - frRegulationsDotGovUrl - frRelatedDocuments - frSignificant - frStartPage - frVolume - goodLawStatus - govInfoHtmlUrl - govInfoPdfUrl - granuleId - history - historyEffectiveDate - htmlUrl - implementingRegulations - issueDate - issueDateRaw - issuingAgency - languageCode - lastAmendedDate - lastAmendedDateRaw - lastAmendedYear - lawImplemented - licenseNote - originalEnactmentDate - originalEnactmentDateRaw - packageId - parent - part - partName - pdfUrl - pendingAdoptions - popularName - president - priorEffectiveDates - program - publicLawCites - publicLaws - publicationDate - publicationDateRaw - publisherKey - referencedShortTitles - relatedCitations - relatedDocuments - releaseDate - releaseDateRaw - relevanceScore - renumberedTo - renumberedToLabel - requesters - rescindedOn - rescindedOnRaw - reviewDate - reviewDateRaw - ruleSet - ruleSetCode - sectionNumber - sectionTitle - settlementAmount - signingDate - signingDateRaw - source - sourceCharEnd - sourceCharStart - sourceCredit - sourceNote - sourcePageEnd - sourcePageStart - sourceUrl - state - stateHtmlUrl - statutoryAuthority - subchapter - subchapterName - subject - subjectNumber - subpart - subpartName - subtitle - subtitleName - supersededBy - supersedes - supersessionActions - textUrl - title - titleName - titleNumber - topLevelTitle - topics - transferredTo - transferredToLabel - versionId - volume - wordCount - xmlUrl - year type: array - type: 'null' title: Fields description: >- Return only these result fields, e.g. `["title", "excerpt"]`. A result carries 40+ fields and most are null on any given row, so a full page of 50 ships a lot of nulls. `actId` and `citation` are always included, because a row without them cannot be used or attributed. Unknown names are rejected with 422 so a typo does not silently drop a field you needed. Omit for the full object. examples: - - title - excerpt - state limit: type: integer maximum: 50 minimum: 1 title: Limit description: Number of results to return per page. default: 10 offset: type: integer maximum: 70 minimum: 0 title: Offset description: >- How many results to skip, for paging. Every page of a given query is cut from one ranking, so results never repeat or go missing between pages, and a later page costs no more than the first. The deepest reachable result is `offset` + `limit`; check `hasMore` to know when there is nothing further. default: 0 includeBody: type: boolean title: Includebody description: >- Return the full text of every hit inline, on each result's `body`, instead of making you fetch it per section afterwards. **Why it exists.** Search returns a ranking preview, so the alternative is a search call plus one `/section/{actId}/body` call per hit. This collapses a whole page to a single round trip. **Cost**: the 4-credit search PLUS the ordinary 6-credit body price for each row that actually returns text. Ten rows with text is 4 + 60 = 64 credits. A row whose text cannot be resolved comes back with `body: null` and is NOT charged, so read `creditsConsumed` rather than computing it from `limit` -- it is the same price as fetching them yourself, so this buys latency, not a discount. ⚠️ It multiplies with `limit`. `limit: 50` with this set is 304 credits in a single call. Page deliberately. Prefer this over raising `excerptChars`: the excerpt is windowed around the match and can begin mid-section, dropping a leading subsection marker, so it is not safe to quote. `body` is the publisher's text. default: false examples: - true excerptChars: type: integer maximum: 4000 minimum: 100 title: Excerptchars description: >- Characters of matching text to include in each result's `excerpt`. The excerpt is a ranking preview; use `/us/statutes/section/{actId}/body` for the full text. Default 500. default: 500 matchType: type: string enum: - any - all - phrase title: Matchtype description: >- Controls exact vs. semantic matching, so there is no need for a separate keyword-only search mode. `any` (default) is hybrid semantic + keyword ranking and suits natural-language questions. Use `all` for strict keyword matching (every query word must appear in the text) or `phrase` for an exact-phrase match (the query's words, contiguous and in order), e.g. a defined term or a statutory phrase, when you want lexical precision. Both match WHOLE words, case-insensitively, ignoring punctuation: `act` does not match `fact`, `10b-5` matches `10b 5`, and `§ 1983` matches `section 1983`. To pull up one specific section, pass its citation as the query (e.g. `42 U.S.C. § 1983`, `Cal. Civ. Code § 1950.5`) and it resolves to that section at rank 1. default: any examples: - phrase additionalProperties: false type: object required: - query title: StatuteSearchRequest example: corpusType: STATE limit: 5 matchType: any query: data breach notification deadline state: ca StatuteSearchResponse: properties: results: items: $ref: '#/components/schemas/StatuteResult' type: array title: Results description: >- Matching sections, most relevant first. Ordering is by relevance, not statutory order; use `/us/statutes/section/{actId}/related` for what sits either side of a section in its code. count: type: integer title: Count description: >- How many results came back in THIS response, i.e. the length of `results`. It is not a total match count: the API ranks a bounded set of candidates rather than scoring the whole corpus, so no such total exists. Use `hasMore` to decide whether to ask for another page. default: 0 total: type: integer title: Total description: >- DEPRECATED alias for `count`, kept for backward compatibility. The name reads as a corpus-wide match total, which it never was. Use `count` instead. default: 0 deprecated: true offset: type: integer title: Offset description: The offset applied to this page. default: 0 hasMore: type: boolean title: Hasmore description: Whether more results exist beyond this page. default: false changedSectionCount: anyOf: - type: integer - type: 'null' title: Changedsectioncount description: >- Only present when `changedSince` is set: how many sections changed in that window, before ranking. Compare it against `count`. `changedSince` is a filter on a RANKED search, so a window holding more sections than one query can return is normal and the page you get is the most relevant slice of it, not all of it. When this number is larger than you can page to, the filter is a trigger rather than an inventory: subscribe to the board and poll `GET /watches/{id}/changes`, which is complete and costs no credits. examples: - 19055 rankingDegraded: type: boolean title: Rankingdegraded description: >- True when the relevance model (a cross-encoder) was unavailable and the results are in hybrid-retrieval order instead. The sections are still real matches for the query, but the ordering is coarser and `relevanceScore` is a retrieval score rather than a 0-1 relevance, so do not threshold on it. Such a ranking is never cached: retrying shortly returns the fully ranked result once the model recovers. default: false examples: - false noGoodMatch: anyOf: - type: boolean - type: 'null' title: Nogoodmatch description: >- True when nothing in the corpus looks on point for this query. It says nothing about whether the top result is the right section; check its citation and jurisdiction. False when the top result clears the relevance bar, or when the query is a citation or a section number that matched exactly. Null when `rankingDegraded` is true, because the bar is on the relevance model's scale. The same on every page of a query. examples: - false matchQuality: anyOf: - type: string enum: - exact - strong - moderate - weak - none - type: 'null' title: Matchquality description: >- How strongly the evidence says result #1 answers the query. exact: a citation or section-number match. strong: the top result was correct about 94% of the time in our measurements (about 91% on questions whose answer is a statute or regulation). moderate: about 67%. weak: about 35%. none: nothing on point (same as noGoodMatch). Measured on our labelled evaluation set; tiers may be re-cut as the index changes, so treat unknown values as moderate. Null when `rankingDegraded` is true. The same on every page of a query. examples: - strong citationOutsideFilters: anyOf: - $ref: '#/components/schemas/CitationOutsideFilters' - type: 'null' description: >- Your query is a citation to a real section that your filters exclude. To read it, retry without the filters named in `excludedBy`, or call `GET /us/statutes/resolve` without them. Null when the query is not a citation, when the citation is inside your filters (it then ranks first), or when it names no section we hold. `results` are unchanged: a filter is a promise, so the section is reported here and not forced into the results. The same on every page of a query. citationMissReason: anyOf: - $ref: '#/components/schemas/CitationMissReason' - type: 'null' description: >- Present only when the whole query is a citation that did not resolve to a section, so the results are an ordinary search and not the section it names. `missReason` says why (`not_held`, `former_law`, `ambiguous_jurisdiction`, `out_of_scope_corpus`), `missReasonHint` what to try, and `candidates` the held sections an ambiguous citation could mean. Absent for a question, for a citation that resolved, and when `citationOutsideFilters` already explains it. `malformed` is never reported here: a free-text question is not malformed. The same on every page of a query. No extra charge. query: type: string title: Query description: The search query used. default: '' processingTimeMs: type: number title: Processingtimems description: >- Server-side time for this request in milliseconds, excluding network transit. Useful for spotting a slow query; not billed on. default: 0 examples: - 240.5 creditsConsumed: type: number title: Creditsconsumed description: >- Credits actually charged for this call. Read it rather than assuming the list price: failed and refunded work bills 0, and batch endpoints charge per item returned, so a partial result costs less than a full one. default: 0 examples: - 4 type: object title: StatuteSearchResponse ApiDetailError: properties: detail: type: string title: Detail description: >- Human-readable reason, safe to surface to an end user. Branch on the HTTP status rather than on this string: the wording is not part of the contract and may be reworded, but 401 (bad key), 402 (out of credits), 403 (missing scope), 404 (no such resource) and 429 (rate limited) are stable. examples: - Insufficient API credits. errors: anyOf: - items: $ref: '#/components/schemas/ApiFieldError' type: array - type: 'null' title: Errors description: 'Present on 422 only: every field that failed validation.' type: object required: - detail title: ApiDetailError description: >- Error envelope the API actually returns. Every error (400/401/402/403/404/405/422/429/5xx) carries a `detail` string, e.g. `{"detail": "Insufficient API credits."}`, on every mount of the API. A 422 adds `errors`, one entry per rejected field. Some 404s add endpoint-specific diagnosis beside `detail` (the statutes section routes add `actId`, `reason` and `didYouMean`); treat unknown keys as optional. StatuteResult: properties: actId: type: string title: Actid description: >- Unique section identifier (e.g., 'USC_T42_C21_S1983', 'CFR_T17_P240_S240_10b5_1'). citation: anyOf: - type: string - type: 'null' title: Citation description: >- Full citation (e.g., '42 U.S.C. § 1983 (2024)', '17 C.F.R. § 240.10b5-1 (2026)'). citationShort: anyOf: - type: string - type: 'null' title: Citationshort description: Short citation (e.g., '42 U.S.C. § 1983', '17 C.F.R. § 240.10b5-1'). title: anyOf: - type: string - type: 'null' title: Title description: Section title. corpusType: anyOf: - type: string - type: 'null' title: Corpustype description: >- One of `USC`, `CFR`, `STATE`, `CONSTITUTION`, `FEDERAL_RULES`, `STATE_CONSTITUTION`, `STATE_RULES`, or `EXECUTIVE_ACTION`. state: anyOf: - type: string - type: 'null' title: State description: >- 2-letter lowercase state code (e.g. `ca`, `tx`) when the row belongs to a state corpus. `federal` for federal rows. source: anyOf: - type: string - type: 'null' title: Source description: >- The named source within `corpusType`, for corpora that fold several independently filterable bodies of law into one token. `FEDERAL_RULES` sources: `frcp` (Federal Rules of Civil Procedure), `frcrp` (Federal Rules of Criminal Procedure), `fre` (Federal Rules of Evidence), `frap` (Federal Rules of Appellate Procedure), `frbp` (Federal Rules of Bankruptcy Procedure), `sct` (Rules of the Supreme Court of the United States). `CFR` sources: `far` (Federal Acquisition Regulation (48 C.F.R. ch. 1)), `dfars` (Defense Federal Acquisition Regulation Supplement (48 C.F.R. ch. 2)) (both are already part of `CFR`; this only splits the existing Title 48 data by chapter, it does not add new sections). `AGENCY_GUIDANCE` sources: `administrative_guidance` (Synthesized administrative guidance (e.g. SALT cap, CTC, 401(k) limits)), `ssa_ruling` (Social Security Administration Rulings), `irs_rev_proc` (IRS Revenue Procedures), `irs_notice` (IRS Notices), `irs_rev_rul` (IRS Revenue Rulings), `irs_announcement` (IRS Announcements), `irs_irm` (Internal Revenue Manual (IRS internal procedure)), `merger_guidelines` (DOJ & FTC Merger Guidelines (2023)), `doj_leniency` (DOJ Antitrust Division Leniency Policy), `doj_business_review` (DOJ Antitrust Division Business Review Letters (1991-2021)), `cms_iom` (CMS Medicare Internet-Only Manuals (instruction to Medicare contractors, not a regulation)), `copyright_circular` (US Copyright Office Circulars), `copyright_compendium` (Compendium of U.S. Copyright Office Practices, Third Edition (2014, 2017 and 2021 editions)), `doj_justice_manual` (DOJ Justice Manual), `uscis_policy_manual` (USCIS Policy Manual), `mpep` (USPTO Manual of Patent Examining Procedure (MPEP)), `tmep` (USPTO Trademark Manual of Examining Procedure (TMEP)), `cftc_staff_letter` (CFTC Staff Letters (no-action, exemptive, interpretative; 2008-present)), `fincen_ruling` (FinCEN Administrative Rulings), `fincen_guidance` (FinCEN Guidance (alerts, advisories, notices, bulletins, fact sheets)), `fincen_boi_faq` (FinCEN Beneficial Ownership Information FAQs), `fincen_boi_rule_qa` (FinCEN BOI Rulemaking Q&As (final rule and interim final rule)), `fincen_boi_compliance_guide` (FinCEN Small Entity Compliance Guide (Beneficial Ownership Information Reporting)), `fincen_amla_material` (FinCEN Anti-Money Laundering Act of 2020 Implementation Material), `frb_sr_letter` (Federal Reserve Supervision and Regulation (SR) / Consumer Affairs (CA) Letters), `occ_bulletin` (OCC Bulletins), `occ_interpretive_letter` (OCC Interpretive Letters), `fdic_fil` (FDIC Financial Institution Letters (FILs)), `cfpb_supervisory_guidance` (CFPB Supervisory Guidance), `cfpb_circular` (CFPB Consumer Financial Protection Circulars), `dfars_pgi` (DFARS PGI (Procedures, Guidance, and Information)), `ftc_advisory_opinion` (FTC Advisory Opinions), `ftc_policy_statement` (FTC Policy Statements (1967-present)), `ftc_hsr_interpretation` (FTC HSR Premerger Notification Interpretations: the Commission's formal interpretations under 16 C.F.R. 803.30 (1978-2000, a closed series) and the Premerger Notification Office's informal interpretations (1983-present; the publisher serves none from 1997)), `ftc_advocacy_filing` (FTC Advocacy Filings: comments and letters to state legislatures, state courts, governors and other federal agencies on the competition effects of a proposed measure (1985-present). Advisory only: they bind nobody and decide no case), `nlrb_gc_memo` (NLRB General Counsel Memoranda), `nlrb_advice_memo` (NLRB Division of Advice Memoranda (rolling 10-year window, not the full archive)), `cpsc_advisory_opinion` (CPSC Office of General Counsel Advisory Opinions (historical, 1970s-2012)), `cpsc_secg` (CPSC Small Entity Compliance Guides), `whd_opinion_letter` (DOL Wage and Hour Division Opinion, Ruling and Administrator Interpretation Letters (FLSA, FMLA, DBRA, SCA, CCPA, MSPA; 1993-present)), `whd_foh` (DOL Wage and Hour Field Operations Handbook (WHD internal enforcement procedure, not law; 22 chapters)), `bis_advisory_opinion` (BIS (Bureau of Industry and Security) Advisory Opinions), `ddtc_commodity_jurisdiction` (DDTC (Directorate of Defense Trade Controls) Commodity Jurisdiction Determinations), `ddtc_guidance` (DDTC (Directorate of Defense Trade Controls) Policy Guidance Documents), `ofac_faq` (OFAC (Office of Foreign Assets Control) Frequently Asked Questions), `hhs_ocr_hipaa_faq` (HHS Office for Civil Rights HIPAA FAQs), `hhs_ocr_hipaa_guidance` (HHS Office for Civil Rights HIPAA Guidance Materials), `hhs_ocr_resolution_agreement` (HHS Office for Civil Rights HIPAA Resolution Agreements and Civil Money Penalties), `fcc_declaratory_ruling` (FCC (Federal Communications Commission) Declaratory Rulings), `ferc_policy_statement` (FERC (Federal Energy Regulatory Commission) Policy Statements), `doe_appliance_guidance` (DOE Appliance Standards Guidance and FAQs), `eeoc_guidance` (EEOC (Equal Employment Opportunity Commission) Enforcement and Policy Guidance, including Compliance Manual sections), `irs_written_determination` (IRS Written Determinations under 26 U.S.C. § 6110: Private Letter Rulings (PLR), Technical Advice Memoranda (TAM) and Chief Counsel Advice (CCA). Each is directed only to the taxpayer who requested it and, by § 6110(k)(3), may not be used or cited as precedent). `US_TAX_TREATY` sources: `us_tax_treaty` (U.S. Bilateral Income and Estate Tax Treaties), `us_tax_treaty_technical_explanation` (Treasury Technical Explanations (article-by-article commentary on a tax treaty)), `senate_treaty` (Senate Treaty Records (transmittal, parties and proceedings)), `senate_treaty_resolution` (Senate Resolutions of Advice and Consent, including the reservations, understandings and declarations that narrow a treaty's effect in US law), `senate_treaty_document` (Treaty Documents (CDOC TDOC series): the President's message transmitting a treaty to the Senate, with the instrument's text). `STATE_AGENCY_GUIDANCE` sources: `state_insurance_bulletin` (State Department of Insurance Bulletins), `state_financial_bulletin` (State Financial-Institutions Regulator Bulletins (banking, credit unions, trust companies, escrow agents, consumer lenders, money transmitters; AZ and OR only, where that regulator shares an index with the insurance regulator)). `AGENCY_ADJUDICATION` sources: `mspb_precedential` (MSPB Precedential Decisions), `mspb_nonprecedential` (MSPB Nonprecedential Orders), `olc_opinion` (DOJ Office of Legal Counsel Opinions (official bound volumes, 1933-2020)), `cfpb_enforcement_action` (CFPB Enforcement Actions), `sec_commission_opinion` (SEC Commission Opinions and Adjudicatory Orders), `bia_precedent` (BIA Precedent Decisions (I&N Dec.)), `ag_precedent` (Attorney General Immigration Decisions (I&N Dec.)), `immigration_admin_precedent` (INS and USCIS Administrative Precedent Decisions (I&N Dec.)), `nlrb_board_decision` (NLRB Board Decisions (bounded window; see coverage.mdx for the exact years covered)), `ftc_administrative_decision` (FTC Part 3 Administrative Decisions). Pass it back as the `source` search filter to scope to just this one source. Null for corpora with only one source, which includes every state's statutes and regulations. Not a link, and not where the text came from: it is a filter token. The official link to the publisher's text is `sourceUrl`. examples: - sct year: anyOf: - type: integer - type: 'null' title: Year description: >- The year this row was ingested, not the year of the law. Most ingesters stamp the capture year (`time.gmtime().tm_year`) and a few pin a literal, so the bulk of the corpus reads the year it was captured. **Do not filter or reason about currency with it.** `lastAmendedYear` carries the amendment year, `currentThrough` and `currencyNote` carry the publisher's own currency statement, and `goodLawStatus` carries the status. relevanceScore: anyOf: - type: number - type: 'null' title: Relevancescore description: >- Relevance score, normalized to roughly 0-1. Higher means a better match for ranking within one response. It is a relative ranking signal, not a calibrated confidence or probability, so do not compare scores across different queries or treat a fixed value as a quality threshold. Exception: a query that resolves to an exact citation (e.g. '42 U.S.C. § 1983', 'Cal. Civ. Code § 1950.5', 'Fed. R. Civ. P. 12') always scores that section 1.0, since it is a certain match rather than a ranked one -- a natural-language or keyword query never returns 1.0 by comparison. **null on any endpoint that did not rank**: fetching a section by id, a batch fetch, or a section embedded in an intelligence response. When the response carries `rankingDegraded: true`, the relevance model was unavailable and this is a retrieval score on a different, much smaller scale: still a valid ORDER, not a 0-1 relevance. excerpt: type: string title: Excerpt description: Text excerpt (up to 500 characters). default: '' body: anyOf: - type: string - type: 'null' title: Body description: >- Full plain text of the section. Present ONLY when the request set `includeBody: true`, and null on any row whose text could not be resolved (those rows are not charged for a body). This is the actual statutory text, not the `excerpt`. The two are different things and the difference matters for quoting: `excerpt` is a ranking preview windowed around the match, so it can begin mid-section and drop a leading subsection marker -- measured 2026-09-02, four of five California rows lost their opening `(a) `. `body` is the document as the publisher printed it. examples: - (a) If within a reasonable time after written or oral notice... titleNumber: anyOf: - type: string - type: 'null' title: Titlenumber description: USC/CFR/state title number (e.g. '26', '13A'). titleName: anyOf: - type: string - type: 'null' title: Titlename description: Title name (e.g., 'The Public Health and Welfare'). chapter: anyOf: - type: string - type: 'null' title: Chapter description: Chapter number or identifier. chapterName: anyOf: - type: string - type: 'null' title: Chaptername description: Chapter name. sectionNumber: anyOf: - type: string - type: 'null' title: Sectionnumber description: Section number (e.g., '1983', '240.10b5-1'). sectionTitle: anyOf: - type: string - type: 'null' title: Sectiontitle description: >- The section's own heading (e.g., 'Rule G. Forfeiture Actions In Rem'). Distinct from `title`, which is the hierarchical display path. displayPath: anyOf: - type: string - type: 'null' title: Displaypath description: Full hierarchical path (Title > Chapter > Section). breadcrumb: anyOf: - items: additionalProperties: type: string type: object type: array - type: 'null' title: Breadcrumb description: Structured breadcrumb trail for navigation. parent: anyOf: - additionalProperties: true type: object - type: 'null' title: Parent description: >- Query for `GET /us/statutes/divisions` that lists this section's siblings (its containing chapter, part, code, article or federal rule set). Pass it straight back to walk up the hierarchy, or spread it into a `POST /us/statutes/search` body to search within that container: every key it carries is also a search filter. Null when the container cannot be determined. subchapter: anyOf: - type: string - type: 'null' title: Subchapter description: Subchapter number or identifier. subchapterName: anyOf: - type: string - type: 'null' title: Subchaptername description: Subchapter name. part: anyOf: - type: string - type: 'null' title: Part description: Part number or identifier (CFR/state). partName: anyOf: - type: string - type: 'null' title: Partname description: Part name. subpart: anyOf: - type: string - type: 'null' title: Subpart description: Subpart number or identifier (CFR). subpartName: anyOf: - type: string - type: 'null' title: Subpartname description: Subpart name. popularName: anyOf: - type: string - type: 'null' title: Popularname description: >- Popular/common name of the act (e.g. 'Truth in Lending Act'), when known. actStatus: anyOf: - type: string - type: 'null' title: Actstatus description: >- Raw section status: `in_force`, `repealed`, `renumbered`, `transferred`, `omitted`, `reserved`, `vacant`, or `unconstitutional`. goodLawStatus: anyOf: - type: string - type: 'null' title: Goodlawstatus description: >- Derived currency verdict: `good_law`, `not_good_law`, `not_operative`, or `unknown`. Conservative: states without a reliable repeal signal report `unknown` rather than over-claiming. `null` when currency checking is disabled. currencyNote: anyOf: - type: string - type: 'null' title: Currencynote description: Source's 'current through ...' note, when published. renumberedTo: anyOf: - type: string - type: 'null' title: Renumberedto description: >- Where the publisher says this section went, when `actStatus` is `renumbered`. RAW SOURCE FORM, not an `actId` and not a citation: `self:4651` means section 4651 of this same title, `34:10105` means section 10105 of Title 34. Do not pass it to a section endpoint. Read `renumberedToLabel` instead, or resolve the citation it names through `/us/statutes/resolve`. examples: - self:4651 renumberedToLabel: anyOf: - type: string - type: 'null' title: Renumberedtolabel description: >- `renumberedTo` written out, e.g. `section 10105 of Title 34`. Present whenever `renumberedTo` is. examples: - section 10105 of Title 34 transferredTo: anyOf: - type: string - type: 'null' title: Transferredto description: >- Where the publisher says this section went, when `actStatus` is `transferred`. Same raw source form as `renumberedTo`, and the same warning: it is not an `actId`. examples: - '34:10105' transferredToLabel: anyOf: - type: string - type: 'null' title: Transferredtolabel description: '`transferredTo` written out. Present whenever `transferredTo` is.' examples: - section 10105 of Title 34 issueDate: anyOf: - type: string - type: 'null' title: Issuedate description: >- Issue/publication date of this version, as `YYYY-MM-DD`, when known. See `issueDateRaw` for the publisher's wording on the rare source that does not print ISO. examples: - '1999-05-25' issueDateRaw: anyOf: - type: string - type: 'null' title: Issuedateraw description: >- The issue date as the publisher writes it, present only when it differs from `issueDate`. Null across the corpus today; it exists so a source that starts printing prose cannot silently put prose in a field documented as a date. crossReferencesCfr: anyOf: - items: type: string type: array - type: 'null' title: Crossreferencescfr description: CFR cross-references parsed from the text, e.g. `['1.6011-4']`. crossReferencesUsc: anyOf: - items: type: string type: array - type: 'null' title: Crossreferencesusc description: >- USC cross-references parsed from the text, e.g. `['42:1983']`. `'self:
'` denotes a reference to another section of the same title. statutoryAuthority: anyOf: - items: additionalProperties: true type: object type: array - type: 'null' title: Statutoryauthority description: >- For a CFR/eCFR section: the USC (or other) citations in its 'Authority' note that authorize the rule, e.g. `[{'type': 'usc', 'title': 15, 'section': '78o', 'display': '15 U.S.C. 78o'}]`. Null for non-regulation corpora. implementingRegulations: anyOf: - items: additionalProperties: true type: object type: array - type: 'null' title: Implementingregulations description: >- For a USC section: the CFR parts that implement it, derived from the reverse of every CFR section's own `statutoryAuthority`, e.g. `[{'cfrTitle': 17, 'part': '240', 'partName': '...', 'display': '17 CFR Part 240'}]`. Null for non-USC corpora. frRegulationIdNumbers: anyOf: - items: type: string type: array - type: 'null' title: Frregulationidnumbers description: Regulation Identifier Number(s) (RIN) assigned to this rule. frDocketIds: anyOf: - items: type: string type: array - type: 'null' title: Frdocketids description: Rulemaking docket ID(s) this document was filed under. frEffectiveOn: anyOf: - type: string - type: 'null' title: Freffectiveon description: The rule's effective date (ISO 8601 date), when set. frCommentsCloseOn: anyOf: - type: string - type: 'null' title: Frcommentscloseon description: Public-comment deadline (ISO 8601 date). Proposed rules only. frSignificant: anyOf: - type: boolean - type: 'null' title: Frsignificant description: >- Whether the Federal Register marked this rule 'economically significant' (EO 12866). frCorrectionOf: anyOf: - type: string - type: 'null' title: Frcorrectionof description: >- Federal Register document number this document corrects, when this is a correction. frCorrections: anyOf: - items: type: string type: array - type: 'null' title: Frcorrections description: >- Federal Register document number(s) that later corrected this document. frRegulationsDotGovUrl: anyOf: - type: string - type: 'null' title: Frregulationsdotgovurl description: Link to this document's public comment docket on regulations.gov. frRelatedDocuments: anyOf: - items: $ref: '#/components/schemas/FrRelatedDocument' type: array - type: 'null' title: Frrelateddocuments description: >- Other Federal Register documents sharing this document's RIN(s) (its proposed rule, its final rule, and any corrections), most recent first. Only populated on `GET /us/statutes/section/{actId}` for a row that carries `frRegulationIdNumbers`; always null on `/us/statutes/search` results, since computing it needs a follow-up lookup that is too expensive to run per search result. subject: anyOf: - type: string - type: 'null' title: Subject description: >- The publisher's own subject or document-type label, where it prints one (for example a state insurance bulletin's `RE:` line, or its listing category such as `Rescission`). rescindedOn: anyOf: - type: string - type: 'null' title: Rescindedon description: >- The date the document was rescinded or withdrawn, as `YYYY-MM-DD`, when the source states one. See `rescindedOnRaw`. examples: - '2016-07-01' rescindedOnRaw: anyOf: - type: string - type: 'null' title: Rescindedonraw description: >- The rescission date as the publisher writes it, present only when it differs from `rescindedOn`. sourceCredit: anyOf: - type: string - type: 'null' title: Sourcecredit description: >- The Office of the Law Revision Counsel's credit line for a **USC** section: the acts that enacted and amended it, in order, e.g. `June 25, 1948, ch. 646, 62 Stat. 869; Pub. L. 85-508, Sec. 12, July 7, 1958, 72 Stat. 348`. Parentheses stripped, whitespace normalized. USC only, and null on a USC section that prints no credit (a transferred, repealed or reclassified stub). CFR sections carry the same fact as a list in `federalRegisterCitations` instead, which is why the shape differs; no other corpus publishes one. amendmentYears: anyOf: - items: type: integer type: array - type: 'null' title: Amendmentyears description: >- Distinct years the section was amended, parsed from the publisher's history note. **Always newest first, and de-duplicated.** Ingesters store the array in both orders (eCFR writes newest first, state regulations and state statutes write oldest first), so the order is imposed at serve time and the served order is the only one to rely on. Years outside 1789..(current year) are dropped rather than served: amendment dates are parsed out of prose and a note can yield a sunset or substitution date that is not an amendment at all. lastAmendedYear: anyOf: - type: integer - type: 'null' title: Lastamendedyear description: >- Most recent amendment year, when known. Re-derived at serve time as `max(amendmentYears)`, so it never exceeds the list served beside it. Falls back to the publisher's own scalar only when `amendmentYears` is empty, and only when that scalar is itself within 1789..(current year). amendmentsCount: anyOf: - type: integer - type: 'null' title: Amendmentscount description: >- How many amendments the publisher recorded for this section. **Not the length of `amendmentYears`, and it is not safe to derive one from the other.** For regulations and court rules this counts amending EVENTS: one per register citation, filing or history entry, so a section amended twice in the same year counts 2 against a single entry in `amendmentYears`. The two disagree on a large share of the regulation and court-rule corpora, so read each for what it is. For the other corpora, and for any source that publishes no per-event record, it falls back to the number of distinct years, which understates a section amended twice in one year. currentThrough: anyOf: - type: string - type: 'null' title: Currentthrough description: >- The date the publisher states this text is current through, e.g. `2025-01-06`. Set on every USC section. `currencyNote` carries the same fact as prose where a publisher writes it that way. pendingAdoptions: anyOf: - items: additionalProperties: true type: object type: array - type: 'null' title: Pendingadoptions description: >- New York only. Register ADOPTION NOTICES that post-date the print volume this section's text was taken from. They are NOTICES from the NY State Register, NOT an updated consolidated text: `text` and `body` are unchanged and still reflect `currentThrough` / `currencyNote`. Read each entry as "the State Register announced an adoption naming this section, or the Part that contains it, after the text we serve was current", and look the notice up in the State Register by its `idNo`. Each entry: `idNo` (the Register I.D. No., e.g. `DFS-23-26-00013-A`), `scope` (`section` when the notice names this section, `part` when it names the Part containing it and says nothing about this section alone), `effectiveDate` (ISO date the adoption takes effect, null if the notice states none), `agency`, `issueDate` (ISO date of the Register issue). We do not return a link to the notice: the Register is hosted on a commercial platform and, as with `sourceUrl` on these regulations, the link is withheld under licence. Only adoptions (`-A`, and `-AA` amended notices of adoption) are listed, never proposals, emergency rules or withdrawals. Null on every section with no such notice, which is NOT a statement that the section is current: we cover Register adoptions for NYCRR Titles 3, 19 and 23 only. examples: - - agency: Department of Financial Services effectiveDate: '2026-09-23' idNo: DFS-23-26-00013-A issueDate: '2026-09-23' scope: part adoptedAfterCurrentThrough: anyOf: - type: boolean - type: 'null' title: Adoptedaftercurrentthrough description: >- New York only. True when `pendingAdoptions` is non-empty, i.e. the State Register records at least one adoption naming this section or its Part that post-dates the volume `currentThrough` refers to, so the text served may be out of date. Null (never false) when no such adoption is recorded; null is not a claim that the text is current. examples: - true amendmentHistory: anyOf: - items: type: string type: array - type: 'null' title: Amendmenthistory description: >- Structured amendment entries where the publisher records them separately from the credit line in `history`. sourceNote: anyOf: - type: string - type: 'null' title: Sourcenote description: The publisher's source note for the section, verbatim. effectiveDate: anyOf: - type: string - type: 'null' title: Effectivedate description: >- When THIS version took effect, as `YYYY-MM-DD`, or null when the publisher's own string does not name one unambiguous day we can read without guessing. On a section with `actStatus=superseded` this is the start of that version's window. The publisher's wording is preserved in `effectiveDateRaw` whenever it differs. examples: - '2002-11-25' effectiveDateRaw: anyOf: - type: string - type: 'null' title: Effectivedateraw description: >- The date exactly as the publisher writes it, present only when it differs from `effectiveDate`. A section whose publisher already prints ISO leaves this null. Expect prose (`September 8, 1916`), abbreviated months (`Feb. 25, 1868`), US numerics (`9/28/15`), Spanish for Puerto Rico (`26 de junio de 1963`), and values that are not a single date at all (`April 1, 2023 to June 30, 2026`), which is why they cannot be published under `effectiveDate`. examples: - September 8, 1916 historyEffectiveDate: anyOf: - type: string - type: 'null' title: Historyeffectivedate description: >- When this version took effect, as `YYYY-MM-DD`, read out of the publisher's own amendment credit line in `history`. **This is a weaker fact than `effectiveDate` and is deliberately not published as one.** `effectiveDate` is a date the publisher put in a date field; this is our reading of the publisher's prose. It is populated ONLY where `effectiveDate` is null, so the two can never be confused, and `history` is returned beside it as the evidence. It exists because most states publish the commencement date nowhere else: measured over the live corpus on 2026-09-20, `effectiveDate` is set on 4.8% of state statutes and this answers a further 21.3%. It is the newest commencement the credit line names, and null whenever that cannot be stated without guessing: a credit line that dates only some of its entries, a date that belongs to a repeal, a sunset, an applicability rule or another section, a commencement still in the future, a date older than the section's own `lastAmendedYear`, or a state whose `history` format we have not measured. Statutes only; never set on a regulation, a court rule or a federal corpus. examples: - '2009-06-19' priorEffectiveDates: anyOf: - items: type: string type: array - type: 'null' title: Prioreffectivedates description: Earlier effective dates recorded for the section. history: anyOf: - type: string - type: 'null' title: History description: >- The publisher's own amendment/history credit line, verbatim, e.g. `Effective 5/4/2005; Superseded 8/1/2016`. `amendmentYears` is parsed from this; keep both when you need the exact wording. supersededBy: anyOf: - type: string - type: 'null' title: Supersededby description: >- `actId` of the section that replaced this one. Present on a superseded version so you can fetch the current text in one hop via `GET /statutes/section/{actId}`. supersedes: anyOf: - type: string - type: 'null' title: Supersedes description: '`actId` of the earlier version this section replaced, when known.' ruleSet: anyOf: - type: string - type: 'null' title: Ruleset description: >- For court rules, the rule family this belongs to, e.g. `North Dakota Rules of Civil Procedure`. Rule numbers repeat across families (a Civil Rule 12 and a Criminal Rule 12 both exist), so this is what disambiguates them. publicLaws: anyOf: - items: type: string type: array - type: 'null' title: Publiclaws description: Public Laws referenced by the section, e.g. `['Pub. L. 96-170']`. federalRegisterCitations: anyOf: - items: type: string type: array - type: 'null' title: Federalregistercitations description: >- Federal Register citations associated with the section, e.g. `['48 FR 3956', '49 FR 15073']`. This is the CFR's form of the credit line `sourceCredit` carries for the USC: the rulemakings that established and amended the section. Populated on 37.4% of CFR sections, empty where eCFR prints no source note. granuleId: anyOf: - type: string - type: 'null' title: Granuleid description: govinfo granule identifier (USC/CFR provenance). packageId: anyOf: - type: string - type: 'null' title: Packageid description: govinfo package identifier (USC/CFR provenance). htmlUrl: anyOf: - type: string - type: 'null' title: Htmlurl description: HTML version of the statute section. pdfUrl: anyOf: - type: string - type: 'null' title: Pdfurl description: PDF version of the statute section. xmlUrl: anyOf: - type: string - type: 'null' title: Xmlurl description: XML version of the statute section. textUrl: anyOf: - type: string - type: 'null' title: Texturl description: >- Plain-text version. Populated for state corpora (MS, NJ, NY, NV, etc.). docxUrl: anyOf: - type: string - type: 'null' title: Docxurl description: Microsoft Word (DOCX) version, when available. stateHtmlUrl: anyOf: - type: string - type: 'null' title: Statehtmlurl description: >- HTML rendering of the document. For most state corpora this is the publisher's own page; for corpora we mirror (state agency guidance, regulations, court rules) it is our archived copy of the artifact the publisher served, on statutes-us.vaquill.ai. Use `externalUrl` for the publisher's canonical address. Never a PDF: a mirrored PDF is served as `pdfUrl` instead. Populated for state corpora only. govInfoHtmlUrl: anyOf: - type: string - type: 'null' title: Govinfohtmlurl description: Official govinfo.gov HTML version. govInfoPdfUrl: anyOf: - type: string - type: 'null' title: Govinfopdfurl description: Official govinfo.gov PDF version. abstract: anyOf: - type: string - type: 'null' title: Abstract description: >- The issuing agency's own summary of the document, as published in the Federal Register. Populated on 99.9% of rules and proposed rules, so a document can be triaged without fetching the full text. examples: - This regulation extends time-limited tolerances for pesticides. agencies: anyOf: - items: type: string type: array - type: 'null' title: Agencies description: >- Issuing agencies, by name. Populated on 99.9% of Federal Register documents. Pair with `agencySlugs` when you need the token the `agency` search filter takes. examples: - - Environmental Protection Agency agencySlugs: anyOf: - items: type: string type: array - type: 'null' title: Agencyslugs description: >- The issuing agencies as slugs. These are exactly the values the `agency` filter on `/us/statutes/search` accepts, so an agency facet can be round-tripped straight back into a query. examples: - - environmental-protection-agency topics: anyOf: - items: type: string type: array - type: 'null' title: Topics description: >- The Federal Register's own CFR-index subject terms. Populated on ~71% of rules and ~68% of proposed rules, with one hard boundary: documents published before 2000 carry none, because the Federal Register did not index them this way. examples: - - Environmental protection - Pesticides and pests documentTypeLabel: anyOf: - type: string - type: 'null' title: Documenttypelabel description: >- The instrument type as the publisher names it: `Rule`, `Proposed Rule`, `Presidential Document`, `Declaratory Ruling`, `Resolution Agreement`. Deliberately NOT `corpusType`, which says which body of law a document belongs to: two documents in one corpus can be very different instruments. examples: - Rule documentSubtype: anyOf: - type: string - type: 'null' title: Documentsubtype description: >- Finer instrument class where the publisher gives one. On presidential documents this separates an executive order from a proclamation, a memorandum or a notice (~90% populated there). examples: - Proclamation action: anyOf: - type: string - type: 'null' title: Action description: >- The Federal Register's own ACTION line, ~100% populated. Carries distinctions no other field makes: interim final rule, direct final rule, withdrawal, reopening of the comment period. examples: - Final rule. president: anyOf: - type: string - type: 'null' title: President description: >- The president in office for this document, on Federal Register and presidential-document corpora spanning 1994 to present. examples: - George W. Bush signingDate: anyOf: - type: string - type: 'null' title: Signingdate description: >- When a presidential document was signed, as `YYYY-MM-DD`, which is routinely earlier than `publicationDate` and is the legally operative date. See `signingDateRaw`. examples: - '2026-04-02' signingDateRaw: anyOf: - type: string - type: 'null' title: Signingdateraw description: >- The signing date as the publisher writes it, present only when it differs from `signingDate`. datesText: anyOf: - type: string - type: 'null' title: Datestext description: >- The verbatim DATES block from the Federal Register, ~98% populated. Worth reading alongside `frEffectiveOn`: a rule with staged or conditional effective dates has them here, and the single date flattens that away. examples: - This regulation is effective December 14, 2001. frVolume: anyOf: - type: integer - type: 'null' title: Frvolume description: Federal Register volume, the `66` in `66 FR 64768`. examples: - 66 frStartPage: anyOf: - type: integer - type: 'null' title: Frstartpage description: First Federal Register page, the `64768` in `66 FR 64768`. examples: - 64768 frEndPage: anyOf: - type: integer - type: 'null' title: Frendpage description: >- Last Federal Register page. With `frStartPage` this gives the page RANGE, which `citation` cannot express because it carries only the first page. examples: - 64775 wordCount: anyOf: - type: integer - type: 'null' title: Wordcount description: >- Words in the full document, so a caller can size a fetch before paying for the body. examples: - 6271 issuingAgency: anyOf: - type: string - type: 'null' title: Issuingagency description: >- The body that promulgated or issued this document: the state agency behind a regulation, the division behind an agency letter. Populated at 83.6-100% across the state-regulation corpora that carry it. examples: - Pollution Control Board adoptingCitations: anyOf: - items: type: string type: array - type: 'null' title: Adoptingcitations description: >- Citations to the instrument that ADOPTED this rule: the state register notice, the Washington filing number, the adopting order. The rulemaking audit trail. Unified across four different payload spellings, so this is comparable across states in a way the underlying data is not. These are also the independent way to confirm a section when the publisher's own page cannot be read without a browser (see `externalUrl`): a Texas rule's `['50 TexReg 8285']` names the Texas Register issue and page that printed its adoption. examples: - - 37 Ill. Reg. 16539 lawImplemented: anyOf: - type: string - type: 'null' title: Lawimplemented description: >- The statute this rule IMPLEMENTS, as distinct from `statutoryAuthority`, which is the statute granting the rulemaking power. Florida populates both and they differ. examples: - Section 4656.1, Public Resources Code lastAmendedDate: anyOf: - type: string - type: 'null' title: Lastamendeddate description: >- Full date of the most recent amendment, as `YYYY-MM-DD`, where the publisher gives one. See `lastAmendedDateRaw` for the wording. Illinois and Colorado regulations carry their amendment provenance only here and in `amendmentNote`: neither state has a `history`, and Colorado has no `effectiveDate` either, so for Colorado this is the only date that exists. examples: - '2013-10-04' lastAmendedDateRaw: anyOf: - type: string - type: 'null' title: Lastamendeddateraw description: >- The last-amended date as the publisher writes it, present only when it differs from `lastAmendedDate`, or null when it is not a date at all. amendmentNote: anyOf: - type: string - type: 'null' title: Amendmentnote description: >- The publisher's amendment credit line where it is stored separately from `history`. Illinois and Colorado regulations, ~72% populated. examples: - Amended at 37 Ill. Reg. 16539, effective October 4, 2013 currencyYear: anyOf: - type: integer - type: 'null' title: Currencyyear description: >- Machine-readable counterpart to `currencyNote`, which is prose. 100% populated on the nine state-regulation corpora that carry a currency statement. examples: - 2025 reviewDate: anyOf: - type: string - type: 'null' title: Reviewdate description: >- The date a rule must be re-adopted or it expires, where the state runs a sunset review. Ohio regulations, ~80% populated. Not an amendment date: it is in the future. examples: - 11/1/2028 reviewDateRaw: anyOf: - type: string - type: 'null' title: Reviewdateraw description: >- The review date as the publisher writes it, present only when it differs from `reviewDate`, or null when it is not a date at all. originalEnactmentDate: anyOf: - type: string - type: 'null' title: Originalenactmentdate description: >- When the section was FIRST enacted, as `YYYY-MM-DD`, ~72% populated on the US Code. Deliberately separate from `effectiveDate`: merging them would report an amended section as effective from its original year. On 35.7% of US Code points this is the only enactment date we hold. See `originalEnactmentDateRaw` for the publisher's wording. examples: - '1934-06-27' originalEnactmentDateRaw: anyOf: - type: string - type: 'null' title: Originalenactmentdateraw description: >- The enactment date as the publisher writes it, present only when it differs from `originalEnactmentDate`. The US Code prints `Aug. 14, 1935` where GovInfo statute compilations print `1935-08-14` for the same fact. examples: - June 27, 1934 releaseDate: anyOf: - type: string - type: 'null' title: Releasedate description: >- When the document was released publicly, where that differs from when it was issued. NLRB advice memoranda are written years before release; measured, the two dates are never equal. examples: - '2018-06-14' releaseDateRaw: anyOf: - type: string - type: 'null' title: Releasedateraw description: >- The release date as the publisher writes it, present only when it differs from `releaseDate`, or null when it is not a date at all. documentNumber: anyOf: - type: string - type: 'null' title: Documentnumber description: >- The issuer's own document or case number, for exact lookup: an FCC DA number, an NLRB case-handling docket, a ruling number. On NLRB advice memoranda and FCC/HHS OCR documents this is NOT recoverable from `sectionNumber`. examples: - 21-CA-211066 caseName: anyOf: - type: string - type: 'null' title: Casename description: >- The charged party or covered entity a document concerns. Only 27% equal to `sectionTitle` on HHS OCR, so it is not recoverable from the served text. examples: - Dunn-Edwards Corp. forum: anyOf: - type: string - type: 'null' title: Forum description: >- For `corpusType=AGENCY_ADJUDICATION`, the KIND of proceeding that produced the document, in the publisher's own words. On CFPB enforcement actions this is `Administrative Proceeding` (the Bureau's own Office of Administrative Adjudication, under 12 C.F.R. Part 1081) or `Civil Action` (a suit the Bureau filed in a federal district court). One action can carry both, in which case they are joined with `; `. Null on every other corpus. examples: - Administrative Proceeding court: anyOf: - type: string - type: 'null' title: Court description: >- The body that heard the matter, where the publisher names one. Distinct from `forum`, which is the KIND of proceeding: `forum` has two values and is what you filter on, `court` has as many values as there are districts and is for display. Populated on every CFPB civil action and on the administrative proceedings the Bureau labels with its own adjudication office. examples: - U.S. District Court for the District of Massachusetts relatedDocuments: anyOf: - items: type: string type: array - type: 'null' title: Relateddocuments description: >- The publisher's own labels for the filings whose text this record carries, in the order the publisher lists them. A CFPB enforcement action is ONE legal event published as two to seventeen PDFs and the unit we serve is the ACTION, not the filing: a consent order and the stipulation consenting to it are one record, because splitting them makes every search return two half-answers. This is what tells you which filings are inside the record you are holding. Only the operative instrument is mirrored under `pdfUrl`. examples: - - Consent Order - Stipulation settlementAmount: anyOf: - type: string - type: 'null' title: Settlementamount description: >- The monetary penalty or settlement, as the agency prints it. 95.2% populated on HHS OCR resolution agreements, where it is the single most-asked fact of the corpus. examples: - $16,500 requesters: anyOf: - items: type: string type: array - type: 'null' title: Requesters description: >- Who asked for the determination or relief. On export-control commodity-jurisdiction determinations this is the applicant (100% populated); on no-action letters it determines who may rely on the relief. examples: - - Preece, Inc. program: anyOf: - type: string - type: 'null' title: Program description: >- The benefit or regulatory program a document governs, e.g. Old-Age and Survivors Insurance. 100% populated on Social Security rulings, where it is the primary axis a practitioner filters on. examples: - Old-Age and Survivors Insurance languageCode: anyOf: - type: string - type: 'null' title: Languagecode description: >- ISO code of the language the document is written in, present where a corpus is not wholly English. 86% of Puerto Rico insurance bulletins are Spanish (`es`). examples: - es volume: anyOf: - type: integer - type: 'null' title: Volume description: >- Volume number for corpora organised in volumes, e.g. the USCIS Policy Manual, whose Volume is the top hierarchy level and had no served representation at all. examples: - 1 articleNumber: anyOf: - type: string - type: 'null' title: Articlenumber description: >- Article number. Article is the PRIMARY hierarchy level in state constitutions, where `chapter` and `part` are 0-6% populated, so without this those corpora served almost no structure. examples: - '1' articleName: anyOf: - type: string - type: 'null' title: Articlename description: Article title, the companion to `articleNumber`. examples: - Declaration of Rights ruleSetCode: anyOf: - type: string - type: 'null' title: Rulesetcode description: >- Stable machine key for the rule family, where `ruleSet` gives only the prose name. 100% populated on the court-rules states that have a rule set. examples: - NDSUPCTADMINR edition: anyOf: - type: string - type: 'null' title: Edition description: The publisher's edition or year for this text. examples: - '2025' relatedCitations: anyOf: - items: type: string type: array - type: 'null' title: Relatedcitations description: >- Citations OUT of this document that are neither USC nor CFR: the state statutes a regulation implements, the Internal Revenue Code sections a ruling construes, other guidance it points at. `crossReferencesUsc` and `crossReferencesCfr` are 0% on several of these corpora, so this is the only outbound citation set they have. examples: - - RCW 28A.150.290 supersessionActions: anyOf: - additionalProperties: true type: object - type: 'null' title: Supersessionactions description: >- What this document does to EARLIER documents, keyed by the issuer's own verb: `modifies`, `obsoletes`, `amplifies`, `clarifies`, `rescinds`, each mapping to the documents affected. `supersedes` and `supersededBy` cover only the strongest verb. Without these a caller cannot tell a modified revenue procedure from an untouched one, nor see which memorandum rescinded which. examples: - modifies: - Rev. Proc. 2011-47 licenseNote: anyOf: - type: string - type: 'null' title: Licensenote description: >- Licence and upstream dataset for text derived from a third-party snapshot rather than fetched from the publisher. Present on the state-regulation corpora built from an external dataset; absent means we hold the text under no third-party licence. examples: - MIT (reglab/statecodes) subtitle: anyOf: - type: string - type: 'null' title: Subtitle description: >- Subtitle, where a jurisdiction puts a level between title and chapter. Maryland's regulations are organised Title > Subtitle > Chapter and are 100% populated; no other served field expressed that level. Deliberately NOT the same as `subchapter`, which sits BELOW chapter. examples: - '11' subtitleName: anyOf: - type: string - type: 'null' title: Subtitlename description: Subtitle title, the companion to `subtitle`. examples: - AIR QUALITY publisherKey: anyOf: - type: string - type: 'null' title: Publisherkey description: >- The publisher's own stable identifier for this document, where it issues one. On the US Code this is the OLRC's `usckey` (100% populated), which joins directly to the uscode.house.gov bulk XML; on Colorado regulations it is the state's rule id. Use it to reconcile our records against the publisher's without matching on citation strings. examples: - '430000000310400000000000000000000' versionId: anyOf: - type: string - type: 'null' title: Versionid description: >- The publisher's identifier for THIS VERSION of the document, where it versions them separately from the document itself. 100% populated on Colorado regulations, where it is the only version pointer that exists. examples: - '11948' referencedShortTitles: anyOf: - items: type: string type: array - type: 'null' title: Referencedshorttitles description: >- Popular names of acts this section REFERENCES, ~10% of the US Code. Distinct from `popularName`, which is the section's own. examples: - - Driftnet Modernization and Bycatch Reduction Act subjectNumber: anyOf: - type: string - type: 'null' title: Subjectnumber description: >- The publisher's numbered subject index entry, the companion to the term in `topics`. 100% populated on Social Security rulings. examples: - '47' audience: anyOf: - type: string - type: 'null' title: Audience description: >- Who the document is addressed to or binds, where the issuer states it. 100% populated on the Montana insurance bulletins. examples: - All Persons Engaged in Marketing sourceCharStart: anyOf: - type: integer - type: 'null' title: Sourcecharstart description: >- Character offset where this text begins in the source document, for callers reconciling our extraction against the original PDF. Pairs with `sourcePageStart`. examples: - 263194 sourceCharEnd: anyOf: - type: integer - type: 'null' title: Sourcecharend description: Character offset where this text ends in the source document. examples: - 264198 alternateCitations: anyOf: - items: type: string type: array - type: 'null' title: Alternatecitations description: >- Other official citation forms for THIS document, where a publisher prints more than one. Puerto Rico gives an L.P.R.A. cite, Arizona a long form, the IRS an Internal Revenue Bulletin cite, the Federal Reserve a paired Consumer Affairs number. Distinct from `relatedCitations`, which is what this document points AT. Use these when you need to match a citation a user typed in the form their jurisdiction actually publishes. examples: - - 4 L.P.R.A. § 2077 expirationDate: anyOf: - type: string - type: 'null' title: Expirationdate description: >- When this rule lapses unless re-adopted, as `YYYY-MM-DD`. Distinct from `reviewDate` (the review deadline) and from any amendment date: it is in the future and it ENDS the rule. See `expirationDateRaw` for the publisher's wording. examples: - '2029-03-01' expirationDateRaw: anyOf: - type: string - type: 'null' title: Expirationdateraw description: >- The expiry date as the publisher writes it, present only when it differs from `expirationDate`. State regulators print this as `1/1/2028` and `03-01-2029` as well as ISO. examples: - 03-01-2029 committeeNote: anyOf: - type: string - type: 'null' title: Committeenote description: >- Advisory-committee note on a procedural rule: the standard interpretive gloss courts read alongside the rule text. Deliberately separate from `amendmentNote`, which records when the rule changed rather than what it means. sourcePageStart: anyOf: - type: integer - type: 'null' title: Sourcepagestart description: >- First page in the official PDF this text was extracted from, for a pinpoint print citation. 100% populated on the Federal Rules. examples: - 114 sourcePageEnd: anyOf: - type: integer - type: 'null' title: Sourcepageend description: Last page in the official PDF; companion to `sourcePageStart`. examples: - 114 displayLabel: anyOf: - type: string - type: 'null' title: Displaylabel description: >- The publisher's own short label for this section, e.g. `Cal. BPC § 655.2` or `MPEP § 2165.03`. Populated on essentially every document we hold. Usually equal to `citationShort`, but NOT always: on the Federal Communications Commission, NLRB, HHS OCR and BIS corpora the two differ on every document, and there `displayLabel` is the form the publisher itself prints. examples: - MPEP § 2165.03 publicationDate: anyOf: - type: string - type: 'null' title: Publicationdate description: >- The date this document was published by its source. For Federal Register documents this is the FR publication date, the primary citation and sort key, populated on 100% of rules and proposed rules. Distinct from `effectiveDate` (when it takes legal effect) and from `issueDate` (when the issuing body dated it). A rule is routinely published before it is effective. examples: - '2001-12-14' publicationDateRaw: anyOf: - type: string - type: 'null' title: Publicationdateraw description: >- The publication date as the publisher writes it, present only when it differs from `publicationDate`, or null when it is not a date at all. publicLawCites: anyOf: - items: additionalProperties: true type: object type: array - type: 'null' title: Publiclawcites description: >- Structured Statutes at Large citations parsed out of the source credit, populated on ~72% of the US Code. Each entry carries `statVolume`, `statPage`, `type` and a `display` string. `publicLaws` gives the bare `Pub. L.` list and `sourceCredit` the raw prose; this is the same information already parsed, so a caller can link to the Statutes at Large without re-parsing the credit line. topLevelTitle: anyOf: - type: string - type: 'null' title: Topleveltitle description: >- The outermost division this document sits under, where the corpus has one that `titleNumber`/`chapter`/`part` do not already express. Examples: `Title 9: Criminal` for the DOJ Justice Manual, `Volume 1 - General Policies and Procedures` for the USCIS Policy Manual. Null for flat corpora, where one document is the whole unit. examples: - 'Title 9: Criminal' externalUrl: anyOf: - type: string - type: 'null' title: Externalurl description: >- The publisher's own page for this section, exactly as recorded at ingest: uscode.house.gov, ecfr.gov, a state legislature or a state register. Null when the publisher issues no per-section link, or when the link is withheld under licence (`licenseNote` says so). Prefer `sourceUrl`, which is this link when present and otherwise the best official alternative. Some official publishers serve their code only through a JavaScript application, so the link renders in a browser but returns an empty page shell to a plain HTTP client. Texas is the main case: the Secretary of State publishes the Texas Administrative Code only on its Appian portal (texas-sos.appianportalsgov.com). The link is still the correct citation. To check a section without a browser, use `adoptingCitations` (for Texas, the `NN TexReg PPPP` register citations that adopted and amended it) and read the text we captured at `textUrl`. examples: - >- https://www.mass.gov/regulations/240-CMR-200-licensure-of-cosmetologists sourceUrl: anyOf: - type: string - type: 'null' title: Sourceurl description: >- Where the government published this text: the link to cite and to verify against. The same value `/us/statutes/section/{actId}/body` returns as `sourceUrl`, on every search result, section record and batch item. It is `externalUrl` when the publisher issued a per-section link, and otherwise falls back to the govinfo.gov page, then the state's own page, then our archived copy of the publisher's page. Null when we hold no publishable link: a third-party compiler is never served here, and where a link exists but is withheld under licence, `licenseNote` says so. examples: - >- https://www.mass.gov/regulations/240-CMR-200-licensure-of-cosmetologists type: object required: - actId title: StatuteResult description: A single statute section from search results. CitationOutsideFilters: properties: actId: type: string title: Actid description: >- The section the citation names. Pass it to `/section/{actId}` to read it. examples: - USC_T42_C21_S1983 citation: anyOf: - type: string - type: 'null' title: Citation description: That section's citation, as it appears in results. examples: - 42 U.S.C. § 1983 (2026) title: anyOf: - type: string - type: 'null' title: Title description: That section's heading. examples: - Civil action for deprivation of rights state: anyOf: - type: string - type: 'null' title: State description: 'That section''s jurisdiction: `federal` or a two-letter state code.' examples: - federal corpusType: anyOf: - type: string - type: 'null' title: Corpustype description: That section's corpus, e.g. `USC`, `CFR`, `STATE`. examples: - USC excludedBy: items: type: string type: array title: Excludedby description: >- The request filters that exclude the section, by their public names (`state`, `corpusType`, `code`, `article`, `titleNumber`, `chapter`, `part`, `yearFrom`, `yearTo`). Empty when the exclusion comes from a condition only the index can attribute (`excludeRepealed`, `actStatus`, `source`, `changedSince` and the Federal Register facets): then any of the filters you set may be responsible. examples: - - state type: object required: - actId title: CitationOutsideFilters description: >- A citation that names a real section the caller's own filters exclude. Both `/search` and `/resolve` treat a filter as a promise: a citation outside it is not forced into the results. This says so, instead of leaving a caller to read an unrelated top hit (or `resolved: false`) as "no such section". CitationMissReason: properties: missReason: type: string enum: - not_held - former_law - ambiguous_jurisdiction - malformed - out_of_scope_corpus title: Missreason description: >- Present only when `resolved` is false and none of `citationOutsideFilters` / `sessionLaw` already explains it. WHY the citation did not resolve: `ambiguous_jurisdiction` (the form is one several jurisdictions print, or names none, and no `state` was given: pass `state`; `candidates` lists the held sections it could mean when we can name them, and never picks one), `out_of_scope_corpus` (it names a body of law this route does not serve; `missReasonHint` says which and where to look), `former_law` (it names a repealed, renumbered or retired compilation we do not serve as current law; `missReasonHint` names the successor where one is known), `malformed` (no parser reads it: a docket or database token, a case or treatise citation, a string with no section number), `not_held` (it reads as a citation to a jurisdiction and corpus we serve, and that corpus does not hold the section). A miss is still charged, because the verdict is the product; the reason adds no charge. Absent on a resolved citation. missReasonHint: anyOf: - type: string - type: 'null' title: Missreasonhint description: >- Present with `missReason`. One sentence on what to try next. Prose for a human or an agent; do not parse it. candidates: anyOf: - items: $ref: '#/components/schemas/MissReasonCandidate' type: array - type: 'null' title: Candidates description: >- Present only with `missReason: ambiguous_jurisdiction`, and only when we can name the held sections the citation could mean (an acronym two states print, such as `CCR`). At most 10 entries. Pass the right one's `state` to `GET /us/statutes/resolve` to resolve it. Never a pick: when several are listed, none is the answer. type: object required: - missReason title: CitationMissReason description: >- The same finding as one block, for a response that is not itself a citation verdict. `POST /us/statutes/search` carries it as `citationMissReason`, beside `citationOutsideFilters`: the query was a citation, the resolver missed, and the ranked results are an ordinary search. ApiFieldError: properties: loc: items: anyOf: - type: string - type: integer type: array title: Loc description: >- Where the bad value is: `body`, `query` or `path`, then the parameter name exactly as you send it (camelCase), then list indexes. A bare `["body"]` means the body as a whole was not a JSON object. examples: - - body - corpusType msg: type: string title: Msg description: What is wrong with the value, in plain English. examples: - Input should be 'USC', 'CFR' or 'STATE' type: type: string title: Type description: >- Machine-readable error kind, e.g. `missing`, `literal_error`, `json_invalid`. examples: - literal_error type: object required: - loc - msg - type title: ApiFieldError description: One rejected field in a 422 response. FrRelatedDocument: properties: actId: type: string title: Actid citation: anyOf: - type: string - type: 'null' title: Citation title: anyOf: - type: string - type: 'null' title: Title description: The related document's own title/heading, when known. documentType: anyOf: - type: string - type: 'null' title: Documenttype description: >- `proposed_rule`, `final_rule`, or the raw Federal Register category otherwise. publicationDate: anyOf: - type: string - type: 'null' title: Publicationdate description: Federal Register publication date (ISO 8601 date), when known. type: object required: - actId title: FrRelatedDocument description: >- One other Federal Register document sharing a RIN with this one. A Regulation Identifier Number (RIN) tracks one regulatory action through its lifecycle -- a proposed rule, its final rule, and any later corrections all carry the same RIN. This is what answers "what happened to this proposed rule": look up its RIN's other documents. MissReasonCandidate: properties: state: type: string title: State description: The jurisdiction to pass as `state` to resolve this one. examples: - co actId: type: string title: Actid description: The section's id. examples: - REG_CO_T8_S1206-2 citation: anyOf: - type: string - type: 'null' title: Citation description: Its own citation, as it appears in results. examples: - 8 CCR 1206-2 subsection: anyOf: - type: string - type: 'null' title: Subsection description: The pinpoint the citation carried, if any. type: object required: - state - actId title: MissReasonCandidate description: A held section an ambiguous citation could mean. securitySchemes: ApiKeyAuth: type: http scheme: bearer bearerFormat: vq_key_* description: >- API key issued from the developer dashboard. Pass as `Authorization: Bearer vq_key_...` (preferred). ApiKeyHeader: type: apiKey in: header name: X-API-Key description: >- The same API key as a bare header value: `X-API-Key: vq_key_...`. Equivalent to the Bearer form. ApiKeyQuery: type: apiKey in: query name: api_key description: >- The same API key as a query parameter: `?api_key=vq_key_...`. Use only where you cannot set a header. A URL can end up in proxy and server logs, browser history and shared links, so prefer either header form, and rotate a key that has leaked. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.