API Coverage

Exactly which US jurisdictions and corpus types the LexBharat statutes API has ingested, with live section counts

5.3M+ distinct sections, indexed as 20M+ retrieval passages, across federal law and all 56 states and territories.

The corpus keeps growing, so this page gives magnitudes and the table below gives the measured split. For a number you can put in a contract, call the endpoint: it is free, it describes itself, and it overrides anything written here by hand.

# The live, self-describing answer. Free, and authoritative over this page.
curl https://api.lexbharat.example/api/v1/us/statutes/coverage \
  -H "Authorization: Bearer lb_key_..."

What’s in the corpus#

This is the only place on the page that states exact counts, so each fact appears once. The rows below were measured on the dates shown in the source notes; the endpoint above is live.

State session laws are held apart from this table and served by their own endpoints. See State Session Laws.

Every section is indexed for hybrid semantic and keyword search, and mirrored in several formats (HTML, PDF, XML, plain text, DOCX) where the source provides them.

Counts are distinct sections, one per provision or document, which is what the coverage endpoint returns. Long documents split into several passages for retrieval, so the index holds more entries than sections. A citation lookup still resolves to one section with its full text.

Federal#

15 corpus types: the US Code and the Statutes at Large, the CFR as a live compilation and as published annual editions, Federal Register rules and notices, Executive Orders, agency guidance, administrative adjudication, the Federal Rules, local court rules, the Constitution, the Sentencing Guidelines and tax treaties.

Full federal table with per-corpus scope limits →

Agency guidance is the one corpus with a source registry behind it: many named sources behind the single AGENCY_GUIDANCE token, each narrowable with source. Source registry →

State and territory matrix#

56 jurisdictions: the 50 states, DC, Puerto Rico, Guam, the Northern Mariana Islands, the US Virgin Islands and American Samoa. All 56 carry statutes, regulations and court rules, and 53 carry constitutions.

Per-jurisdiction counts for all 56 →

State administrative registers#

corpusType=STATE_REGISTER holds the notices a state printed in its official register: proposed, adopted and emergency rule text, one document per item. It is not codified law, it is served with goodLawStatus: "unknown", and it is never ranked as primary law.

Per-jurisdiction counts →

State agency guidance#

State-issued regulatory guidance that interprets state law, almost all of it insurance-regulator bulletins. Query it with corpusType=STATE_AGENCY_GUIDANCE paired with state. This is not a comprehensive rollout: it lands state by state.

Per-state sources and counts →

State Attorney General opinions#

Formal written opinions of a state Attorney General, construing that state’s own statutes, constitution and regulations. Query them with corpusType=STATE_AG_OPINION paired with state.

These are persuasive authority, not binding law, and every section is served with goodLawStatus: "unknown". See Status & Currency.

Refresh cadence#

How often each corpus is re-pulled from its official source. Counts grow between updates, so call GET /us/statutes/coverage for a live figure.

For the age of any single source, call GET /boards: it is free and carries lastRetrievedAt, cadence and retrievalStatus per source.

Which statute cadence applies where#

Jurisdictions that publish their code in a form that can be pulled whole (an official bulk export, an API, or a complete per-section fetch) are re-pulled weekly, and each run reconciles the whole code against what is stored. A few are pulled the same way on a quarterly slot. Everywhere else, statutes are re-pulled monthly or carry text as of their ingest date.

A cadence is a schedule, not a promise that the last run worked: read it off GET /boards rather than off this page. Some jurisdictions are covered but not watchable, so they are absent from GET /boards; for those, read currency from GET /us/statutes/coverage.

Point-in-time and change history#

Every corpus can be asked what it said on a past date, and the answer states whether it is a published edition or a reconstruction. See Point-in-time law.

Detecting a change#

GET /us/statutes/coverage is self-describing, so new corpora appear there as they land. To find sections that moved rather than corpora that appeared, use the changedSince filter on POST /us/statutes/search. See Coverage monitoring for both patterns, and Law change alerts to be pushed a change instead of polling for one.

Corpora that are planned but not yet served, and what is deliberately out of scope, are on the Roadmap.