PagerDuty
PagerDuty is a digital operations management platform that helps teams detect problems and resolve incidents with automated alerting, on-call management, and incident response workflows.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles PagerDuty the way a machine reads it — 100 machine-readable artifacts across 38 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — PagerDuty scores 61.9/100 (strong), with a separate agent-readiness read of 53/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-28 · rubric v0.6
How we profile PagerDuty
Each block below is one kind of artifact we hold for PagerDuty. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 38
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
PagerDuty Events API
The PagerDuty Events API is a system for triggering, acknowledging, and resolving alerts from monitoring tools and other data sources.
PagerDuty Abilities API
This describes your account's abilities by feature name. For example `"teams"`. An ability may be available to your account based on things like your pricing plan or account state.
PagerDuty Add-Ons API
Developers can write their own functionality to insert into PagerDuty's UI.
PagerDuty Alert Grouping Settings API
Alert Grouping Settings allow you to configure how alerts in services are grouped together into incidents.
PagerDuty Analytics API
Provides enriched incident data.
PagerDuty Audit API
Provides audit record data.
PagerDuty Automation Actions API
Automation Actions invoke jobs that are staged in Runbook Automation or Process Automation.
PagerDuty Business Services API
Business services model capabilities that span multiple technical services and that may be owned by several different teams.
PagerDuty Change Events API
Change Events enable you to send informational events about recent changes such as code deploys and system config changes from any system that can make an outbound HTTP connecti...
PagerDuty Change Tags API
The Change Tags API from PagerDuty — 1 operation(s) for change tags.
PagerDuty Custom Fields API
Custom fields allow you to enrich PagerDuty incidents with critical and helpful metadata throughout the incident lifecycle.
PagerDuty Escalation Policies API
Escalation policies define which user should be alerted at which time.
PagerDuty Event Orchestrations API
Event Orchestrations allow you to route events to an endpoint and create collections of Event Orchestrations, which define sets of actions to take based on event content.
PagerDuty Extension Schemas API
A PagerDuty extension vendor represents a specific type of outbound extension such as Generic Webhook, Slack, ServiceNow.
PagerDuty Extensions API
Extensions are representations of Extension Schema objects that are attached to Services.
PagerDuty Incident Workflows API
An Incident Workflow is a sequence of configurable Steps and associated Triggers that can execute automated Actions for a given Incident.
PagerDuty Incidents API
An incident represents a problem or an issue that needs to be addressed and resolved. Incidents trigger on a service, which prompts notifications to go out to on-call responders...
PagerDuty Licenses API
Licenses are allocated to Users to allow for per-User access to PagerDuty functionality within an Account.
PagerDuty Log Entries API
A log of all the events that happen to an Incident, and these are exposed as Log Entries.
PagerDuty Maintenance Windows API
A Maintenance Window is used to temporarily disable one or more Services for a set period of time.
PagerDuty Notifications API
A Notification is created when an Incident is triggered or escalated.
PagerDuty On-Calls API
An on-call represents a contiguous unit of time for which a User will be on call for a given Escalation Policy and Escalation Rules
PagerDuty Paused Incident Reports API
Provides paused Incident reporting data on services and accounts that have paused Alerts.
PagerDuty Priorities API
A priority is a label representing the importance and impact of an incident. This feature is only available on Standard and Enterprise plans.
PagerDuty Response Plays API
Response Plays are a package of Incident Actions that can be applied during an Incident's life cycle.
PagerDuty Rulesets API
Rulesets allow you to route events to an endpoint and create collections of Event Rules, which define sets of actions to take based on event content.
PagerDuty Schedules API
A Schedule determines the time periods that users are On-Call.
PagerDuty Service Dependencies API
Services are categorized into technical and business services. Dependencies can be created via any combination of these services.
PagerDuty Services API
The Services API from PagerDuty — 8 operation(s) for services.
PagerDuty Standards API
Standards help provide a clear understanding of what a good service configuration looks like, allowing to share and enforce organization guidelines across services to ensure adh...
PagerDuty Status Dashboards API
Status Dashboards represent user-defined views for the Status Dashboard product that are limited to specific Business Services rather than the whole set of top-level Business Se...
PagerDuty Status Pages API
Status Pages can be public or private read-only pages, that display the status of some predefined set of services, to be shared with customers or internal stakeholders.
PagerDuty Tags API
The Tags API from PagerDuty — 4 operation(s) for tags.
PagerDuty Teams API
A team is a collection of Users and Escalation Policies that represent a group of people within an organization.
PagerDuty Templates API
Templates is a new feature which will allow customers to create message templates to be leveraged by (but not limited to) status updates. The API will be secured to customers wi...
PagerDuty Users API
Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account.
PagerDuty Vendors API
A PagerDuty Vendor represents a specific type of integration. AWS Cloudwatch, Splunk, Datadog are all examples of vendors
PagerDuty Webhooks API
A webhook is a way to receive events that occur on the PagerDuty platform via an HTTP POST request. V3 webhooks are set up by creating a webhook subscription.
Scroll within the panel for all 38 ·
Postman Collections 37
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
PagerDuty Abilities API
POSTMANPagerDuty Abilities Tags API
POSTMANScroll within the panel for all 37 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
MCP Server
MCP SERVERGraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
PagerDuty GraphQL Schema
PagerDuty is a digital operations management platform providing incident management, on-call scheduling, and automated alerting for engineering and operations teams. This concep...
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Pagerduty Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Pagerduty Finops
FINOPSFeatures 15
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Scroll within the panel for all 15 ·
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
PagerDuty Events
AsyncAPI description of PagerDuty's event-driven surface. Two complementary channels are modelled: 1. Outbound V3 Webhooks — PagerDuty POSTs a JSON envelope to subscriber URLs w...
ASYNCAPISpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
PagerDuty API Rules
SPECTRALSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for PagerDuty — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/pagerduty · machine-readable index on apis.io