Alerts
Alertsalerts
Providers using this tag (211)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 9 Complete, well-documented, and agent-ready
Strong 34 Solid coverage with minor gaps
Developing 82 Usable, with meaningful gaps to close
Thin 54 Limited public surface area
Emerging 31 Early or largely undocumented
Minimal 1 Almost no public developer surface
APIs with this tag (297)
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 10 Complete, well-documented, and agent-ready
Strong 118 Solid coverage with minor gaps
Developing 83 Usable, with meaningful gaps to close
Thin 57 Limited public surface area
Emerging 28 Early or largely undocumented
Minimal 1 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 211 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 | 49.8 | 17.5 | +32.3 | 211 |
| Developer Ergonomics | 40.7 | 17.9 | +22.8 | 211 |
| Operational Transparency | 28.6 | 11.3 | +17.3 | 211 |
| Access Clarity | 39.4 | 22.3 | +17.1 | 211 |
| Discoverability | 71.8 | 60.4 | +11.4 | 211 |
| Contract Governance | 15.7 | 6.4 | +9.3 | 211 |
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) | 38% | 16% | +22 |
| MCP server (first-party) | 16% | 7% | +9 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 21% | 9% | +12 |
| Security | 99% | 88% | +11 |
| Arazzo workflows | 18% | 2% | +16 |
| Governance rules | 45% | 13% | +32 |
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 SendGrid 77
- 2 MoEngage 75.8
- 3 Twilio 73.4
- 4 ThousandEyes 70.2
- 5 New Relic 68.8
- 6 Matomo 67.3
- 7 Dow Jones 66.8
- 8 Highlight (highlight.io) 66.7
- 9 Tomorrow.io 66.6
- 10 Cordial 64.8
- 1 DoiT 74.4
- 2 Cordial 62.9
- 3 Automattic 62.3
- 4 MoEngage 59.4
- 5 Upsun 56.7
- 6 Conviva 53.6
- 7 Jira 52.9
- 8 Red Hat 52.3
- 9 ThousandEyes 51.1
- 10 Socket 48.6
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/alerts"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/alerts"
curl "https://apis.io/api/v1/cohorts/tag/alerts/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.