Messaging
Messagingmessaging
Providers using this tag (451)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 30 Complete, well-documented, and agent-ready
Strong 56 Solid coverage with minor gaps
Developing 125 Usable, with meaningful gaps to close
Thin 117 Limited public surface area
Emerging 68 Early or largely undocumented
Minimal 55 Almost no public developer surface
APIs with this tag (320)
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 30 Complete, well-documented, and agent-ready
Strong 52 Solid coverage with minor gaps
Developing 108 Usable, with meaningful gaps to close
Thin 83 Limited public surface area
Emerging 41 Early or largely undocumented
Minimal 6 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 451 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.8 | 17.5 | +23.3 | 451 |
| Developer Ergonomics | 36 | 17.9 | +18.1 | 451 |
| Access Clarity | 37.3 | 22.3 | +15 | 451 |
| Operational Transparency | 25.6 | 11.3 | +14.3 | 451 |
| Discoverability | 70.3 | 60.4 | +9.9 | 451 |
| Contract Governance | 13.6 | 6.4 | +7.2 | 451 |
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) | 32% | 16% | +16 |
| MCP server (first-party) | 16% | 7% | +9 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 24% | 9% | +15 |
| Security | 95% | 88% | +7 |
| Arazzo workflows | 8% | 2% | +6 |
| Governance rules | 32% | 13% | +19 |
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 Brevo 87.3
- 2 Customer.io 87.3
- 3 Elation Health 84.1
- 4 Salesforce Marketing Cloud 83.5
- 5 Salesforce 83.3
- 6 Amazon Pinpoint 83.1
- 7 HubSpot 82.4
- 8 Braze 81.2
- 9 Amazon SES 79.7
- 10 Svix 79.2
- 1 Boom Ai 71.9
- 2 Cordial 62.9
- 3 Adobe Suite 61.5
- 4 Birdeye 61
- 5 Sarj AI Developer API 60.4
- 6 OneSignal 59.2
- 7 Knock 58.6
- 8 Mapp Marketing Cloud 56.3
- 9 Salesforce Marketing Cloud 56.2
- 10 SendPulse 55.8
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for tags
7 MCP tools reach this
find_tagsBrowse and filter every tag in the catalog.get_cohortThis tag as a scored cohort — every provider carrying it, with scores.cohort_statsPRO — the distribution across this tag: mean, median, band split, adoption rates.cohort_rankingsPRO — the leaderboard, on composite AND agent-readiness axes.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/tags/messaging"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/messaging"
curl "https://apis.io/api/v1/cohorts/tag/messaging/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.