Incident.io website screenshot

Incident.io

incident.io is an incident management platform that helps teams declare, manage, and learn from incidents.

Incident.io publishes 25 APIs on the APIs.io network, including Actions API, Alert Attributes API, Alert Routes API, and 22 more. Tagged areas include AIOps, Incident Management, and Monitoring.

The Incident.io catalog on APIs.io includes 1 Spectral governance ruleset.

Incident.io’s developer surface includes authentication, documentation, engineering blog, and 9 more developer resources.

🌐 Visit website 📡 Source on GitHub
28.1/100 thin ▬ flat Agent 32/100 agent ready Front door AI 4/6 moderate Full breakdown ↓
scored 2026-09-25 · rubric v0.23.0
AccessPaid
25 APIs 16 Features
AIOpsIncident ManagementMonitoring

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-25 · rubric v0.23.0
Composite quality — 28.1/100 · thin
Contract Quality 9.1 / 19
Developer Ergonomics 2.1 / 15
Access Clarity 3.6 / 15
Operational Transparency 1.0 / 10
Contract Governance 0.9 / 9
Discoverability 4.1 / 8
Regulatory Posture 3.4 / 15
Create-or-Update Ergonomics 0.0 / 10
Agent readiness — 32/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 10 / 10
Documented Reversibility 0 / 6
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Delegated User Identity 0 / 6
Protected Resource Metadata 5 / 5
Registration Without a Human 0 / 6
Agentic Commerce Well-Known Document 0 / 5
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/incident-io: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

What adopting incident.io moves on the Kin Score 1

incident.io is an area vendor: providers adopt it to run part of their developer surface. This is the Kin Score checks its features can move for a provider that adopts it, what each one really earns, and what it earns nothing for.

status pagecapability map4 features checked 2026-09-25 · rubric v0.22.0

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/ 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.

Operational Transparency6.0 of 38 pts
CheckEarnsThrough
Status page
Operational TransparencyBinary check, cleared in full. The only check the status-page area touches.		 6.0 of 6 Public, customer and internal status pages
Across 8977 providers that publish a contract, adopting incident.io would move 6390. Median lift: composite +2.0 (90th percentile +2.1), agent readiness +0.0 (+0.0). Conditional rows excluded.
What incident.io ships that earns nothing (2)
  • incident.io remote MCP server (mcp.incident.io) — 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.
  • Status Page API and public Widget API — A polled widget JSON is not an AsyncAPI document or webhooks in the provider’s OpenAPI.

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. The rating is not for sale → · Full vendor facets artifact

APIs 25

Individual APIs this provider publishes, each with its own machine-readable definition.

Incident.io Actions API

The Actions API from Incident.io — 2 operation(s) for actions.

Incident.io Alert Attributes API

The Alert Attributes API from Incident.io — 2 operation(s) for alert attributes.

Incident.io Alert Routes API

The Alert Routes API from Incident.io — 2 operation(s) for alert routes.

Incident.io Alert Sources API

The Alert Sources API from Incident.io — 2 operation(s) for alert sources.

Incident.io Alerts API

The Alerts API from Incident.io — 3 operation(s) for alerts.

Incident.io API Keys API

The API Keys API from Incident.io — 3 operation(s) for api keys.

Incident.io Catalog Entries API

The Catalog Entries API from Incident.io — 2 operation(s) for catalog entries.

Incident.io Catalog Types API

The Catalog Types API from Incident.io — 2 operation(s) for catalog types.

Incident.io Custom Fields API

The Custom Fields API from Incident.io — 2 operation(s) for custom fields.

Incident.io Escalation Paths API

The Escalation Paths API from Incident.io — 2 operation(s) for escalation paths.

Incident.io Escalations API

The Escalations API from Incident.io — 2 operation(s) for escalations.

Incident.io Follow-ups API

The Follow-ups API from Incident.io — 2 operation(s) for follow-ups.

Incident.io Incident Roles API

The Incident Roles API from Incident.io — 2 operation(s) for incident roles.

Incident.io Incident Statuses API

The Incident Statuses API from Incident.io — 2 operation(s) for incident statuses.

Incident.io Incident Types API

The Incident Types API from Incident.io — 2 operation(s) for incident types.

Incident.io Incidents API

The Incidents API from Incident.io — 2 operation(s) for incidents.

Incident.io Maintenance Windows API

The Maintenance Windows API from Incident.io — 2 operation(s) for maintenance windows.

