How incident.io’s scores are calculated

The full audit trail, recomputed from the verdict data at build time through the same code that produced the leaderboard: verdict × quality × story weight per cell, cells sum to dimension scores, dimensions blend into the PA Score. Every number on the product page is reproducible from this page alone; for why the formula looks like this, see the methodology.

verdict factors: full ×1.0 · partial ×0.6 · disputed ×0.3 · none ×0.0 · n/a excluded from both sides · cell points = weight × quality × factor · cell max = weight × 10

PA Score42/100

Agent-ready 49.2 × 0.30 = 14.76

API quality 40.3 × 0.20 = 8.06

Openness 28.8 × 0.20 = 5.76

Built-in AI 80.0 × 0.15 = 12.00

Automation 11.3 × 0.15 = 1.70

(14.76 + 8.06 + 5.76 + 12.00 + 1.70) ÷ (0.30 + 0.20 + 0.20 + 0.15 + 0.15) = 42.27 ÷ 1.00 = 42.3

Scores are stored to 1 decimal; the product page’s pills round to whole numbers for display. Each dimension below shows the stories, verdicts, and cited evidence behind its number.

Agent-ready49.2/100×0.30 of the PA blend

Outside-in: can YOUR agent reach and drive this product — API, MCP, CLI, headless runs, agent docs.

Point an agent at llms.txt or agent-oriented docsweight 2

2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max

[probe] https://docs.incident.io/llms.txt“PROBE llms.txt: HTTP 200 at https://docs.incident.io/llms.txt # incident.io - [Help center (452 pages)](https://docs.incident.io/_llms/help-center.md): Documentation for Help center”
[probe] https://docs.incident.io/api-reference/introduction“PROBE runtime (recorded 2026-09-06): incident.io publishes machine-readable per-tag OpenAPI 3.0.3 specs keylessly (e.g. https://docs.incident.io/openapi/tags/incidents-v2.json downloaded and parsed), alongside a docs llms.txt index listing 550+ API-reference pages as markdown.”

Run the product headlessly / in CI for automationweight 2

2 (weight) × 7 (quality) × 1.0 (full) = 14.0 of 20 max

[claimed-docs] https://docs.incident.io/api-reference/introduction“The API is hosted at `https://api.incident.io/`, and you will need an API key from your incident.io dashboard to make requests.”
[claimed-docs] https://docs.incident.io/api-reference/introduction“Download the full OpenAPI 3.0 spec to generate”
[claimed-docs] https://incident.io/changelog“We're working through our Terraform provider resource by resource to make your infra-as-code setup easier to understand and maintain.”
[claimed-docs] https://docs.incident.io/integrations/webhooks“Webhooks can be used to receive notifications when certain events occur in incident.io.”
[claimed-docs] https://docs.incident.io/integrations/webhooks“Webhooks can be used to receive notifications when certain events occur in incident.io. This might be useful for annotating graphs in a monitoring tool with incidents, keeping track of follow-ups, or syncing on-call data”
[probe] https://docs.incident.io/api-reference/introduction“PROBE runtime (recorded 2026-09-06): incident.io publishes machine-readable per-tag OpenAPI 3.0.3 specs keylessly (e.g. https://docs.incident.io/openapi/tags/incidents-v2.json downloaded and parsed), alongside a docs llms.txt index listing 550+ API-reference pages as markdown.”

Plug MCP servers into this product so it can use their toolsweight 3

3 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 30 max

