Messaging
Messagingmessaging
Providers using this tag (337)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 23 Complete, well-documented, and agent-ready
Strong 46 Solid coverage with minor gaps
Developing 79 Usable, with meaningful gaps to close
Thin 85 Limited public surface area
Emerging 47 Early or largely undocumented
Minimal 41 Almost no public developer surface
APIs with this tag (256)
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 42 Solid coverage with minor gaps
Developing 85 Usable, with meaningful gaps to close
Thin 77 Limited public surface area
Emerging 34 Early or largely undocumented
Minimal 4 Almost no public developer surface
Companies reaching this through an API (112)
These companies publish an API, specification or operation carrying “Messaging” 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.
Show all 112 companies ↓
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 311 providers in the APIs.io catalog tagged Messaging, 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 | 40.3 | 19.8 | +20.5 | 311 |
| Developer Ergonomics | 40.1 | 23.4 | +16.7 | 311 |
| Operational Transparency | 27.1 | 13.9 | +13.2 | 311 |
| Access Clarity | 39.5 | 26.5 | +13 | 311 |
| Discoverability | 68.1 | 61.2 | +6.9 | 311 |
| Contract Governance | 10.4 | 6.4 | +4 | 311 |
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) | 19% | 10% | +9 |
| MCP server (first-party) | 21% | 13% | +8 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 22% | 11% | +11 |
| Security | 97% | 96% | +1 |
| Arazzo workflows | 5% | 2% | +3 |
| Governance rules | 28% | 14% | +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 Customer.io 89.3
- 2 Brevo 87.3
- 3 Amazon Pinpoint 82.2
- 4 Braze 80.4
- 5 Svix 80.4
- 6 Boom Ai 79.9
- 7 Confluent 79
- 8 Nylas 76.6
- 9 Amazon SES 76.3
- 10 Infobip 75.4
- 1 Boom Ai 65.8
- 2 Birdeye 63.3
- 3 Cordial 62.9
- 4 Customer.io 62.1
- 5 Paubox 61.5
- 6 Nylas 59.3
- 7 Knock 58.6
- 8 Braze 55.9
- 9 MailerSend 55.4
- 10 Brevo 54.8
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.