Notification
notificationsNotification
Providers using this tag (56)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 7 Complete, well-documented, and agent-ready
Strong 8 Solid coverage with minor gaps
Developing 8 Usable, with meaningful gaps to close
Thin 13 Limited public surface area
Emerging 13 Early or largely undocumented
Minimal 7 Almost no public developer surface
APIs with this tag (556)
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 89 Complete, well-documented, and agent-ready
Strong 130 Solid coverage with minor gaps
Developing 172 Usable, with meaningful gaps to close
Thin 123 Limited public surface area
Emerging 32 Early or largely undocumented
Minimal 10 Almost no public developer surface
Companies reaching this through an API (507)
These companies publish an API, specification or operation carrying “Notification” 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 507 companies ↓
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 51 providers in the APIs.io catalog tagged Notification, 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 | 42.5 | 18.6 | +23.9 | 51 |
| Operational Transparency | 29.7 | 13.2 | +16.5 | 51 |
| Developer Ergonomics | 37.3 | 24.5 | +12.8 | 51 |
| Access Clarity | 41.2 | 30 | +11.2 | 51 |
| Contract Governance | 16.1 | 9.7 | +6.4 | 51 |
| Discoverability | 65.3 | 59.1 | +6.2 | 51 |
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% | 18% | +13 |
| MCP server (first-party) | 33% | 16% | +17 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 18% | 13% | +5 |
| Security | 100% | 99% | +1 |
| Arazzo workflows | 4% | 1% | +3 |
| Governance rules | 73% | 36% | +37 |
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 Amazon SES 83.8
- 2 AfterShip 83.3
- 3 OneSignal 76.8
- 4 Novu 71.7
- 5 Amazon Health Dashboard 69
- 6 PagoPA 68.3
- 7 Entergram 66.9
- 8 Liveblocks 66.2
- 9 Amazon SNS 64.4
- 10 Kudosity 64.2
- 1 OneSignal 71.3
- 2 Novu 61.2
- 3 AfterShip 60.4
- 4 Entergram 60.4
- 5 Knock 57.4
- 6 AnnounceKit 52.2
- 7 Kudosity 49.2
- 8 PagoPA 49
- 9 Amazon SNS 42.6
- 10 Neynar 41.7
Coverage caveat. 28 of 51 scored members had under half their catalog-attributable points satisfied at all (catalog_earned / catalog_max < 0.5). They are INCLUDED in the mean above. A large share here means the cohort mean is partly a measurement of how far our enrichment reached, not only of how these providers publish.Generated from the catalog build of 14 November 2026, across 41591 providers, using the same computation served by the APIs.io cohort API. Briefs are published for rosters of 5 or more scored providers; below that a distribution is not meaningful.
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.