Data Lake
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
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
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.
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 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.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| 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.
| Artifact | This cohort | Catalog | Difference |
|---|---|---|---|
| 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.
- 1 Amazon Redshift 75.1
- 2 Amazon Security Lake 74.6
- 3 Monte Carlo 71
- 4 Cumulocity 68.5
- 5 Amazon Lake Formation 66.2
- 6 Azure Data Lake Storage 64.9
- 7 Panther 56.9
- 8 Cribl 51.6
- 9 Apache Iceberg 47.3
- 10 Delta Lake 47.3
- 1 Monte Carlo 62.9
- 2 Amazon Redshift 45.5
- 3 Ryft 42.6
- 4 Apache Iceberg 41
- 5 Amazon Lake Formation 36.9
- 6 Eon 35.5
- 7 Panther 34.5
- 8 InfoLang Inc. 34.4
- 9 lakeFS 34.3
- 10 Delta Lake 31.8
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.