Communications
CommunicationCommunications
Providers using this tag (174)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 12 Complete, well-documented, and agent-ready
Strong 22 Solid coverage with minor gaps
Developing 28 Usable, with meaningful gaps to close
Thin 35 Limited public surface area
Emerging 33 Early or largely undocumented
Minimal 44 Almost no public developer surface
APIs with this tag (61)
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 7 Complete, well-documented, and agent-ready
Strong 12 Solid coverage with minor gaps
Developing 14 Usable, with meaningful gaps to close
Thin 13 Limited public surface area
Emerging 15 Early or largely undocumented
Companies reaching this through an API (37)
These companies publish an API, specification or operation carrying “Communications” 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
174 providers carry this tag directly, and 318 counting the 4 narrower tags below and the 3 beneath them — 144 more to reach.
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 158 providers in the APIs.io catalog tagged Communications, 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 | 31.2 | 17.6 | +13.6 | 158 |
| Access Clarity | 39.7 | 26.5 | +13.2 | 158 |
| Developer Ergonomics | 34.5 | 23.2 | +11.3 | 158 |
| Operational Transparency | 24.8 | 13.7 | +11.1 | 158 |
| Discoverability | 63.7 | 58.1 | +5.6 | 158 |
| Contract Governance | 10.1 | 6.3 | +3.8 | 158 |
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) | 23% | 14% | +9 |
| MCP server (first-party) | 22% | 12% | +10 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 22% | 11% | +11 |
| Security | 100% | 98% | +2 |
| Arazzo workflows | 4% | 2% | +2 |
| Governance rules | 20% | 14% | +6 |
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 Nylas 93.2
- 2 Infobip 82.4
- 3 Telnyx 79.6
- 4 Amazon Pinpoint 78.9
- 5 Twilio 77.8
- 6 Leadping 74.9
- 7 Loops 71.4
- 8 SMTP2GO 69
- 9 Mailboxlayer 68.9
- 10 Sinch 68.3
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.