Incident Response
Providers using this tag (66)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Strong 4 Solid coverage with minor gaps
Developing 17 Usable, with meaningful gaps to close
Thin 14 Limited public surface area
Emerging 22 Early or largely undocumented
Minimal 9 Almost no public developer surface
APIs with this tag (17)
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 2 Complete, well-documented, and agent-ready
Strong 2 Solid coverage with minor gaps
Developing 7 Usable, with meaningful gaps to close
Thin 4 Limited public surface area
Emerging 1 Early or largely undocumented
Minimal 1 Almost no public developer surface
Companies reaching this through an API (4)
These companies publish an API, specification or operation carrying “Incident Response” 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 63 providers in the APIs.io catalog tagged Incident Response, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Access Clarity | 36.5 | 26.5 | +10 | 63 |
| Developer Ergonomics | 32.9 | 23.2 | +9.7 | 63 |
| Discoverability | 64.4 | 58.1 | +6.3 | 63 |
| Operational Transparency | 19.9 | 13.7 | +6.2 | 63 |
| Contract Governance | 9.3 | 6.3 | +3 | 63 |
| Contract Quality | 18.5 | 17.6 | +0.9 | 63 |
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) | 27% | 14% | +13 |
| MCP server (first-party) | 27% | 12% | +15 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 16% | 11% | +5 |
| Security | 100% | 98% | +2 |
| Arazzo workflows | 0% | 2% | -2 |
| Governance rules | 13% | 14% | -1 |
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 Splunk Observability Cloud 65.7
- 2 Cisco XDR 65.6
- 3 IRONSCALES 56.9
- 4 AirMDR 55.1
- 5 Corelayer 50.4
- 6 LevelBlue 50
- 7 Cyware 49.2
- 8 IncidentFox (Brownie) 48.6
- 9 RunWhen 46.1
- 10 Coalition 45.9
- 1 IRONSCALES 49.5
- 2 AirMDR 45.8
- 3 RunWhen 42.6
- 4 Cisco XDR 38.5
- 5 Splunk Observability Cloud 32.4
- 6 Cyware 32.4
- 7 Spyderbat 30.5
- 8 Stairwell 30
- 9 Corelayer 29.3
- 10 Coalition 28.1
Coverage caveat. 53 of 63 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 5 October 2026, across 29093 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.