Data Enrichment
Enrichmentb2b-data-enrichmentData Enrichment
Providers using this tag (108)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 16 Complete, well-documented, and agent-ready
Strong 36 Solid coverage with minor gaps
Developing 27 Usable, with meaningful gaps to close
Thin 13 Limited public surface area
Emerging 9 Early or largely undocumented
Minimal 7 Almost no public developer surface
APIs with this tag (71)
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 13 Complete, well-documented, and agent-ready
Strong 18 Solid coverage with minor gaps
Developing 18 Usable, with meaningful gaps to close
Thin 13 Limited public surface area
Emerging 9 Early or largely undocumented
Companies reaching this through an API (26)
These companies publish an API, specification or operation carrying “Data Enrichment” 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
Where this tag sits
108 providers carry this tag directly, and 111 counting the 8 narrower tags below — 3 more to reach.
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 107 providers in the APIs.io catalog tagged Data Enrichment, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Access Clarity | 61.2 | 23.9 | +37.3 | 107 |
| Operational Transparency | 40.4 | 13 | +27.4 | 107 |
| Developer Ergonomics | 49.9 | 23.2 | +26.7 | 107 |
| Contract Quality | 40.6 | 17.2 | +23.4 | 107 |
| Discoverability | 71.2 | 57.9 | +13.3 | 107 |
| Contract Governance | 16 | 6.5 | +9.5 | 107 |
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) | 60% | 13% | +47 |
| MCP server (first-party) | 58% | 12% | +46 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 38% | 11% | +27 |
| Security | 100% | 98% | +2 |
| Arazzo workflows | 5% | 2% | +3 |
| Governance rules | 21% | 16% | +5 |
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 Cracked API 69.2
- 2 The Hog 65.6
- 3 Infinite Audience 65.2
- 4 lemlist 65
- 5 Parallel 64.7
- 6 ZoomInfo 64.3
- 7 Sumble 62.3
- 8 Ploid 60.9
- 9 DeBounce 60.8
- 10 Lusha 60.7
Coverage caveat. 58 of 107 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 24 October 2026, across 31984 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.