Incident.io Postmortem Documents API

The Postmortem Documents API from Incident.io — 2 operation(s) for postmortem documents.

Incident.io Schedules API

The Schedules API from Incident.io — 2 operation(s) for schedules.

Incident.io Severities API

The Severities API from Incident.io — 2 operation(s) for severities.

Incident.io Status Pages API

The Status Pages API from Incident.io — 2 operation(s) for status pages.

Incident.io Teams API

The Teams API from Incident.io — 2 operation(s) for teams.

Incident.io Users API

The Users API from Incident.io — 2 operation(s) for users.

Incident.io Utilities API

The Utilities API from Incident.io — 3 operation(s) for utilities.

Incident.io Workflows API

The Workflows API from Incident.io — 2 operation(s) for workflows.

Scroll for all 25

Open Collections 27

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Incident.io Actions API

OPEN COLLECTION

Incident.io Actions Alert Attributes API

OPEN COLLECTION

Incident.io Actions Alert Routes API

OPEN COLLECTION

Incident.io Actions Alert Sources API

OPEN COLLECTION

Incident.io Actions Alerts API

OPEN COLLECTION

Incident.io Actions API Keys API

OPEN COLLECTION

Incident.io Actions Catalog Entries API

OPEN COLLECTION

Incident.io Actions Catalog Types API

OPEN COLLECTION

Incident.io Actions Custom Fields API

OPEN COLLECTION

Incident.io Actions Escalation Paths API

OPEN COLLECTION

Incident.io Actions Escalations API

OPEN COLLECTION

Incident.io Actions Follow-ups API

OPEN COLLECTION

Incident.io Actions Incident Roles API

OPEN COLLECTION

Incident.io Actions Incident Statuses API

OPEN COLLECTION

Incident.io Actions Incident Types API

OPEN COLLECTION

Incident.io Actions Incidents API

OPEN COLLECTION

Incident.io Actions Maintenance Windows API

OPEN COLLECTION

Incident.io Actions Postmortem Documents API

OPEN COLLECTION

Incident.io Actions Schedules API

OPEN COLLECTION

Incident.io Actions Severities API

OPEN COLLECTION

Incident.io Actions Status Pages API

OPEN COLLECTION

Incident.io Actions Teams API

OPEN COLLECTION

Incident.io Actions Users API

OPEN COLLECTION

Incident.io Actions Utilities API

OPEN COLLECTION

Incident.io Actions Workflows API

OPEN COLLECTION

Incident.io API

OPEN COLLECTION

Scroll for all 27

Pricing Plans 1

Published pricing tiers and plan structures.

Incident Io Plans Pricing

5 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Incident Io Rate Limits

3 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Incident Io Finops

FINOPS

Features 16

Notable capabilities this provider offers.

Basic: free Slack/MS Teams native incident response
Team: $15/user/mo annual + $10/user for on-call
Pro: $25/user/mo + $20/user for on-call; AI Scribe, SSO/SAML
Enterprise: custom; Slack Enterprise Grid, Sandbox, CSM
On-Call only: $20/user/mo standalone alerting
Slack-native and MS Teams-native flow
AI suggestions for incident triage
AI Scribe for post-mortem writing (Pro+)
Status pages (public + internal)
Workflows for automation
Heartbeats for synthetic monitoring
REST API at api.incident.io
Default 600 req/min/org
Webhook delivery + Catalog API
OAuth 2.0 + Bearer tokens
Live call routing for paged engineers

Scroll for all 16

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Incident.io API Rules

4 rules · 3 warnings 1 info

SPECTRAL

JSON Schema 2

Standalone JSON Schema definitions for this provider's data models.

ListResponse

2 properties

JSON SCHEMA

Resource

0 properties

JSON SCHEMA

JSON Structure 1

JSON Structure definitions describing this provider's data shapes.

Incident Io Structure

0 properties

JSON STRUCTURE

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Incident Io Authentication

http · 1 scheme

SECURITY

Incident Io Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Incident Io Vulnerability Disclosure

security.txt · contact published

SECURITY

Incident Io Trust Center

SOC 2

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Incident Io Agentic Access

99 operations · 48 acting

99 operations · 48 acting

AGENTIC

Resources

Documentation 1

Reference material describing how the API behaves

Documentation
Documentation

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess
AgenticAccess
 LlmsText
LlmsText

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization
GitHubOrganization

