Push Notifications
Push NotificationsPush notificationsPushNotificationspush-notifications
Providers using this tag (51)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 13 Complete, well-documented, and agent-ready
Strong 10 Solid coverage with minor gaps
Developing 10 Usable, with meaningful gaps to close
Thin 10 Limited public surface area
Emerging 6 Early or largely undocumented
Minimal 1 Almost no public developer surface
Unrated 1 Not yet scored
APIs with this tag (34)
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 8 Complete, well-documented, and agent-ready
Strong 3 Solid coverage with minor gaps
Developing 7 Usable, with meaningful gaps to close
Thin 6 Limited public surface area
Emerging 10 Early or largely undocumented
Companies reaching this through an API (16)
These companies publish an API, specification or operation carrying “Push Notifications” 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 50 providers in the APIs.io catalog tagged Push Notifications, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Operational Transparency | 45.8 | 14 | +31.8 | 50 |
| Developer Ergonomics | 52.9 | 23.4 | +29.5 | 50 |
| Access Clarity | 54.6 | 26.5 | +28.1 | 50 |
| Contract Quality | 47 | 19.8 | +27.2 | 50 |
| Discoverability | 69.2 | 61.2 | +8 | 50 |
| Contract Governance | 14.4 | 6.4 | +8 | 50 |
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) | 31% | 10% | +21 |
| MCP server (first-party) | 33% | 13% | +20 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 27% | 11% | +16 |
| Security | 100% | 97% | +3 |
| Arazzo workflows | 6% | 2% | +4 |
| Governance rules | 29% | 14% | +15 |
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 Amazon Pinpoint 82.2
- 3 Braze 80.4
- 4 OneSignal 80
- 5 Listrak 77
- 6 Adobe Campaign 74.9
- 7 Mapp Marketing Cloud 74.8
- 8 iOS 73.1
- 9 Iterable 73
- 10 MoEngage 71.5
- 1 OneSignal 75.4
- 2 MoEngage 67.8
- 3 Cordial 62.9
- 4 Customer.io 62.1
- 5 Mapp Marketing Cloud 56.3
- 6 Braze 55.9
- 7 Acoustic 53
- 8 WoowUp 52.9
- 9 Insider 51.6
- 10 CleverTap 47.5
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.