Can AI agents automate incident.io?

incident.io is automatable today through a public REST API. The API is hosted at https://api.incident.io/ and authenticates with an API key as Authorization Bearer. OpenAPI 3.0 is published. Default rate limit is 1,200 requests per minute per key, with lower limits on some list and catalog endpoints. Breaking changes move to a new path and integrators are asked to upgrade within three months. First-party remote MCP is at https://mcp.incident.io/mcp. An organisation admin enables it from Settings → MCP. Interactive clients use OAuth; agents and CI use a Bearer API key. Tools cover incidents, alerts, on-call, investigations, and analysis. Some tools need Response, On-call, or Investigations. status_page_update only drafts. The official CLI (`inc`) supports JSON output, `inc auth login`, and INCIDENT_API_KEY. Browser CLI login uses the same Settings → MCP organisation setting. Webhooks are powered by Svix. This record excludes PagerDuty and Rootly. Official language SDKs and connector catalogs were not established from the opened pages. Computer-use viability is unassessed. API scores 8 and is the best path.

Best path today: api · Overall automatability: 8/10