corpusType chooses which body of law a search runs against. It is the single most important
filter in the API: it decides whether you get a statute, a regulation, a court rule, agency
guidance or a decided case.
Scoping rules
1
A federal token needs only corpusType
2
A state token needs corpusType and state
Omit
state on a state-scoped token and the search spans every jurisdiction that has that
corpus ingested, which is rarely what you want and always costs the same.state also accepts a list, so one call can cover several jurisdictions.3
Narrow further with source, where a token folds in several bodies
titleNumber is only valid alongside corpusType USC or CFR. Sending it with any other
token returns a 422.The 22 tokens
Sizes are distinct sections, measured 2026-10-13 fromGET /us/statutes/coverage. Call GET /us/statutes/coverage for a live figure and
for which tokens have data in which jurisdiction.
The OpenAPI enum also accepts USC_ANNUAL, GPO’s retired annual edition of the US Code, which is
kept only so a past date can be answered from a printed edition. It is not a token to search.
Federal-scoped
State-scoped
Each of these requiresstate, or spans every jurisdiction holding that corpus.
State session laws have no
corpusType.
They are served by /us/session-laws, not /us/statutes.
SESSION_LAW is the federal Statutes at Large only.
STATE_REGISTER in particular
A state’s official register prints each proposed, adopted or emergency rule as a notice on a date.
STATE_REGISTER holds those notices, one document per printed item, cited by register volume and page (36 Pa. Bull. 510).
Cite a register item by its register citation; see
Register citations.
The states loaded are listed on State and territory coverage.
STATE_AG_OPINION in particular
A formal written opinion in which a state’s chief legal officer construes that state’s own
statutes, constitution and regulations for a state officer, legislator or local government who
asked.
Where a jurisdiction runs more than one series, the series field carries the publisher’s own
label, so you can filter Washington’s formal AGO apart from its AGLO letter opinions, or
Georgia’s Official from its Unofficial opinions. The series is also part of the actId, which is
what makes the field trustworthy rather than derived from a title.
Choosing between tokens that look alike
Five pairs are routinely confused, and picking the wrong one returns a confident answer to a different question.
For asking any corpus what it said on a past date, see
Point-in-time law.
SESSION_LAW and STATUTE_COMPILATION both carry goodLawStatus: "unknown" by design: they are
historical records, not statements of current law.
Filtering to one named source
AGENCY_GUIDANCE, AGENCY_ADJUDICATION, FEDERAL_RULES, CFR, US_TAX_TREATY and
STATE_AGENCY_GUIDANCE each fold several independently filterable bodies into one token. Every
result carries a source field naming which one it came from; pass that value back as the source
filter to scope to it.
source accepts a single value or a list, so source: ["frcp", "sct"] searches both in one call.
An unrecognized value is rejected with 422 and the error names every valid code, so the API
itself is the authoritative list.
The
far and dfars sources split existing Title 48 data by chapter. They are not a
separate ingest and do not add sections to the CFR total.Related
API Coverage
How much sits behind each token, and what each corpus deliberately excludes.
Jurisdictions and state codes
The 56 jurisdictions and how to discover live coverage.