[claimed-docs] https://docs.incident.io/ai/remote-mcp“The incident.io MCP server lets you connect any AI assistant that supports the Model Context Protocol directly to your incident data.”
[claimed-docs] https://docs.incident.io/ai/remote-mcp“The incident.io MCP server lets you connect any AI assistant that supports the Model Context Protocol directly to your incident data. Query incidents, analyze alerts, check who's on call, manage escalations, and run deep operational analysis”
[claimed-docs] https://docs.incident.io/ai/remote-mcp“Query incidents, analyze alerts, check who's on call, manage escalations, and run deep operational analysis — all from your existing AI tools.”
[claimed-docs] https://docs.incident.io/ai/remote-mcp“connect any AI assistant that supports the Model Context Protocol directly to your incident data”
[probe] https://docs.incident.io/ai/remote-mcp“official MCP server documented at https://docs.incident.io/ai/remote-mcp”
[probe] https://docs.incident.io/ai/remote-mcp“PROBE runtime (recorded 2026-09-06): incident.io's hosted remote MCP server is live — a keyless JSON-RPC initialize POST to https://mcp.incident.io/mcp returned HTTP 401 with WWW-Authenticate Bearer resource_metadata=https://mcp.incident.io/mcp/.well-known/oauth-protected-resource — the managed MCP endpoint speaks the MCP OAuth flow.”

Connect an agent via an official MCP serverweight 3

3 (weight) × 9 (quality) × 1.0 (full) = 27.0 of 30 max

[claimed-docs] https://docs.incident.io/ai/remote-mcp“The incident.io MCP server lets you connect any AI assistant that supports the Model Context Protocol directly to your incident data.”
[claimed-docs] https://docs.incident.io/ai/remote-mcp“The incident.io MCP server lets you connect any AI assistant that supports the Model Context Protocol directly to your incident data. Query incidents, analyze alerts, check who's on call, manage escalations, and run deep operational analysis”
[claimed-docs] https://docs.incident.io/ai/remote-mcp“Query incidents, analyze alerts, check who's on call, manage escalations, and run deep operational analysis — all from your existing AI tools.”
[claimed-docs] https://docs.incident.io/ai/remote-mcp“connect any AI assistant that supports the Model Context Protocol directly to your incident data”
[probe] https://docs.incident.io/ai/remote-mcp“official MCP server documented at https://docs.incident.io/ai/remote-mcp”
[probe] https://docs.incident.io/ai/remote-mcp“PROBE runtime (recorded 2026-09-06): incident.io's hosted remote MCP server is live — a keyless JSON-RPC initialize POST to https://mcp.incident.io/mcp returned HTTP 401 with WWW-Authenticate Bearer resource_metadata=https://mcp.incident.io/mcp/.well-known/oauth-protected-resource — the managed MCP endpoint speaks the MCP OAuth flow.”

Use an official CLIweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Drive the product through a documented public APIweight 3

3 (weight) × 8 (quality) × 1.0 (full) = 24.0 of 30 max

[claimed-docs] https://docs.incident.io/api-reference/introduction“The API is hosted at `https://api.incident.io/`, and you will need an API key from your incident.io dashboard to make requests.”
[claimed-docs] https://docs.incident.io/api-reference/introduction“Download the full OpenAPI 3.0 spec to generate”
[claimed-docs] https://docs.incident.io/api-reference/introduction“you will need an API key from your incident.io dashboard to make requests”
[probe] https://docs.incident.io/api-reference/introduction“PROBE runtime (recorded 2026-09-06): incident.io publishes machine-readable per-tag OpenAPI 3.0.3 specs keylessly (e.g. https://docs.incident.io/openapi/tags/incidents-v2.json downloaded and parsed), alongside a docs llms.txt index listing 550+ API-reference pages as markdown.”
[probe] https://docs.incident.io/llms.txt“PROBE llms.txt: HTTP 200 at https://docs.incident.io/llms.txt # incident.io - [Help center (452 pages)](https://docs.incident.io/_llms/help-center.md): Documentation for Help center”

Issue scoped/least-privilege API credentials for an agentweight 2

2 (weight) × 3 (quality) × 0.6 (partial) = 3.6 of 20 max