Access & Security 4

Authentication, authorization, and security posture

TrustCenter
TrustCenter
 VulnerabilityDisclosure
VulnerabilityDisclosure
 DomainSecurity
DomainSecurity
 Authentication
Authentication

Company 3

The organization behind the API

LinkedIn
LinkedIn
 Website
Website
 Blog
Blog

Other 1

Properties that don't map to a standard resource type

VendorFacets
VendorFacets

Source (apis.yml)

apis.yml Raw ↑ 
aid: incident-io
name: Incident.io
description: incident.io is an incident management platform that helps teams declare, manage, and learn from incidents.
type: Index
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: true
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - openapi
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-09-03'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/incident-io.png
tags:
- AIOps
- Incident Management
- Monitoring
url: https://raw.githubusercontent.com/api-evangelist/incident-io/refs/heads/main/apis.yml
created: '2026-03-27'
modified: '2026-05-19'
specificationVersion: '0.23'
apis:
- aid: incident-io:incident-io-actions-api
  name: Incident.io Actions API
  description: The Actions API from Incident.io — 2 operation(s) for actions.
  humanURL: https://incident.io
  tags:
  - Actions
  properties:
  - type: OpenAPI
    url: openapi/incident-io-actions-api-openapi.yml
  - type: Documentation
    url: https://api-docs.incident.io
- aid: incident-io:incident-io-alert-attributes-api
  name: Incident.io Alert Attributes API
  description: The Alert Attributes API from Incident.io — 2 operation(s) for alert attributes.
  humanURL: https://incident.io
  tags:
  - Alert Attributes
  properties:
  - type: OpenAPI
    url: openapi/incident-io-alert-attributes-api-openapi.yml
  - type: Documentation
    url: https://api-docs.incident.io
- aid: incident-io:incident-io-alert-routes-api
  name: Incident.io Alert Routes API
  description: The Alert Routes API from Incident.io — 2 operation(s) for alert routes.
  humanURL: https://incident.io
  tags:
  - Alert Routes
  properties:
  - type: OpenAPI
    url: openapi/incident-io-alert-routes-api-openapi.yml
  - type: Documentation
    url: https://api-docs.incident.io
- aid: incident-io:incident-io-alert-sources-api
  name: Incident.io Alert Sources API
  description: The Alert Sources API from Incident.io — 2 operation(s) for alert sources.
  humanURL: https://incident.io
  tags:
  - Alert Sources
  properties:
  - type: OpenAPI
    url: openapi/incident-io-alert-sources-api-openapi.yml
  - type: Documentation
    url: https://api-docs.incident.io
- aid: incident-io:incident-io-alerts-api
  name: Incident.io Alerts API
  description: The Alerts API from Incident.io — 3 operation(s) for alerts.
  humanURL: https://incident.io
  tags:
  - Alerts
  properties:
  - type: OpenAPI
    url: openapi/incident-io-alerts-api-openapi.yml
  - type: Documentation
    url: https://api-docs.incident.io
- aid: incident-io:incident-io-api-keys-api
  name: Incident.io API Keys API
  description: The API Keys API from Incident.io — 3 operation(s) for api keys.
  humanURL: https://incident.io
  tags:
  - APIKeys
  tags_raw:
  - API Keys
  properties:
  - type: OpenAPI
    url: openapi/incident-io-api-keys-api-openapi.yml
  - type: Documentation
    url: https://api-docs.incident.io
- aid: incident-io:incident-io-catalog-entries-api
  name: Incident.io Catalog Entries API
  description: The Catalog Entries API from Incident.io — 2 operation(s) for catalog entries.
  humanURL: https://incident.io
  tags:
  - Catalog Entries
  properties:
  - type: OpenAPI
    url: openapi/incident-io-catalog-entries-api-openapi.yml
  - type: Documentation
    url: https://api-docs.incident.io
- aid: incident-io:incident-io-catalog-types-api
  name: Incident.io Catalog Types API
  description: The Catalog Types API from Incident.io — 2 operation(s) for catalog types.
  humanURL: https://incident.io
  tags:
  - Catalog Types
  properties:
  - type: OpenAPI
    url: openapi/incident-io-catalog-types-api-openapi.yml
  - type: Documentation
    url: https://api-docs.incident.io
