Natural Language Processing
Providers using this tag (79)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 2 Complete, well-documented, and agent-ready
Strong 5 Solid coverage with minor gaps
Developing 18 Usable, with meaningful gaps to close
Thin 13 Limited public surface area
Emerging 14 Early or largely undocumented
Minimal 26 Almost no public developer surface
Unrated 1 Not yet scored
APIs with this tag (21)
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 3 Complete, well-documented, and agent-ready
Strong 2 Solid coverage with minor gaps
Developing 2 Usable, with meaningful gaps to close
Thin 9 Limited public surface area
Emerging 5 Early or largely undocumented
Companies reaching this through an API (8)
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
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 68 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 | 25.9 | 17.6 | +8.3 | 68 |
| Developer Ergonomics | 31 | 23.2 | +7.8 | 68 |
| Access Clarity | 34.1 | 26.5 | +7.6 | 68 |
| Operational Transparency | 20.9 | 13.7 | +7.2 | 68 |
| Discoverability | 61.9 | 58.1 | +3.8 | 68 |
| Contract Governance | 10.1 | 6.3 | +3.8 | 68 |
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) | 7% | 14% | -7 |
| MCP server (first-party) | 6% | 12% | -6 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 13% | 11% | +2 |
| Security | 96% | 98% | -2 |
| Arazzo workflows | 4% | 2% | +2 |
| Governance rules | 32% | 14% | +18 |
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 78.1
- 2 Google Dialogflow 67.4
- 3 Hugging Face Transformers 60
- 4 Actionpower 57.3
- 5 Amazon Comprehend 57.3
- 6 DreamThreads 57.3
- 7 fatsecret 55.2
- 8 Claude 53.6
- 9 Microsoft 365 Copilot 51.8
- 10 Allo-Media 50.9
- 1 Kensho 51.1
- 2 Hugging Face Transformers 49.2
- 3 Allo-Media 37.8
- 4 Google Dialogflow 35.7
- 5 Amazon Lex 34.1
- 6 Actionpower 33.6
- 7 DreamThreads 32.4
- 8 Lang.ai 31.8
- 9 DetectLanguage 30.6
- 10 Yandex Translate API 30.6
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.