emerging · -1.1 capability resource

Data Lineage

Score 20.9 / 100 25 providers +15 via APIs 29 APIs Search apis.io →
Variants seen in the corpus: LineageData Lineage

Providers using this tag (25)

Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.

Exemplar 2 Complete, well-documented, and agent-ready
Strong 5 Solid coverage with minor gaps
Developing 6 Usable, with meaningful gaps to close
Thin 4 Limited public surface area
Emerging 6 Early or largely undocumented
Minimal 2 Almost no public developer surface

APIs with this tag (29)

Ranked by the provider's API Evangelist rating — the Kin Score is scored per provider, not per API, so every API of a provider shares its band. How the rating works →

Exemplar 8 Complete, well-documented, and agent-ready
Strong 5 Solid coverage with minor gaps
Developing 7 Usable, with meaningful gaps to close
Thin 6 Limited public surface area
Emerging 3 Early or largely undocumented

Companies reaching this through an API (15)

These companies publish an API, specification or operation carrying “Data Lineage” but do not classify their business under it. Listed unranked and kept out of the count above, because one tagged operation is not a statement about what a company does.

Acceldata Altimate AI Amazon DataZone Cask CrawlCheck data.world EvalGate Google Cloud Data Catalog Kubeflow Pipelines LF AI and Data Microsoft Azure Microsoft Purview PostHog Tableau Tableau Desktop

Score breakdown

Frequency
46.6
log-scaled weighted occurrences
Breadth
0.3
spread across providers
Quality lift
39.0
mean composite of providers using it
Cohesion
9.2
strength of nearest seed neighbor

Related tags

Data Governance 24 co-occurrences Data Observability 9 co-occurrences Data Quality 17 co-occurrences Metadata Management 5 co-occurrences Glossary 7 co-occurrences Data Discovery 5 co-occurrences Data Catalog 20 co-occurrences Tables 7 co-occurrences

Where this tag comes from

Api tag28
Provider tag25
Openapi tag10
Openapi op tag44

Cohort brief

Auto-generated

The 24 providers in the APIs.io catalog tagged Data Lineage, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.

Providers
24
of 25 in the catalog
Mean Kin Score
38.7
+14.6 vs catalog 24.1
Mean Agent Readiness
22.4
+8.3 vs catalog 14.1
Spread
2.6–71.4
median 39.3 · σ 20.5
How the 24 split by band
Exemplar 2Strong 5Developing 5Thin 4Emerging 6Minimal 2
Facet averages, against the whole catalog
FacetThis cohortCatalogDifferenceScored
Developer Ergonomics 42.6 24.5 +18.1 24
Operational Transparency 30.8 13.2 +17.6 24
Access Clarity 42.3 30 +12.3 24
Contract Quality 29.8 18.6 +11.2 24
Discoverability 66.5 59.1 +7.4 24
Contract Governance 14.3 9.7 +4.6 24

A facet is averaged over the members that carry it, not over the whole cohort — the “Scored” column is that count. Averaging an absent facet as zero would score our own coverage gaps as the providers’ posture.

What this cohort publishes
ArtifactThis cohortCatalogDifference
MCP server (any) 42% 18% +24
MCP server (first-party) 42% 16% +26
Agent Skills 0% 0% 0
OAuth scopes 8% 13% -5
Security 100% 99% +1
Arazzo workflows 4% 1% +3
Governance rules 50% 36% +14

mcp_pct counts any mcp/ artifact including ones API Evangelist derived from the provider OpenAPI; mcp_first_party_pct counts only servers the provider publishes. Prefer the latter.

Top by Kin Score
  1. 1 Sifflet 71.4
  2. 2 Monte Carlo 71
  3. 3 Collate 66.4
  4. 4 Bigeye 61.2
  5. 5 Metaplane 60.5
  6. 6 Decube 58
  7. 7 DataHub 57.4
  8. 8 Select Star 50.6
  9. 9 Validio 50.6
  10. 10 Secoda 47.5
Top by Agent Readiness
  1. 1 Collate 65.9
  2. 2 Monte Carlo 62.9
  3. 3 DataHub 48.9
  4. 4 Sifflet 35.6
  5. 5 Bigeye 34.6
  6. 6 OpenMetadata 31.8
  7. 7 Foundational 31.3
  8. 8 Decube 28.4
  9. 9 Atlan 28.3
  10. 10 Apache Atlas 27.8
All 25 members of this roster resolve to a provider in the catalog; 24 carry a score (96%). The figures above describe the scored members only.
Coverage caveat. 17 of 24 scored members had under half their catalog-attributable points satisfied at all (catalog_earned / catalog_max < 0.5). They are INCLUDED in the mean above. A large share here means the cohort mean is partly a measurement of how far our enrichment reached, not only of how these providers publish.Generated from the catalog build of 14 November 2026, across 41591 providers, using the same computation served by the APIs.io cohort API. Briefs are published for rosters of 5 or more scored providers; below that a distribution is not meaningful.

Work with this as data

Every tag here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for tags

7 MCP tools reach this
  • find_tagsBrowse and filter every tag in the catalog.
  • get_cohortThis tag as a scored cohort — every provider carrying it, with scores.
  • cohort_statsPRO — the distribution across this tag: mean, median, band split, adoption rates.
  • cohort_rankingsPRO — the leaderboard, on composite AND agent-readiness axes.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This tag
curl "https://apis.io/api/v1/tags/data-lineage"
All tags
curl "https://apis.io/api/v1/tags?limit=25"
As a scored cohort (paid plan)
The distribution (Pro)

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.