slug: incident-io provider: Incident.io generated_by: planning/capability-mapping/scripts/classify_capabilities.py model: claude-opus-5 frame: - Software & Technology min_confidence: 0.7 capability_model: source: https://github.com/vincentmakes/turbo-ea-capabilities license: CC-BY-4.0 attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 notice: NOTICE edge_count: 13 edges: - tag: Incidents spec_file: incident-io-incidents-api-openapi.yml capability_id: BC-4220.30 capability_id_l1: BC-4220 capability_name: Incident Response Management confidence: 0.95 evidence: POST /incidents createIncident Create incident; vendor "helps teams declare, manage, and learn from incidents" reason: Core incident declaration and management surface of an incident response platform. - tag: Postmortem Documents spec_file: incident-io-postmortem-documents-api-openapi.yml capability_id: BC-4220.40 capability_id_l1: BC-4220 capability_name: Postmortem & Reliability Improvement confidence: 0.93 evidence: GET /postmortem-documents listPostmortemDocuments List postmortem documents reason: Direct management of postmortem authoring artefacts after production incidents. - tag: Alerts spec_file: incident-io-alerts-api-openapi.yml capability_id: BC-4220.30 capability_id_l1: BC-4220 capability_name: Incident Response Management confidence: 0.85 evidence: POST /alert-events createAlertEvent Create an alert event; GET /alerts listAlerts List alerts reason: Ingestion and listing of production alerts on an incident management platform — incident detection and on-call response. Not financial-crime or clinical alerting. - tag: Escalations spec_file: incident-io-escalations-api-openapi.yml capability_id: BC-4220.30 capability_id_l1: BC-4220 capability_name: Incident Response Management confidence: 0.82 evidence: POST /escalations createEscalation Create escalation; platform provides access to "escalations, on-call schedules" reason: Escalations in incident.io page on-call responders for production incidents, which is on-call/incident response coordination rather than any financial or HR escalation. - tag: Alert Routes spec_file: incident-io-alert-routes-api-openapi.yml capability_id: BC-4220.30 capability_id_l1: BC-4220 capability_name: Incident Response Management confidence: 0.8 evidence: POST /alert-routes createAlertRoute Create alert route reason: Alert routing rules determine how production alerts reach on-call responders and trigger escalation — core incident detection and response configuration on this incident management platform. - tag: Escalation Paths spec_file: incident-io-escalation-paths-api-openapi.yml capability_id: BC-4220.30 capability_id_l1: BC-4220 capability_name: Incident Response Management confidence: 0.8 evidence: POST /escalation-paths createEscalationPath Create escalation path reason: Escalation paths define on-call escalation for production incidents, explicitly listed in the API description alongside "escalations, on-call schedules" — incident response management. - tag: Incident Roles spec_file: incident-io-incident-roles-api-openapi.yml capability_id: BC-4220.30 capability_id_l1: BC-4220 capability_name: Incident Response Management confidence: 0.8 evidence: POST /incident-roles createIncidentRole Create incident role reason: Defines the responder roles used when coordinating production incidents — configuration in service of incident response management. - tag: Schedules spec_file: incident-io-schedules-api-openapi.yml capability_id: BC-4220.30 capability_id_l1: BC-4220 capability_name: Incident Response Management confidence: 0.8 evidence: POST /schedules createSchedule Create schedule; description lists "on-call schedules" reason: Schedules here are on-call rotations (not staff shift scheduling for HR), supporting on-call incident response. - tag: Severities spec_file: incident-io-severities-api-openapi.yml capability_id: BC-4220.30 capability_id_l1: BC-4220 capability_name: Incident Response Management confidence: 0.78 evidence: POST /severities createSeverity Create severity reason: Severity levels used to triage and prioritise production incidents on an incident management platform. - tag: Alert Sources spec_file: incident-io-alert-sources-api-openapi.yml capability_id: BC-4220.30 capability_id_l1: BC-4220 capability_name: Incident Response Management confidence: 0.75 evidence: POST /alert-sources createAlertSource Create alert source reason: Registration of monitoring/alerting integrations that feed incident detection. Sits between observability ingestion and incident response; chose incident response given the platform's stated purpose of declaring and managing incidents. - tag: Incident Statuses spec_file: incident-io-incident-statuses-api-openapi.yml capability_id: BC-4220.30 capability_id_l1: BC-4220 capability_name: Incident Response Management confidence: 0.75 evidence: POST /incident-statuses createIncidentStatus Create incident status reason: Configures the incident lifecycle statuses used in incident coordination; supports incident response rather than a separate business capability. - tag: Incident Types spec_file: incident-io-incident-types-api-openapi.yml capability_id: BC-4220.30 capability_id_l1: BC-4220 capability_name: Incident Response Management confidence: 0.75 evidence: GET /incident-types listIncidentTypes List incident types reason: Taxonomy of incident types used by the incident management platform, part of production incident response. - tag: Alert Attributes spec_file: incident-io-alert-attributes-api-openapi.yml capability_id: BC-4220.30 capability_id_l1: BC-4220 capability_name: Incident Response Management confidence: 0.7 evidence: POST /alert-attributes createAlertAttribute Create alert attribute reason: 'Configuration of attribute schema for production alerts on an incident management platform — supports incident detection/on-call response. Homograph check: these are monitoring alerts, not financial-crime alerts. Partly configuration metadata, hence moderate confidence.'