Enrichment
Enrichmentenrichment
Providers using this tag (47)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 9 Complete, well-documented, and agent-ready
Strong 15 Solid coverage with minor gaps
Developing 12 Usable, with meaningful gaps to close
Thin 6 Limited public surface area
Minimal 1 Almost no public developer surface
APIs with this tag (52)
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 17 Solid coverage with minor gaps
Developing 12 Usable, with meaningful gaps to close
Thin 7 Limited public surface area
Emerging 3 Early or largely undocumented
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 47 providers in the APIs.io catalog tagged 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 | 56.4 | 22.3 | +34.1 | 47 |
| Contract Quality | 50.9 | 17.5 | +33.4 | 47 |
| Developer Ergonomics | 47.3 | 17.9 | +29.4 | 47 |
| Operational Transparency | 40.6 | 11.3 | +29.3 | 47 |
| Discoverability | 79.8 | 60.4 | +19.4 | 47 |
| Contract Governance | 22.2 | 6.4 | +15.8 | 47 |
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) | 66% | 16% | +50 |
| MCP server (first-party) | 47% | 7% | +40 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 43% | 9% | +34 |
| Security | 100% | 88% | +12 |
| Arazzo workflows | 11% | 2% | +9 |
| Governance rules | 23% | 13% | +10 |
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 80.8
- 2 6sense 73.1
- 3 Lusha 71.7
- 4 Coresignal 71.4
- 5 Surfe 70.6
- 6 Seamless.AI 69.8
- 7 Dun & Bradstreet 67.9
- 8 Koala 67
- 9 Leadspace 67
- 10 Logz.io 65.2
- 1 Seamless.AI 58.7
- 2 Lusha 57.6
- 3 Apollo.io 55.3
- 4 Lean Technologies 53.2
- 5 6sense 50.4
- 6 ZoomInfo 49.5
- 7 Leadspace 48.8
- 8 Koala 48.6
- 9 toksta 48.2
- 10 Coresignal 47.5
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/tags/enrichment"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/enrichment"
curl "https://apis.io/api/v1/cohorts/tag/enrichment/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.