- aid: incident-io:incident-io-custom-fields-api
  name: Incident.io Custom Fields API
  description: The Custom Fields API from Incident.io — 2 operation(s) for custom fields.
  humanURL: https://incident.io
  tags:
  - Custom Fields
  properties:
  - type: OpenAPI
    url: openapi/incident-io-custom-fields-api-openapi.yml
  - type: Documentation
    url: https://api-docs.incident.io
- aid: incident-io:incident-io-escalation-paths-api
  name: Incident.io Escalation Paths API
  description: The Escalation Paths API from Incident.io — 2 operation(s) for escalation paths.
  humanURL: https://incident.io
  tags:
  - Escalation Paths
  properties:
  - type: OpenAPI
    url: openapi/incident-io-escalation-paths-api-openapi.yml
  - type: Documentation
    url: https://api-docs.incident.io
- aid: incident-io:incident-io-escalations-api
  name: Incident.io Escalations API
  description: The Escalations API from Incident.io — 2 operation(s) for escalations.
  humanURL: https://incident.io
  tags:
  - Escalations
  properties:
  - type: OpenAPI
    url: openapi/incident-io-escalations-api-openapi.yml
  - type: Documentation
    url: https://api-docs.incident.io
- aid: incident-io:incident-io-follow-ups-api
  name: Incident.io Follow-ups API
  description: The Follow-ups API from Incident.io — 2 operation(s) for follow-ups.
  humanURL: https://incident.io
  tags:
  - Follow-ups
  properties:
  - type: OpenAPI
    url: openapi/incident-io-follow-ups-api-openapi.yml
  - type: Documentation
    url: https://api-docs.incident.io
- aid: incident-io:incident-io-incident-roles-api
  name: Incident.io Incident Roles API
  description: The Incident Roles API from Incident.io — 2 operation(s) for incident roles.
  humanURL: https://incident.io
  tags:
  - Incident Roles
  properties:
  - type: OpenAPI
    url: openapi/incident-io-incident-roles-api-openapi.yml
  - type: Documentation
    url: https://api-docs.incident.io
- aid: incident-io:incident-io-incident-statuses-api
  name: Incident.io Incident Statuses API
  description: The Incident Statuses API from Incident.io — 2 operation(s) for incident statuses.
  humanURL: https://incident.io
  tags:
  - Incident Statuses
  properties:
  - type: OpenAPI
    url: openapi/incident-io-incident-statuses-api-openapi.yml
  - type: Documentation
    url: https://api-docs.incident.io
- aid: incident-io:incident-io-incident-types-api
  name: Incident.io Incident Types API
  description: The Incident Types API from Incident.io — 2 operation(s) for incident types.
  humanURL: https://incident.io
  tags:
  - Incident Types
  properties:
  - type: OpenAPI
    url: openapi/incident-io-incident-types-api-openapi.yml
  - type: Documentation
    url: https://api-docs.incident.io
- aid: incident-io:incident-io-incidents-api
  name: Incident.io Incidents API
  description: The Incidents API from Incident.io — 2 operation(s) for incidents.
  humanURL: https://incident.io
  tags:
  - Incidents
  properties:
  - type: OpenAPI
    url: openapi/incident-io-incidents-api-openapi.yml
  - type: Documentation
    url: https://api-docs.incident.io
- aid: incident-io:incident-io-maintenance-windows-api
  name: Incident.io Maintenance Windows API
  description: The Maintenance Windows API from Incident.io — 2 operation(s) for maintenance windows.
  humanURL: https://incident.io
  tags:
  - Maintenance Windows
  properties:
  - type: OpenAPI
    url: openapi/incident-io-maintenance-windows-api-openapi.yml
  - type: Documentation
    url: https://api-docs.incident.io
- aid: incident-io:incident-io-postmortem-documents-api
  name: Incident.io Postmortem Documents API
  description: The Postmortem Documents API from Incident.io — 2 operation(s) for postmortem documents.
  humanURL: https://incident.io
  tags:
  - Postmortem Documents
  properties:
  - type: OpenAPI
    url: openapi/incident-io-postmortem-documents-api-openapi.yml
  - type: Documentation
    url: https://api-docs.incident.io
- aid: incident-io:incident-io-schedules-api
  name: Incident.io Schedules API
  description: The Schedules API from Incident.io — 2 operation(s) for schedules.
  humanURL: https://incident.io
  tags:
  - Schedule
  tags_raw:
  - Schedules
  properties:
  - type: OpenAPI
    url: openapi/incident-io-schedules-api-openapi.yml
  - type: Documentation
    url: https://api-docs.incident.io
