SMS
SMSSmssms
Providers using this tag (160)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 32 Complete, well-documented, and agent-ready
Strong 39 Solid coverage with minor gaps
Developing 34 Usable, with meaningful gaps to close
Thin 28 Limited public surface area
Emerging 11 Early or largely undocumented
Minimal 14 Almost no public developer surface
Unrated 2 Not yet scored
APIs with this tag (98)
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 14 Complete, well-documented, and agent-ready
Strong 23 Solid coverage with minor gaps
Developing 23 Usable, with meaningful gaps to close
Thin 24 Limited public surface area
Emerging 11 Early or largely undocumented
Minimal 3 Almost no public developer surface
Companies reaching this through an API (35)
These companies publish an API, specification or operation carrying “SMS” 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
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 157 providers in the APIs.io catalog tagged SMS, 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 | 50.6 | 19.8 | +30.8 | 157 |
| Operational Transparency | 40.9 | 13.9 | +27 | 157 |
| Developer Ergonomics | 48.6 | 23.4 | +25.2 | 157 |
| Access Clarity | 50.6 | 26.5 | +24.1 | 157 |
| Discoverability | 69.5 | 61.2 | +8.3 | 157 |
| Contract Governance | 11.9 | 6.4 | +5.5 | 157 |
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) | 26% | 10% | +16 |
| MCP server (first-party) | 29% | 13% | +16 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 29% | 11% | +18 |
| Security | 99% | 96% | +3 |
| Arazzo workflows | 6% | 2% | +4 |
| Governance rules | 25% | 14% | +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 Customer.io 89.3
- 2 Brevo 87.3
- 3 Salesforce Marketing Cloud 82.6
- 4 Amazon Pinpoint 82.2
- 5 Braze 80.4
- 6 Stannp 80.1
- 7 OneSignal 80
- 8 Boom Ai 79.9
- 9 Klaviyo 79.1
- 10 Close 78.8
- 1 OneSignal 75.4
- 2 MoEngage 67.8
- 3 Boom Ai 65.8
- 4 Cordial 62.9
- 5 Customer.io 62.1
- 6 Knock 58.6
- 7 Salesforce Marketing Cloud 57.9
- 8 Close 57.4
- 9 Mapp Marketing Cloud 56.3
- 10 Braze 55.9
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.