[probe] https://docs.incident.io/ai/remote-mcp“PROBE runtime (recorded 2026-09-06): incident.io's hosted remote MCP server is live — a keyless JSON-RPC initialize POST to https://mcp.incident.io/mcp returned HTTP 401 with WWW-Authenticate Bearer resource_metadata=https://mcp.incident.io/mcp/.well-known/oauth-protected-resource — the managed MCP endpoint speaks the MCP OAuth flow.”
[claimed-docs] https://docs.incident.io/api-reference/introduction“The API is hosted at `https://api.incident.io/`, and you will need an API key from your incident.io dashboard to make requests.”
[claimed-docs] https://docs.incident.io/api-reference/introduction“you will need an API key from your incident.io dashboard to make requests”
[claimed-docs] https://docs.incident.io/ai/remote-mcp“The incident.io MCP server lets you connect any AI assistant that supports the Model Context Protocol directly to your incident data.”

Build against official SDKsweight 2

2 (weight) × 4 (quality) × 0.6 (partial) = 4.8 of 20 max

[claimed-docs] https://docs.incident.io/api-reference/introduction“The API is hosted at `https://api.incident.io/`, and you will need an API key from your incident.io dashboard to make requests.”
[claimed-docs] https://docs.incident.io/api-reference/introduction“Download the full OpenAPI 3.0 spec to generate”
[claimed-docs] https://docs.incident.io/api-reference/introduction“you will need an API key from your incident.io dashboard to make requests”
[probe] https://docs.incident.io/api-reference/introduction“PROBE runtime (recorded 2026-09-06): incident.io publishes machine-readable per-tag OpenAPI 3.0.3 specs keylessly (e.g. https://docs.incident.io/openapi/tags/incidents-v2.json downloaded and parsed), alongside a docs llms.txt index listing 550+ API-reference pages as markdown.”

Subscribe to events via webhooksweight 2

2 (weight) × 7 (quality) × 1.0 (full) = 14.0 of 20 max

[claimed-docs] https://docs.incident.io/integrations/webhooks“Webhooks can be used to receive notifications when certain events occur in incident.io.”
[claimed-docs] https://docs.incident.io/integrations/webhooks“Webhooks can be used to receive notifications when certain events occur in incident.io. This might be useful for annotating graphs in a monitoring tool with incidents, keeping track of follow-ups, or syncing on-call data”
[claimed-docs] https://docs.incident.io/integrations/webhooks“Webhooks can be used to receive notifications when certain events occur in incident.io... syncing on-call data like alerts, escalations, and schedule changes to external tools.”

Agent-ready = 103.4 ÷ 210 × 100 = 49.2

API quality40.3/100×0.20 of the PA blend

The programmable surface once an agent is there — machine-readable spec, interactive docs, sandbox, versioning discipline.

Explore an interactive API reference with runnable examplesweight 2

2 (weight) × 4 (quality) × 0.6 (partial) = 4.8 of 20 max

[claimed-docs] https://docs.incident.io/api-reference/introduction“The API is hosted at `https://api.incident.io/`, and you will need an API key from your incident.io dashboard to make requests.”
[claimed-docs] https://docs.incident.io/api-reference/introduction“Download the full OpenAPI 3.0 spec to generate”
[probe] https://docs.incident.io/api-reference/introduction“PROBE runtime (recorded 2026-09-06): incident.io publishes machine-readable per-tag OpenAPI 3.0.3 specs keylessly (e.g. https://docs.incident.io/openapi/tags/incidents-v2.json downloaded and parsed), alongside a docs llms.txt index listing 550+ API-reference pages as markdown.”
[probe] https://docs.incident.io/openapi.json“PROBE openapi: all candidate paths 404 (https://docs.incident.io/openapi.json, https://docs.incident.io/swagger.json, https://docs.incident.io/api/openapi.json, https://docs.incident.io/.well-known/openapi.json)”

Download a machine-readable API spec (OpenAPI or equivalent)weight 2

2 (weight) × 9 (quality) × 1.0 (full) = 18.0 of 20 max

