# Vendor facets — incident.io (status pages). Status pages built into an incident-management platform; on the
# Kin Score they touch one pointer check, status_page_present (6 pts), and earn it at full credit: both the
# statuspage.incident.io/<slug> path and custom domains return a real 404 for unknown paths, so the
# pointer-liveness probe can prove the page. The incident.io MCP server scores nothing for the provider.
vendor: incident-io
name: incident.io
website: https://incident.io
areas:
- status-page
registry_keys:
- incident-io
rubric_schema_version: 0.22.0
generated: '2026-09-25'
features_refreshed: '2026-09-25'
basis: capability
summary: >-
  incident.io status pages move one Kin Score check, status_page_present (6 of 38 operational-transparency
  points), once the provider declares the page as a StatusPage in apis.yml. The hosting clears the pointer-liveness
  probe: statuspage.incident.io/<slug> and custom domains such as status.openai.com return a real 404
  for nonsense paths, so the pointer grades live. Its Widget API, RSS subscriptions, maintenance windows
  and component uptime are good practice that no check reads, and its remote MCP server manages the provider's
  incident.io account rather than the provider's API.
features:
- id: hosted-status-page
  name: Public, customer and internal status pages
  description: >-
    Component-based status pages per audience with uptime history per component, maintenance windows,
    and email, Slack and RSS subscriptions.
  source: https://incident.io/status-pages
  tier: unknown
- id: soft-404-safe-hosting
  name: Real 404 for unknown paths (measured)
  description: >-
    Probed 2026-09-25: statuspage.incident.io/wispr-flow, status.incident.io and status.openai.com return
    200 for the page and 404 for a nonsense path.
  source: https://status.openai.com
  tier: all
- id: status-page-api
  name: Status Page API and public Widget API
  description: >-
    An authenticated API to create and update status incidents and maintenance, and an unauthenticated
    read-only Widget API returning ongoing incidents and maintenances for public and customer pages.
  source: https://docs.incident.io/status-pages/api
  tier: unknown
- id: remote-mcp
  name: incident.io remote MCP server (mcp.incident.io)
  description: >-
    Hosted MCP server over OAuth or API key for the provider's incident data, on-call and drafting status
    page updates; Team, Pro and Enterprise plans only.
  source: https://docs.incident.io/ai/remote-mcp
  tier: paid
maps:
- feature: hosted-status-page
  check: status_page_present
  layer: composite
  credit: 1.0
  provider_must: >-
    Declare the page (public, not internal) in apis.yml as common[].type StatusPage. The pointer is liveness-graded
    and incident.io hosting grades live.
  note: Binary check, cleared in full. The only check the status-page area touches.
  catalog_pass_rate: 0.125
  facet: operational_transparency
  points: 6
  baseline_pass_rate: 0.376
earns_nothing:
- feature: remote-mcp
  check: mcp_server
  why: >-
    It serves the provider's own team their incident.io data. The dimension reads an MCP server for the
    provider's API, described in the provider's mcp/ manifest; this is neither.
- feature: status-page-api
  check: event_surface_described
  why: A polled widget JSON is not an AsyncAPI document or webhooks in the provider's OpenAPI.
out_of_reach:
  checks:
  - change_log_present
  - deprecation_policy
  - roadmap_present
  - rate_limits_documented
  - webhooks_advertised
  note: >-
    Incident history is not a change log, and a status page publishes nothing about the API's limits,
    deprecations or its own webhooks.
unscored_practice:
- feature: status-page-api
  why: Unauthenticated machine-readable status an agent could poll; no check reads it.
- feature: hosted-status-page
  why: Per-component uptime history and maintenance windows; unscored.
surface:
  operational_transparency:
    reachable: 6.0
    total: 38
  agent_readiness:
    reachable: 0
    total: 139
hard_rule: >-
  A model, not a score. Adopting this vendor changes a provider's Kin Score only when the provider publishes
  the resulting artifacts on its own surface; nothing here writes a score, and no sponsorship or partnership
  can.
method: searched
source:
- https://docs.incident.io/ai/remote-mcp
- https://docs.incident.io/status-pages/api
- https://incident.io/status-pages
- https://status.openai.com
measured:
  cohort:
    method: vendors-catalog.json detections (CNAME / header / URL shape / markup), never a name match
    detected: 0
    in_baseline: 0
  control:
    basis: providers earning contract_present + documentation_present + api_reference_present, minus the
      cohort
    n: 5216
  metric: >-
    cohort_pct / control_pct = mean share of the check's points earned (derived and platform credit weighted),
    x100
  measured_on: '2026-09-25'
  status: 'not measurable: 0 detected customers clear the baseline (need 20)'
simulation:
  simulated_on: '2026-09-25'
  rubric: 0.23.0
  population: providers publishing a contract (contract_present earned), replayable exactly
  providers: 8977
  providers_unreplayable: 987
  providers_moved: 6390
  conditional_rows: excluded (they depend on what the API already does)
  composite_lift:
    median: 2.0
    p75: 2.1
    p90: 2.1
    max: 2.1
    mean_among_movers: 1.9
  agent_readiness_lift:
    median: 0.0
    p75: 0.0
    p90: 0.0
    max: 0.0
    mean_among_movers: 0.0
  facet_lift_median_among_movers:
    operational_transparency: 15.8
  composite_band_moves:
    thin -> developing: 598
    developing -> strong: 172
    emerging -> thin: 158
    strong -> exemplar: 43
    minimal -> emerging: 1
  agent_readiness_band_moves: {}
  method: >-
    each provider's own kin/checks file, the vendor's maps at their stated credit, the scorer's composite
    formula; from -> to, nothing written