Chatbots
ChatbotChatbots
Providers using this tag (136)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 9 Complete, well-documented, and agent-ready
Strong 9 Solid coverage with minor gaps
Developing 29 Usable, with meaningful gaps to close
Thin 30 Limited public surface area
Emerging 33 Early or largely undocumented
Minimal 25 Almost no public developer surface
Unrated 1 Not yet scored
APIs with this tag (37)
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 5 Complete, well-documented, and agent-ready
Strong 7 Solid coverage with minor gaps
Developing 13 Usable, with meaningful gaps to close
Thin 6 Limited public surface area
Emerging 6 Early or largely undocumented
Companies reaching this through an API (22)
These companies publish an API, specification or operation carrying “Chatbots” 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 125 providers in the APIs.io catalog tagged Chatbots, 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 | 41.5 | 30 | +11.5 | 125 |
| Developer Ergonomics | 33.1 | 24.5 | +8.6 | 125 |
| Contract Quality | 25.9 | 18.6 | +7.3 | 125 |
| Operational Transparency | 19.2 | 13.2 | +6 | 125 |
| Discoverability | 63 | 59.1 | +3.9 | 125 |
| Contract Governance | 13.5 | 9.7 | +3.8 | 125 |
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) | 20% | 18% | +2 |
| MCP server (first-party) | 21% | 16% | +5 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 15% | 13% | +2 |
| Security | 98% | 99% | -1 |
| Arazzo workflows | 2% | 1% | +1 |
| Governance rules | 47% | 36% | +11 |
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 Ada 88
- 2 OpenAI 82.5
- 3 Amazon Lex 80
- 4 Corebee 77.8
- 5 Google Dialogflow 74.7
- 6 SendPulse 72.3
- 7 LINE 71.3
- 8 sitegpt-ai 69.5
- 9 Khoros 67.8
- 10 communicate-so 65.2
- 1 sitegpt-ai 66.2
- 2 Corebee 61.3
- 3 OpenAI 58.4
- 4 Causerie 58
- 5 communicate-so 55
- 6 SendPulse 54.5
- 7 Animam.ai 53.7
- 8 trilo-chat 48.4
- 9 LINE 47.9
- 10 Ada 47.4
Coverage caveat. 94 of 125 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.