[claimed-docs] https://docs.incident.io/api-reference/introduction“The API is hosted at `https://api.incident.io/`, and you will need an API key from your incident.io dashboard to make requests.”
[claimed-docs] https://docs.incident.io/api-reference/introduction“Download the full OpenAPI 3.0 spec to generate”
[claimed-docs] https://docs.incident.io/api-reference/introduction“you will need an API key from your incident.io dashboard to make requests”
[probe] https://docs.incident.io/api-reference/introduction“PROBE runtime (recorded 2026-09-06): incident.io publishes machine-readable per-tag OpenAPI 3.0.3 specs keylessly (e.g. https://docs.incident.io/openapi/tags/incidents-v2.json downloaded and parsed), alongside a docs llms.txt index listing 550+ API-reference pages as markdown.”

Test against a sandbox environment without touching production dataweight 1

1 (weight) × 3 (quality) × 0.6 (partial) = 1.8 of 10 max

[claimed-docs] https://docs.incident.io/incidents/declaring“a **test** incident to practice without affecting production”
[claimed-docs] https://docs.incident.io/ai/remote-mcp“The incident.io MCP server lets you connect any AI assistant that supports the Model Context Protocol directly to your incident data.”
[probe] https://docs.incident.io/ai/remote-mcp“official MCP server documented at https://docs.incident.io/ai/remote-mcp”

Rely on versioned APIs with a documented deprecation policyweight 2

2 (weight) × 3 (quality) × 0.6 (partial) = 3.6 of 20 max

[claimed-docs] https://docs.incident.io/api-reference/introduction“The API is hosted at `https://api.incident.io/`, and you will need an API key from your incident.io dashboard to make requests.”
[claimed-docs] https://docs.incident.io/api-reference/introduction“Download the full OpenAPI 3.0 spec to generate”
[probe] https://docs.incident.io/api-reference/introduction“PROBE runtime (recorded 2026-09-06): incident.io publishes machine-readable per-tag OpenAPI 3.0.3 specs keylessly (e.g. https://docs.incident.io/openapi/tags/incidents-v2.json downloaded and parsed), alongside a docs llms.txt index listing 550+ API-reference pages as markdown.”
[probe] https://docs.incident.io/openapi.json“PROBE openapi: all candidate paths 404 (https://docs.incident.io/openapi.json, https://docs.incident.io/swagger.json, https://docs.incident.io/api/openapi.json, https://docs.incident.io/.well-known/openapi.json)”

API quality = 28.2 ÷ 70 × 100 = 40.3

Openness28.8/100×0.20 of the PA blend

Can you leave, inspect, or self-host — data export, open source, portability.

Do everything through the API that I can do in the UIweight 2

2 (weight) × 6 (quality) × 0.6 (partial) = 7.2 of 20 max

[claimed-docs] https://docs.incident.io/api-reference/introduction“The API is hosted at `https://api.incident.io/`, and you will need an API key from your incident.io dashboard to make requests.”
[claimed-docs] https://docs.incident.io/api-reference/introduction“Download the full OpenAPI 3.0 spec to generate”
[probe] https://docs.incident.io/api-reference/introduction“PROBE runtime (recorded 2026-09-06): incident.io publishes machine-readable per-tag OpenAPI 3.0.3 specs keylessly (e.g. https://docs.incident.io/openapi/tags/incidents-v2.json downloaded and parsed), alongside a docs llms.txt index listing 550+ API-reference pages as markdown.”
[claimed-docs] https://docs.incident.io/status-pages/api“Automate status page incidents, maintenance windows, and embed status data in your product.”
[claimed-docs] https://docs.incident.io/integrations/webhooks“Webhooks can be used to receive notifications when certain events occur in incident.io.”
[claimed-docs] https://docs.incident.io/ai/remote-mcp“Query incidents, analyze alerts, check who's on call, manage escalations, and run deep operational analysis — all from your existing AI tools.”
[probe] https://docs.incident.io/ai/remote-mcp“official MCP server documented at https://docs.incident.io/ai/remote-mcp”

