All datasets
5 datasets from one provider today (LAW.co). Every listing shows its real access status, license and coverage — including what is not available yet.
4 of 5 datasets
Access method: REST APIU.S. Court Opinions (LAW.co corpus)
Federal and state court opinions in the LAW.co corpus: opinion text, case name, court, jurisdiction, decision date, docket number, reporter citations, judges, parties and attorneys. Legacy corpus is Caselaw Access Project-structured; newer opinions are ingested from CourtListener plain text behind LAW.co's copyright gate.
- Coverage
- U.S. federal, U.S. state (all 50)
- Records
- Not yet verified
- WEB
- REST
- MCP
- DOWNLOAD
LAW.co AI Case Summaries
LAW.co-generated plain-language summary, holding, key issues, topics and procedural posture for a prominence-selected subset of cases. Only enrichment that passed LAW.co's QA gate (published / approved / auto) is exposed. Machine-generated; not citable as authority.
- Coverage
- U.S. federal, U.S. state
- Records
- Not yet verified
- WEB
- REST
- MCP
- DOWNLOAD
LAW.co Case Citation Graph
Directed citation edges between cases (citing case → cited authority, with pin cite), seeded from CAP cites_to data and extended with eyecite extraction on ingest. Exposed per case as 'authorities cited' and 'cited by'.
- Coverage
- U.S. federal, U.S. state
- Records
- Not yet verified
- WEB
- REST
- MCP
- DOWNLOAD
State Estate-Planning Statute Reference Values
Small curated table of state-level estate-planning provisions (state, category, provision, value, effective date, source URL) maintained by LAW.co to drive estate-planner document generation and staleness checks. Not a statute corpus.
- Coverage
- U.S. state
- Records
- Not yet verified
- REST
- MCP
- DOWNLOAD
Access badges: blue = available now; grey = listed but not yet connected or awaiting rights confirmation; struck through = not offered. Record counts are shown only once verified with the provider.
Keyword search and ten filters, all from the catalog
The keyword box matches every word you type against a listing's title, description, category, provider name, document types, source names and schema field names. A dataset is shown only if all of your words appear somewhere in that text, so adding words narrows the results rather than widening them.
Each filter reads a field the provider declared: category, provider, federal or state coverage, access channel, pricing tier, redistribution license, update frequency, file format and data type. The access filter keeps any dataset that lists a channel at all, even if that channel is still awaiting credentials; the badge on the card tells you its real status.
Filtered result pages are kept out of search engines and point back to this unfiltered listing, so share the URL with a colleague rather than expecting to find it in a search engine.
Four things to check on any listing
- 1
Coverage
Jurisdictions and coverage notes say where a dataset is thin. LAW.co's opinions, for example, note uneven coverage by year and court.
- 2
Record count
Counts appear only once verified with the provider. Right now 0 listings show a verified count; the rest say "Not yet verified" instead of an estimate.
- 3
Access status
Blue badges are open, grey badges are waiting on the provider, and struck-through badges are not offered. Plan around what is open, not what is listed.
- 4
Provenance and license
Each listing names its upstream sources and license. Derived layers, such as AI summaries, are licensed differently from the source text they summarize.
From a search result to an API call
Every result is designed to be addressable by its slug through the REST API at https://api.data.co/v1 (dataset metadata, schema and records) and through the MCP server at https://api.data.co/mcp, so an agent can run the same search you just ran. See REST access and MCP access for the details.
The pricing tier on each card decides which plan covers it: free and standard tiers on Free ($0), premium on Pro ($149/mo) and Business ($799/mo), and contact-only tiers through an Enterprise agreement. Of the 5 listings, 1 is standard, 2 premium and 2 contact-only.
Searching the catalog
Why do most filter combinations return nothing?
All current listings come from one legal-data provider, so filters for other categories, provider names or formats it does not use correctly return an empty result.
Are results ranked?
No relevance score is applied. Matching datasets are shown in catalog order, and the result count tells you how many of the total matched.
Is search available through the API?
The API's dataset list endpoint is designed to accept the same kinds of filters, including keyword, category, provider, tier and access channel, so you can reproduce a search in code.
Can I save a search?
Not as a search. Bookmark the filtered URL to return to it. In the Data.co app, every account, including Free, can also save individual datasets into named collections.
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.