emerging · -1.2 marketcapability domainschema

Data Lake

Score 20.3 / 100 26 providers +7 via APIs 11 APIs Search apis.io →
Variants seen in the corpus: Data LakesData Lake

Providers using this tag (26)

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

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

APIs with this tag (11)

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 4 Complete, well-documented, and agent-ready
Strong 2 Solid coverage with minor gaps
Developing 1 Usable, with meaningful gaps to close
Thin 2 Limited public surface area
Emerging 2 Early or largely undocumented

Companies reaching this through an API (7)

These companies publish an API, specification or operation carrying “Data Lake” 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.

Amazon Supply Chain Amazon Web Services Azure Blob Storage Cloudera LF AI and Data SAP HANA UBIX Labs

Score breakdown

Frequency
40.0
log-scaled weighted occurrences
Breadth
0.3
spread across providers
Quality lift
46.4
mean composite of providers using it
Cohesion
6.3
strength of nearest seed neighbor

Related tags

Data Warehouse 5 co-occurrences Big Data 7 co-occurrences ETL 5 co-occurrences Amazon Web Services 5 co-occurrences Storage 5 co-occurrences Tags 5 co-occurrences Metadata 5 co-occurrences Cloud 6 co-occurrences

Where this tag comes from

Provider tag26
Api tag11
Openapi tag2

Cohort brief

Auto-generated

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

Providers
24
of 26 in the catalog
Mean Kin Score
46.4
+22.3 vs catalog 24.1
Mean Agent Readiness
26.8
+12.7 vs catalog 14.1
Spread
19.1–75.1
median 45.5 · σ 16.4
How the 24 split by band
Exemplar 4Strong 3Developing 8Thin 7Emerging 2Minimal 0
Facet averages, against the whole catalog
FacetThis cohortCatalogDifferenceScored
Developer Ergonomics 51.3 24.5 +26.8 24
Contract Quality 41.8 18.6 +23.2 24
Access Clarity 51.2 30 +21.2 24
Operational Transparency 30.6 13.2 +17.4 24
Contract Governance 22.3 9.7 +12.6 24
Discoverability 70.8 59.1 +11.7 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) 27% 18% +9
MCP server (first-party) 27% 16% +11
Agent Skills 0% 0% 0
OAuth scopes 19% 13% +6
Security 96% 99% -3
Arazzo workflows 8% 1% +7
Governance rules 73% 36% +37

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 Amazon Redshift 75.1
  2. 2 Amazon Security Lake 74.6
  3. 3 Monte Carlo 71
  4. 4 Cumulocity 68.5
  5. 5 Amazon Lake Formation 66.2
  6. 6 Azure Data Lake Storage 64.9
  7. 7 Panther 56.9
  8. 8 Cribl 51.6
  9. 9 Apache Iceberg 47.3
  10. 10 Delta Lake 47.3
Top by Agent Readiness
  1. 1 Monte Carlo 62.9
  2. 2 Amazon Redshift 45.5
  3. 3 Ryft 42.6
  4. 4 Apache Iceberg 41
  5. 5 Amazon Lake Formation 36.9
  6. 6 Eon 35.5
  7. 7 Panther 34.5
  8. 8 InfoLang Inc. 34.4
  9. 9 lakeFS 34.3
  10. 10 Delta Lake 31.8
All 26 members of this roster resolve to a provider in the catalog; 24 carry a score (92%). The figures above describe the scored members only.
Coverage caveat. 15 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-lake"
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.