Export all of my data in open formats and leaveweight 3

3 (weight) × 4 (quality) × 0.6 (partial) = 7.2 of 30 max

[claimed-docs] https://docs.incident.io/api-reference/introduction“The API is hosted at `https://api.incident.io/`, and you will need an API key from your incident.io dashboard to make requests.”
[claimed-docs] https://docs.incident.io/api-reference/introduction“Download the full OpenAPI 3.0 spec to generate”
[claimed-docs] https://docs.incident.io/api-reference/introduction“you will need an API key from your incident.io dashboard to make requests”
[probe] https://docs.incident.io/api-reference/introduction“PROBE runtime (recorded 2026-09-06): incident.io publishes machine-readable per-tag OpenAPI 3.0.3 specs keylessly (e.g. https://docs.incident.io/openapi/tags/incidents-v2.json downloaded and parsed), alongside a docs llms.txt index listing 550+ API-reference pages as markdown.”
[claimed-docs] https://docs.incident.io/integrations/webhooks“Webhooks can be used to receive notifications when certain events occur in incident.io.”
[claimed-docs] https://docs.incident.io/integrations/webhooks“Webhooks can be used to receive notifications when certain events occur in incident.io... syncing on-call data like alerts, escalations, and schedule changes to external tools.”

Read the product's source under an open licenseweight 2

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Self-host the core productweight 3

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Openness = 14.4 ÷ 50 × 100 = 28.8

Built-in AI80.0/100×0.15 of the PA blend

Inside-out: how agentic the product itself is for its users — built-in assistants, autonomous features.

Get AI-generated insights and suggestions from my data inside the productweight 2

2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max

[claimed-docs] https://docs.incident.io/investigations/overview“Investigations automatically work out what's going on during an incident, doing the legwork a responder normally would, faster and across every source at once.”
[claimed-docs] https://docs.incident.io/investigations/how-investigations-work“An investigation isn't a single prompt to a model. It's a structured process that gathers evidence, forms a hypothesis, then tests that hypothesis against your code and telemetry.”
[claimed-docs] https://incident.io/investigations“Investigations runs on a purpose-built harness that re-assesses as new signals land, builds findings from real evidence, and pressure-tests every hypothesis with an adversarial agent before it reaches you.”
[claimed-docs] https://docs.incident.io/investigations/overview“The moment an incident is declared, an investigation gathers context from across your stack: the alert and its stack trace, similar past incidents, incident channel discussion and change events, your runbooks, recent code changes, and your telemetry.”
[claimed-docs] https://docs.incident.io/investigations/overview“Investigations automatically work out what’s going on during an incident, doing the legwork a responder normally would, faster and across every source at once.”
[claimed-docs] https://docs.incident.io/investigations/overview“Find the root cause of incidents faster, with evidence you can trust.”
[claimed-docs] https://incident.io/investigations“Investigations tackles the hardest part of the incident and gets you from alert to resolution an order of magnitude faster.”
[claimed-docs] https://docs.incident.io/ai/suggestions“Suggestions uses AI to help teams communicate better during incidents by automatically drafting updates, summaries and follow-up actions based on your incident activity.”
[claimed-docs] https://docs.incident.io/ai/summaries“responders don’t always have time to digest lots of information or communicate externally what’s going on... This is where suggested summaries comes in.”
[claimed-docs] https://docs.incident.io/ai/suggestions“Suggestions uses AI to help teams communicate better during incidents by automatically drafting updates, summaries and follow-up actions”
[claimed-docs] https://docs.incident.io/insights/overview“You can also compare with the previous period by toggling it on.”
[claimed-docs] https://docs.incident.io/insights/overview“you can choose to include data from the current Week/Month/Quarter... You can also compare with the previous period by toggling it on.”

Set up automations that run autonomously in the backgroundweight 2

2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max