- aid: incident-io:incident-io-severities-api
  name: Incident.io Severities API
  description: The Severities API from Incident.io — 2 operation(s) for severities.
  humanURL: https://incident.io
  tags:
  - Severities
  properties:
  - type: OpenAPI
    url: openapi/incident-io-severities-api-openapi.yml
  - type: Documentation
    url: https://api-docs.incident.io
- aid: incident-io:incident-io-status-pages-api
  name: Incident.io Status Pages API
  description: The Status Pages API from Incident.io — 2 operation(s) for status pages.
  humanURL: https://incident.io
  tags:
  - Status Pages
  properties:
  - type: OpenAPI
    url: openapi/incident-io-status-pages-api-openapi.yml
  - type: Documentation
    url: https://api-docs.incident.io
- aid: incident-io:incident-io-teams-api
  name: Incident.io Teams API
  description: The Teams API from Incident.io — 2 operation(s) for teams.
  humanURL: https://incident.io
  tags:
  - Team
  tags_raw:
  - Teams
  properties:
  - type: OpenAPI
    url: openapi/incident-io-teams-api-openapi.yml
  - type: Documentation
    url: https://api-docs.incident.io
- aid: incident-io:incident-io-users-api
  name: Incident.io Users API
  description: The Users API from Incident.io — 2 operation(s) for users.
  humanURL: https://incident.io
  tags:
  - User
  tags_raw:
  - Users
  properties:
  - type: OpenAPI
    url: openapi/incident-io-users-api-openapi.yml
  - type: Documentation
    url: https://api-docs.incident.io
- aid: incident-io:incident-io-utilities-api
  name: Incident.io Utilities API
  description: The Utilities API from Incident.io — 3 operation(s) for utilities.
  humanURL: https://incident.io
  tags:
  - Utilities
  properties:
  - type: OpenAPI
    url: openapi/incident-io-utilities-api-openapi.yml
  - type: Documentation
    url: https://api-docs.incident.io
- aid: incident-io:incident-io-workflows-api
  name: Incident.io Workflows API
  description: The Workflows API from Incident.io — 2 operation(s) for workflows.
  humanURL: https://incident.io
  tags:
  - Workflows
  properties:
  - type: OpenAPI
    url: openapi/incident-io-workflows-api-openapi.yml
  - type: Documentation
    url: https://api-docs.incident.io
common:
- type: VendorFacets
  url: vendor-facets/incident-io-vendor-facets.yml
- type: AgenticAccess
  url: agentic-access/incident-io-agentic-access.yml
- type: TrustCenter
  url: security/incident-io-trust-center.yml
- type: VulnerabilityDisclosure
  url: security/incident-io-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/incident-io-domain-security.yml
- type: Authentication
  url: authentication/incident-io-authentication.yml
- type: GitHubOrganization
  url: https://github.com/incident-io
- type: LinkedIn
  url: https://www.linkedin.com/company/incident-io
- type: Website
  url: https://incident.io
- type: Documentation
  url: https://api-docs.incident.io
- type: Features
  data:
  - 'Basic: free Slack/MS Teams native incident response'
  - 'Team: $15/user/mo annual + $10/user for on-call'
  - 'Pro: $25/user/mo + $20/user for on-call; AI Scribe, SSO/SAML'
  - 'Enterprise: custom; Slack Enterprise Grid, Sandbox, CSM'
  - 'On-Call only: $20/user/mo standalone alerting'
  - Slack-native and MS Teams-native flow
  - AI suggestions for incident triage
  - AI Scribe for post-mortem writing (Pro+)
  - Status pages (public + internal)
  - Workflows for automation
  - Heartbeats for synthetic monitoring
  - REST API at api.incident.io
  - Default 600 req/min/org
  - Webhook delivery + Catalog API
  - OAuth 2.0 + Bearer tokens
  - Live call routing for paged engineers
  sources:
  - https://incident.io/pricing
  updated: '2026-05-04'
- type: LlmsText
  url: https://incident.io/llms.txt
- type: Blog
  url: https://incident.io/blog
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider 
curl "https://apis.io/api/v1/providers/incident-io"
All providers 
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose 
curl "https://apis.io/api/v1/providers/incident-io/operations?limit=25"
How their score was established 
curl "https://apis.io/api/v1/providers/incident-io/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.