Jurisdictions covered
All current legal data is U.S. only. Here is what each dataset says it covers — at the level of detail the provider has confirmed.
What each dataset covers
| Dataset | Jurisdictions | Geography | Coverage notes | REST status |
|---|---|---|---|---|
| U.S. Court Opinions (LAW.co corpus) | U.S. federal, U.S. state (all 50) | United States | Coverage is uneven by year and court (ingestion plan notes under-covered 2019–2024 years). | Available |
| LAW.co AI Case Summaries | U.S. federal, U.S. state | United States | Subset only; the plan targets the most-cited cases. | Available |
| LAW.co Case Citation Graph | U.S. federal, U.S. state | United States | — | Available |
| State Estate-Planning Statute Reference Values | U.S. state | United States | Only the states/categories LAW.co has curated. | Not yet connected |
| State Estate-Law Bill Monitor | U.S. state (all 50) | United States | Keyword-filtered to estate-planning topics only. | Not offered |
Why there is no per-state breakdown yet
LAW.co's corpus spans federal and state courts, but Data.co has not verified per-jurisdiction record counts or date ranges. Publishing them before verification would risk misleading researchers who need to know whether a court is fully covered.
When LAW.co's proposed metadata endpoint is available, each jurisdiction will list its courts, record counts and date span.
Federal and state, explained
U.S. courts sit in two parallel systems. Federal courts (district courts, the courts of appeals and the Supreme Court) decide federal questions and certain disputes between parties from different states. Each state runs its own trial, appellate and supreme courts, and most litigation happens there.
The marketplace tags each legal dataset with U.S. federal, U.S. state, or both. Individual records carry the court and jurisdiction from the source, so you can filter or group results yourself even before a verified per-court breakdown exists.
Filtering by jurisdiction
The REST API and MCP tools accept jurisdiction and court filters. With LAW.co's current upstream search, those filters apply to a random sample of up to 50 matches, so a filtered query can return few or no results even when matching cases exist. A warning on the response says so.
GET /legal/jurisdictions and the list_jurisdictions tool return catalog-level coverage only (U.S. federal, U.S. state) until the provider exposes verified metadata.
Outside the United States
No non-U.S. legal data is listed. If you hold court decisions or legislation from another country with clear rights and provenance, the provider program is open to you.
How to check coverage yourself
Until verified metadata exists, the most reliable check is a targeted one: search for cases you already know from the court you care about and see whether they are present. Because upstream search is sampled, run more than one query before concluding something is missing, and treat absence as a reason to check the court's own records.
Provenance on every record
Whatever the topic, each legal record carries the same provenance fields, so you can tell source text from derived work and cite it correctly.
- provider / sourceId
- Who served the record and its id at that provider.
- upstreamSource
- Where the provider got it (for example CAP or CourtListener), or null if not stated.
- canonicalUrl
- Public URL for the record, when one exists.
- licenseId
- The license that applies, such as public domain for court-authored text.
- isDerived
- false for original text and facts; true for AI or editorial layers.
- retrievedAt
- When Data.co fetched it from the provider.
Access today
Individual cases can be read now on LAW.co's own public case pages. REST API and MCP access through Data.co are live for court opinions, case summaries and the citation graph. Previews on this site are synthetic samples titled [DEMO] that are never billed; the API returns live records. Bulk downloads stay closed until the provider confirms redistribution rights.
Each dataset page shows its status channel by channel, with the reason for anything that is not open, so you can plan an integration without guessing.
Jurisdictions: common questions
Does “U.S. state” mean all 50 states?
Not necessarily. It means the dataset contains state-court material. The estate-planning reference table is labeled for all 50 states in the catalog, but its completeness has not been confirmed by the provider.
Are territories and tribal courts covered?
Not as far as we can verify. We will only say so once the provider confirms it.
When will per-state counts appear?
When LAW.co exposes a metadata or statistics endpoint and signs off on the numbers. We will not estimate them.
Is coverage the same for every year?
No. The provider notes that coverage is uneven by year and court, including under-covered recent years.
More in the legal hub
Case Law
U.S.
Court Opinions
Federal and state court opinions from the LAW.co corpus: opinion text, court, decision date, docket, citations, judges and parties, with source provenance..
Federal
U.S.
State
U.S.
Legal Research
How to use LAW.co case law on the Data.co Marketplace for legal research tools and AI agents: retrieval, citation lookup, provenance and limits..
Statutes
Full statute corpora are not currently offered on the Data.co Marketplace.
Regulations
Federal and state regulations are not currently offered on the Data.co Marketplace.
Start building with live data.
API and MCP access is live. Sign up at app.data.co, create a scoped key, or talk to us about your use case.