[claimed-docs] https://docs.incident.io/investigations/overview“Investigations automatically work out what's going on during an incident, doing the legwork a responder normally would, faster and across every source at once.”
[claimed-docs] https://docs.incident.io/investigations/how-investigations-work“An investigation isn't a single prompt to a model. It's a structured process that gathers evidence, forms a hypothesis, then tests that hypothesis against your code and telemetry.”
[claimed-docs] https://docs.incident.io/investigations/trust-and-safety“Letting an AI agent work on a live production incident only pays off if you can trust it: to stay within the bounds you set, to show its working, and to be honest about what it does and doesn't know.”
[claimed-docs] https://incident.io/investigations“Investigations runs on a purpose-built harness that re-assesses as new signals land, builds findings from real evidence, and pressure-tests every hypothesis with an adversarial agent before it reaches you.”
[claimed-docs] https://docs.incident.io/investigations/overview“The moment an incident is declared, an investigation gathers context from across your stack: the alert and its stack trace, similar past incidents, incident channel discussion and change events, your runbooks, recent code changes, and your telemetry.”
[claimed-docs] https://docs.incident.io/status-pages/auto-publishing“With Workflows, you can automatically publish to your status page when an incident is updated.”
[claimed-docs] https://docs.incident.io/investigations/trust-and-safety“How investigations stay under your control, keep a full record of their work, and stay honest about what they know.”

Delegate tasks to a built-in AI assistant inside the productweight 3

3 (weight) × 8 (quality) × 1.0 (full) = 24.0 of 30 max

[claimed-docs] https://docs.incident.io/investigations/overview“Investigations automatically work out what's going on during an incident, doing the legwork a responder normally would, faster and across every source at once.”
[claimed-docs] https://docs.incident.io/investigations/how-investigations-work“An investigation isn't a single prompt to a model. It's a structured process that gathers evidence, forms a hypothesis, then tests that hypothesis against your code and telemetry.”
[claimed-docs] https://incident.io/investigations“Investigations runs on a purpose-built harness that re-assesses as new signals land, builds findings from real evidence, and pressure-tests every hypothesis with an adversarial agent before it reaches you.”
[claimed-docs] https://docs.incident.io/investigations/overview“The moment an incident is declared, an investigation gathers context from across your stack: the alert and its stack trace, similar past incidents, incident channel discussion and change events, your runbooks, recent code changes, and your telemetry.”
[claimed-docs] https://docs.incident.io/post-incident/postmortem-ai“Generate first drafts, get inline review suggestions, and redraft sections with AI.”
[claimed-docs] https://docs.incident.io/ai/suggestions“Suggestions uses AI to help teams communicate better during incidents by automatically drafting updates, summaries and follow-up actions based on your incident activity.”
[claimed-docs] https://docs.incident.io/ai/suggestions“Suggestions uses AI to help teams communicate better during incidents by automatically drafting updates, summaries and follow-up actions”

Operate the product with natural-language commandsweight 2

2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max

[claimed-docs] https://docs.incident.io/ai/remote-mcp“The incident.io MCP server lets you connect any AI assistant that supports the Model Context Protocol directly to your incident data.”
[claimed-docs] https://docs.incident.io/ai/remote-mcp“The incident.io MCP server lets you connect any AI assistant that supports the Model Context Protocol directly to your incident data. Query incidents, analyze alerts, check who's on call, manage escalations, and run deep operational analysis”
[claimed-docs] https://docs.incident.io/ai/remote-mcp“Query incidents, analyze alerts, check who's on call, manage escalations, and run deep operational analysis — all from your existing AI tools.”
[claimed-docs] https://docs.incident.io/ai/remote-mcp“connect any AI assistant that supports the Model Context Protocol directly to your incident data”
[claimed-docs] https://incident.io/changelog“You can now update your status page using the agent, add Pingdom”
[probe] https://docs.incident.io/ai/remote-mcp“official MCP server documented at https://docs.incident.io/ai/remote-mcp”
[probe] https://docs.incident.io/ai/remote-mcp“PROBE runtime (recorded 2026-09-06): incident.io's hosted remote MCP server is live — a keyless JSON-RPC initialize POST to https://mcp.incident.io/mcp returned HTTP 401 with WWW-Authenticate Bearer resource_metadata=https://mcp.incident.io/mcp/.well-known/oauth-protected-resource — the managed MCP endpoint speaks the MCP OAuth flow.”

