Incident Response
Providers using this tag (62)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Strong 3 Solid coverage with minor gaps
Developing 14 Usable, with meaningful gaps to close
Thin 19 Limited public surface area
Emerging 18 Early or largely undocumented
Minimal 7 Almost no public developer surface
Unrated 1 Not yet scored
APIs with this tag (16)
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 1 Complete, well-documented, and agent-ready
Strong 1 Solid coverage with minor gaps
Developing 6 Usable, with meaningful gaps to close
Thin 6 Limited public surface area
Emerging 1 Early or largely undocumented
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 59 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 | 37 | 26.5 | +10.5 | 59 |
| Developer Ergonomics | 33.5 | 23.4 | +10.1 | 59 |
| Operational Transparency | 21 | 14 | +7 | 59 |
| Discoverability | 66.8 | 61 | +5.8 | 59 |
| Contract Governance | 9.9 | 6.5 | +3.4 | 59 |
| Contract Quality | 22 | 20.1 | +1.9 | 59 |
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% | 10% | +17 |
| MCP server (first-party) | 27% | 13% | +14 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 17% | 11% | +6 |
| Security | 100% | 96% | +4 |
| Arazzo workflows | 0% | 2% | -2 |
| Governance rules | 13% | 13% | 0 |
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 Cisco XDR 61.4
- 2 Splunk Observability Cloud 61
- 3 IRONSCALES 55.5
- 4 Coalition 50.2
- 5 Corelayer 49.4
- 6 LevelBlue 48
- 7 Cyware 47.1
- 8 IncidentFox (Brownie) 47
- 9 Tracebit 45.2
- 10 RunWhen 45.1
- 1 IRONSCALES 51.6
- 2 RunWhen 42.6
- 3 Cisco XDR 38.5
- 4 Splunk Observability Cloud 34.6
- 5 Cyware 34.6
- 6 Spyderbat 32.4
- 7 Stairwell 32.2
- 8 Corelayer 29.3
- 9 LevelBlue 28.6
- 10 Coalition 28.1
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.