Alerts
Providers using this tag (60)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Strong 7 Solid coverage with minor gaps
Developing 14 Usable, with meaningful gaps to close
Thin 19 Limited public surface area
Emerging 15 Early or largely undocumented
Minimal 4 Almost no public developer surface
APIs with this tag (313)
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 65 Complete, well-documented, and agent-ready
Strong 73 Solid coverage with minor gaps
Developing 77 Usable, with meaningful gaps to close
Thin 74 Limited public surface area
Emerging 20 Early or largely undocumented
Minimal 4 Almost no public developer surface
Companies reaching this through an API (265)
These companies publish an API, specification or operation carrying “Alerts” 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 265 companies ↓
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 55 providers in the APIs.io catalog tagged Alerts, 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 | 34.2 | 18.6 | +15.6 | 55 |
| Access Clarity | 40.4 | 30 | +10.4 | 55 |
| Developer Ergonomics | 34.1 | 24.5 | +9.6 | 55 |
| Discoverability | 65.7 | 59.1 | +6.6 | 55 |
| Contract Governance | 15.8 | 9.7 | +6.1 | 55 |
| Operational Transparency | 19 | 13.2 | +5.8 | 55 |
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) | 36% | 18% | +18 |
| MCP server (first-party) | 40% | 16% | +24 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 16% | 13% | +3 |
| Security | 100% | 99% | +1 |
| Arazzo workflows | 5% | 1% | +4 |
| Governance rules | 64% | 36% | +28 |
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 BigPanda 72.7
- 2 AI for Database 62.7
- 3 Mention 61.7
- 4 Socure 60.4
- 5 LVT 60.2
- 6 puzaricloud-in 56.6
- 7 WeatherAPI 55.8
- 8 Tomorrow.io 54.4
- 9 HackNotice 52.2
- 10 Codex Reset 50.1
- 1 BigPanda 54
- 2 puzaricloud-in 47.8
- 3 AlertCamp 43.5
- 4 CaseMagic 42.3
- 5 Boletín Claro 40
- 6 Estiaje 39.2
- 7 Firmenwatch 39.1
- 8 HostTracker 38.4
- 9 Tomorrow.io 37.4
- 10 alphayou-net 36.9
Coverage caveat. 34 of 55 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.