Built-in AI = 72.0 ÷ 90 × 100 = 80.0

Automation11.3/100×0.15 of the PA blend

Depth of automation primitives — rules, scheduling, bulk operations, webhooks.

Perform bulk operations across many items at onceweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

[claimed-docs] https://docs.incident.io/api-reference/introduction“The API is hosted at `https://api.incident.io/`, and you will need an API key from your incident.io dashboard to make requests.”
[claimed-docs] https://docs.incident.io/ai/remote-mcp“The incident.io MCP server lets you connect any AI assistant that supports the Model Context Protocol directly to your incident data. Query incidents, analyze alerts, check who's on call, manage escalations, and run deep operational analysis”
[claimed-docs] https://docs.incident.io/ai/remote-mcp“Query incidents, analyze alerts, check who's on call, manage escalations, and run deep operational analysis — all from your existing AI tools.”
[probe] https://docs.incident.io/api-reference/introduction“PROBE runtime (recorded 2026-09-06): incident.io publishes machine-readable per-tag OpenAPI 3.0.3 specs keylessly (e.g. https://docs.incident.io/openapi/tags/incidents-v2.json downloaded and parsed), alongside a docs llms.txt index listing 550+ API-reference pages as markdown.”
[claimed-docs] https://docs.incident.io/alerts/grouping-alerts“Group related alerts into an alert group so you can triage, escalate and attach them to incidents as one.”

Define rules that trigger actions automatically on eventsweight 3

3 (weight) × 5 (quality) × 0.6 (partial) = 9.0 of 30 max

[claimed-docs] https://docs.incident.io/status-pages/auto-publishing“With Workflows, you can automatically publish to your status page when an incident is updated.”
[claimed-docs] https://docs.incident.io/on-call/escalation-paths“You can now set up rules around priority and/or working hours to ensure you page the right people at the right time without causing additional noise.”
[claimed-docs] https://docs.incident.io/on-call/escalation-paths“You can now set up rules around priority and/or working hours to ensure you page the right people at the right time”
[claimed-docs] https://docs.incident.io/alerts/deduplication“if alert A is received with a deduplication key "x" and alert B with the same deduplication key is received while alert A is still active... no new alert will be created for alert B”
[claimed-docs] https://docs.incident.io/alerts/grouping-alerts“Alert grouping groups those related alerts into a single alert group, so you can triage, escalate and attach them to an incident once”
[claimed-docs] https://docs.incident.io/integrations/webhooks“Webhooks can be used to receive notifications when certain events occur in incident.io.”
[claimed-docs] https://docs.incident.io/integrations/webhooks“Webhooks can be used to receive notifications when certain events occur in incident.io... syncing on-call data like alerts, escalations, and schedule changes to external tools.”

Schedule recurring jobs or workflowsweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

[claimed-docs] https://docs.incident.io/status-pages/auto-publishing“With Workflows, you can automatically publish to your status page when an incident is updated.”
[claimed-docs] https://docs.incident.io/on-call/building-schedules“Name your new schedule, set up rotation, and choose the people who should be in that specific s”
[claimed-docs] https://docs.incident.io/on-call/building-schedules“Leverage schedules to tell us who should be on-call and when.”

Version, review, and roll back my automationsweight 1

1 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 10 max

[claimed-docs] https://incident.io/changelog“We're working through our Terraform provider resource by resource to make your infra-as-code setup easier to understand and maintain.”

Automation = 9.0 ÷ 80 × 100 = 11.3