Data Enrichment
Enrichmentb2b-data-enrichmentData Enrichment
Providers using this tag (139)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 21 Complete, well-documented, and agent-ready
Strong 45 Solid coverage with minor gaps
Developing 32 Usable, with meaningful gaps to close
Thin 21 Limited public surface area
Emerging 13 Early or largely undocumented
Minimal 7 Almost no public developer surface
APIs with this tag (82)
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 16 Complete, well-documented, and agent-ready
Strong 21 Solid coverage with minor gaps
Developing 21 Usable, with meaningful gaps to close
Thin 15 Limited public surface area
Emerging 8 Early or largely undocumented
Minimal 1 Almost no public developer surface
Companies reaching this through an API (33)
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
139 providers carry this tag directly, and 145 counting the 8 narrower tags below — 6 more to reach.
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 132 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 | 62.7 | 30 | +32.7 | 132 |
| Developer Ergonomics | 50.7 | 24.5 | +26.2 | 132 |
| Contract Quality | 41.1 | 18.6 | +22.5 | 132 |
| Operational Transparency | 35.1 | 13.2 | +21.9 | 132 |
| Contract Governance | 21.9 | 9.7 | +12.2 | 132 |
| Discoverability | 70.2 | 59.1 | +11.1 | 132 |
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) | 56% | 18% | +38 |
| MCP server (first-party) | 55% | 16% | +39 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 36% | 13% | +23 |
| Security | 100% | 99% | +1 |
| Arazzo workflows | 4% | 1% | +3 |
| Governance rules | 71% | 36% | +35 |
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 ZoomInfo 86.8
- 2 Surfe 77.3
- 3 lemlist 76
- 4 Lusha 73.9
- 5 Unify 72.2
- 6 Leadspace 71.2
- 7 Context.dev 70.4
- 8 Spade 70.2
- 9 Demandbase 70.1
- 10 Coresignal 69.7
- 1 AnyAPI 73.5
- 2 Infinite Audience 70.3
- 3 Cracked API 69.2
- 4 Parallel 66.1
- 5 The Hog 65.6
- 6 lemlist 65
- 7 ZoomInfo 64.3
- 8 FullEnrich 63.5
- 9 LastDatabase 63.4
- 10 Sumble 62.3
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.