Statutes · Regulations · Court rules · Agency guidance · Jury instructions · Sentencing Guidelines
What the law said, on any given date — with the receipt attached.
3,118,113 sections of American law across 59 jurisdictions and 7 corpora — statutes, regulations, court rules, agency guidance, jury instructions and the Sentencing Guidelines. Each section carries its source URL, retrieval time, content hash and validity dates. Outside coverage you get an explicit miss, never a nearest guess.
(1) Unfair methods of competition, unconscionable acts or practices, and unfair or deceptive acts or practices in the conduct of any trade or commerce are hereby declared unlawful.
- citation.display
- § 501.204, Fla. Stat.
- catchline
- Unlawful acts and practices.
- status
- active
- validFrom → validTo
- 2017-07-01 → present
- temporalBasis
- compiled-edition
- provenance.sourceSystem
- flsenate.gov
- provenance.versionLabel
- 2017
- provenance.retrievedAt
- 2026-07-22
- provenance.contentHash
- 949ab03cdfa96589734237a616008373873ba4d333a990eb0c2ea7cce8c82bf3
Florida publishes a compiled edition, so the validity window is edition granularity and the response says so rather than implying act-level precision.
check this record →3,118,113
sections with full provenance
59
jurisdictions across all corpora
7
corpora, one query contract
0
nearest guesses — misses are explicit
The corpus, this week
Nothing here is a one-off scrape.
Every corpus re-reads its sources on a schedule and records when it last did. These dates are read from /v1/law/coverage as this page renders — the same field your own monitoring would poll.
A refresh that finds no change still records the read, so a stale date means a pipeline problem rather than a quiet source. When a source does change, the prior text is not overwritten — it keeps its validity window and becomes answerable by date.
The endpoint is live and unmetered; no audit run has been recorded against the current deployment yet, and it says so rather than returning a clean sheet. The checks behind it caught two defects already in production — Colorado regulations stored whole-document, and eight CMS survey appendices stored as one row each — which is why the results are published at all instead of kept in an internal dashboard.
Point-in-time
“What did §2B1.1 say at sentencing in 2019?”
One added parameter, and the answer is the 2018 Guidelines Manual — with a closed validity window, its own edition label and its own content hash. Not today's text with a caveat, and not a nearest edition picked on your behalf.
The Sentencing Guidelines corpus →(2) (Apply the greatest) If the offense— (A) (i) involved 10 or more victims; (ii) was committed through mass-marketing; or (iii) resulted in substantial financial hardship to one or more victims, increase by 2 levels; (B) resulted in substantial financial hardship to five or more victims, increase by 4 levels…
- citation.display
- U.S.S.G. §2B1.1
- status
- active
- validFrom → validTo
- 2018-11-01 → 2023-11-01
- temporalBasis
- act-effective-date
- provenance.versionLabel
- ussg-2018
- provenance.sourceSystem
- ussc.gov
- provenance.contentHash
- 8124372bbc13f61c5932828b20043445d238d3ffbf53b18a5d60e91cf32ed36c
Same citation, same call, one added parameter — and a different edition, a different hash, and a closed validity window. That is the whole product in one diff.
check this record →Why it holds up
Built for teams that have to stand behind the answer.
01
Point-in-time, not just current
Ask for a section as of 2019 and get the 2019 text with its validity window — not today's version with a disclaimer. Supersessions are first-class data.
02
Provenance on every field
Source URL, retrieval timestamp, content hash, validity dates. Your compliance team can re-derive any answer from the official source, byte for byte.
03
Explicit misses
Outside coverage, the API returns a structured miss with the reason — never a nearest-neighbor guess. Your agent knows what it doesn't know.
Agent-native
Your agent cites the law. We prove it.
The binding.law MCP server ships narrow, well-named tools over streamable HTTP — one for each thing an agent actually needs, and none that invite a model to improvise a query. Install once; every agent gets grounded law with citations it can hand to a human.
MCP quickstart →$ MCP endpoint: https://mcp.binding.law
lookup_law(jurisdiction, citation, corpus?, asOf?)
one section, full text and provenance
get_law_text(jurisdiction, citation, corpus?, asOf?)
the same section, compact — for quoting
search_law(q, jurisdiction?, corpus?, asOf?, limit?)
ranked hits with highlighted snippets
lookup_citation(text)
case citations resolved against the caselaw replica
law_coverage(—)
what is carried, and from when
law_quality(jurisdiction?, history?)
our own audit of where the corpus is thin
The data
7 corpora, one contract: every fact has a source.
/v1/law/lookup?corpus=statutes
45 jur.
Statutes1,946,798
State and federal statutory text, versioned at the section level. Ask as of any date and get the text in force then, with its validity window.
/v1/law/lookup?corpus=regulations
36 jur.
Regulations1,066,551
The whole Code of Federal Regulations plus state administrative codes, under the same point-in-time contract as statutes.
/v1/law/lookup?corpus=rules
38 jur.
Court rules49,704
Rules of civil and criminal procedure, evidence and appellate practice — federal, state and the local rules of the federal district courts.
/v1/law/lookup?corpus=guidance
2 jur.
Agency guidance20,436
Sub-regulatory material: the Internal Revenue Bulletin and Manual, the Justice Manual, BOP program statements, CMS manuals. Dated, hashed, and labelled as not binding.
/v1/law/lookup?corpus=jury_instructions
27 jur.
Jury instructions23,891
Pattern instructions as approved for use at trial, split to the individual instruction, with the committee's notes on use carried alongside rather than merged in.
/v1/law/lookup?corpus=guidelines
1 jur.
Sentencing Guidelines416
The United States Sentencing Guidelines Manual, one row per guideline and one edition per November 1 — so you can read §2B1.1 as it stood at a 2019 sentencing.
/v1/law/lookup?corpus=constitutions
40 jur.
Constitutions10,317
/v1/attorneys/lookup
Attorneys & firms
Bar-verified practitioner and firm data with per-field provenance, kept accurate by the attorneys themselves — free for them, always.
/v1/law/coverage
Coverage, live
A public, unmetered endpoint listing exactly which jurisdictions, corpora and date ranges are in — so you never have to guess what we know.
Statutes reach 43 states and the District of Columbia alongside the U.S. Code. The states still missing are missing for a reason we can name — a code published exclusively by a legal vendor, a host that refuses retrieval, or no machine-readable edition we have been able to find — and the coverage page leaves them out rather than previewing them.
Worked through
The corpora that answer a real question, named.
Federal criminal practice
The Guidelines as they read at sentencing, the BOP program statements that decide how a sentence is served, and the Justice Manual behind the charging decision.
guidelines · guidance · statutes · rules
Tax
Revenue rulings, revenue procedures and notices from the Internal Revenue Bulletin, the Internal Revenue Manual, and Title 26 on both sides of the statute/regulation line.
guidance · statutes · regulations
Healthcare & hospice
42 C.F.R. conditions of participation next to the CMS manuals that tell a surveyor how to read them.
regulations · guidance
Legal tech & agents
Point-in-time, provenance on every field, explicit misses, an MCP server, and bulk export when the API is the wrong shape.
statutes · regulations · rules
An attorney or a law firm?
We likely already have a record for you, built from public bar data. Review it, correct it, and it becomes the authoritative value. Free — we never charge attorneys or firms.
Ground your product in the actual law.
Free tier, no card. Two endpoints don't even need one — what we carry, and what our own audit says about it.