Coverage · live · no key required
You never have to guess what we know.
The coverage matrix is a public, unmetered endpoint — the same data this page shows. Jurisdictions go live as their full back-catalog passes hash verification; the rest of the 50 states are in the ingestion pipeline.
GET https://api.binding.law/v1/law/coverage
Loading live coverage…
These are the counts the API serves right now, read from the same public endpoint your code would call. The page re-checks every minute; the endpoint itself caches for five minutes, so that is the real freshness floor. Counts are exact, never rounded up, and a jurisdiction appears here only once its full back-catalog has passed hash verification — states still in ingestion are deliberately absent rather than previewed.
What the columns mean
- Statutes · Regulations
- Codified law as the jurisdiction publishes it, section by section, each carrying its source URL, retrieval time and content hash.
- Guidance
- Sub-regulatory material — interpretive guidelines and survey procedures. Not binding law, and labelled as such in every response.
- Jury instructions
- Pattern instructions as approved for use at trial, split to the individual instruction and carrying its official notes on use alongside — never merged into the text a judge would read to a jury. Instructions the drafting committee has reserved are served as reserved rather than quietly omitted, and an instruction for which no standard text is provided says so.
Validity dates for jury instructions come from the compilation the publisher dated, so “the instruction as published in that compilation” is answerable with a hash for every one of them. A minority carry their own amendment date in the text. Point-in-time history accrues from the first compilation we hold forward; we do not reconstruct what an instruction said before that, and we never resolve a citation to a nearest edition.
A jurisdiction and material we do not carry answers not_carried — a stated gap, distinct from no_edition_on_file, which means we carry the material but not that citation or date. The difference matters to an agent: one means stop, the other means look again.
Changelog
What went live, when
Jury instructions: a new material class, seeded with Florida
Florida's Standard Jury Instructions — civil, criminal, and contract & business — are live as their own corpus: 960 instructions, split to the individual instruction, each with its notes on use carried alongside rather than merged into the text. Instructions the committee reserved are served as reserved; where no standard text is provided, the record says so instead of showing an empty instruction.
Washington + Maryland statutes live
R.C.W. and the Annotated Code of Maryland full back-catalogs pass hash verification; point-in-time queries land alongside the existing statute corpus.
CMS State Operations Manual added to the guidance corpus
The full CMS State Operations Manual is now ingested, dated, and hashed — linked to the Medicare and Medicaid regulations it interprets.
Eight C.F.R. titles live, including Medicare/Medicaid + FDA
Title 42 (Public Health), Title 21 (Food & Drugs), and six more C.F.R. titles versioned daily from the Federal Register, with as_of queries back to 2017.
Colorado CCR — first state regulations corpus
The Colorado Code of Regulations ships as the first state administrative code, cross-linked to its authorizing statutes.
MCP server live at mcp.binding.law
Narrow, well-named tools — statute_coverage, lookup_statute, get_statute_text, search_statutes — over streamable HTTP, with structured misses and citations your agent can hand to a human.
Need a jurisdiction that isn't live yet?
Ingestion is prioritized by customer demand. Tell us what you need and we'll move it up the queue.