Skip to content
Data.co Marketplace← Data.co for Enterprise
data.coMarketplace
Explore data

Popular datasets

Popularity will be ranked by real usage — API calls, MCP tool calls and saves. Public API access opened on 2026-11-06, so there is not yet enough usage to rank.

How this list is built: No popularity ranking is shown until there is metered usage to base it on. Below is every listed dataset, alphabetically.

No popularity data yet.

Rankings will appear once there is enough metered API and MCP usage to base them on. We will not publish view counts or download counts we cannot verify.

All datasets, A–Z

Every dataset currently listed, in alphabetical order.
LAW.coPremium

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.coPremium

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
LAW.coContact usRestricted

State Estate-Law Bill Monitor

Weekly LegiScan scan of state bills matching estate-planning keywords (wills, trusts, probate, POA, guardianship…), with status changes. Used internally to flag affected estate-planning matters.

Coverage
U.S. state (all 50)
Records
Not yet verified
  • REST
  • DOWNLOAD
LAW.coContact us

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
LAW.coStandard

U.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
Ranking method

What popularity will measure, and what it won't

Popularity is designed to be ranked from metered activity inside Data.co: API requests, MCP tool calls and saves. Those are events we record ourselves, so a ranking built on them can be checked against usage logs.

It will not be built from page views, social shares or download figures reported by a provider, because we cannot verify them. Until there is enough metered usage to rank, this page shows no ranking at all, and the list above is simply alphabetical.

That is a deliberate choice. A ranking of 5 datasets from a single provider, with REST access open for 3, would tell you nothing useful.

Choosing without a ranking

How to pick a dataset today

  1. 1

    Start from the task

    Need primary text for retrieval? Start with court opinions. Need navigation between cases? Look at the citation graph.

  2. 2

    Match the tier to your plan

    The tier tag on each card tells you whether a plan covers it or whether it is contact-only.

  3. 3

    Check what is open

    The channel badges at the bottom of each card show which access methods are open, waiting or not offered.

  4. 4

    Ask us

    If the right dataset is not listed, tell us what you are looking for.

Usage and plans

Usage will be metered against your plan

The same counters that feed popularity also drive plan quotas. Free ($0) has small monthly allowances for API requests, MCP calls and downloads; Pro ($149/mo) and Business ($799/mo) raise them and add premium datasets; Enterprise limits are set by contract.

REST requests to https://api.data.co/v1 and MCP calls to https://api.data.co/mcp share one key and are metered in one place, so an agent and an application count toward the same totals. Rankings are designed to use aggregate counts, not any one account's activity.

FAQ

Popularity questions

When will rankings appear?

After public API and MCP access opens and enough metered usage exists to compare datasets meaningfully. We have not set a date.

Will my usage be visible to others?

No. A popularity ranking is designed to show the order of datasets, not who is using them or how much any one customer uses.

Can a provider boost its ranking?

Rankings are designed to come only from metered usage. Editorial picks live on the featured list, which is separate and never paid.

Why show all datasets here instead of an empty page?

So the page is still useful. The A–Z list is labeled as such, and it will be replaced by a real ranking once there is data to support one.

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.