Natural Language Processing
NLPNatural Language Processing
Providers using this tag (108)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 6 Complete, well-documented, and agent-ready
Strong 8 Solid coverage with minor gaps
Developing 16 Usable, with meaningful gaps to close
Thin 22 Limited public surface area
Emerging 24 Early or largely undocumented
Minimal 31 Almost no public developer surface
Unrated 1 Not yet scored
APIs with this tag (49)
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 6 Complete, well-documented, and agent-ready
Strong 3 Solid coverage with minor gaps
Developing 6 Usable, with meaningful gaps to close
Thin 13 Limited public surface area
Emerging 21 Early or largely undocumented
Companies reaching this through an API (18)
These companies publish an API, specification or operation carrying “Natural Language Processing” 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 170 counting the 6 narrower tags below — 62 more to reach.
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 95 providers in the APIs.io catalog tagged Natural Language Processing, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Contract Quality | 27.8 | 18.6 | +9.2 | 95 |
| Operational Transparency | 20.7 | 13.2 | +7.5 | 95 |
| Developer Ergonomics | 31.9 | 24.5 | +7.4 | 95 |
| Discoverability | 63 | 59.1 | +3.9 | 95 |
| Contract Governance | 12.7 | 9.7 | +3 | 95 |
| Access Clarity | 32.5 | 30 | +2.5 | 95 |
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) | 14% | 18% | -4 |
| MCP server (first-party) | 13% | 16% | -3 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 17% | 13% | +4 |
| Security | 96% | 99% | -3 |
| Arazzo workflows | 2% | 1% | +1 |
| Governance rules | 50% | 36% | +14 |
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 Lex 80
- 2 Google Dialogflow 74.7
- 3 Amazon Translate 73.7
- 4 Amazon Comprehend 70.7
- 5 AWS HealthLake 70
- 6 Google Cloud Translation API 68
- 7 Google Cloud Natural Language 66.1
- 8 classifier-dev 65.4
- 9 Hugging Face Transformers 65.4
- 10 Microsoft 365 Copilot 62.8
- 1 classifier-dev 65.2
- 2 Deepset 54.4
- 3 Kensho 51.1
- 4 Hugging Face Transformers 48.5
- 5 AWS HealthLake 47.2
- 6 Cohere 41.4
- 7 Allo-Media 37.8
- 8 Unwrap 36.9
- 9 Google Cloud Natural Language 36.1
- 10 Amazon Translate 36
Coverage caveat. 75 of 95 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.