# PagerDuty — API Agent Score

> Score: 72/100 (Grade: B) | Domain: pagerduty.com | Rubric: 1.0.0 | Checked: July 24, 2026

PagerDuty scored 72/100 (B), classified "partially-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/pagerduty)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 72/100 (B)
- Classification: partially-ready

## Category Scores

- API Design: 78/100 (B)
- Developer Experience: 75/100 (B)
- Agent Discovery: 69/100 (C)
- Agent Understanding: 72/100 (B)
- Agent Usability: 68/100 (C)

## Check Results

### API Design

- [warn] Machine-readable, versioned contract — info.version="2.0.0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 83%, docs 67%.
- [warn] Schema coverage & depth — 85% of operations have documented schemas (target 95%+). Investigated: spec 78%, sdk 70%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [pass] Example coverage — 12% example coverage. Investigated: spec 100%, sdk 50%, docs 0%.
- [warn] Auth declared & discoverable — No securitySchemes declared. Investigated: docs 33%, spec 17%.

### Developer Experience

- [pass] Self-service developer portal — Self-service signup at https://www.pagerduty.com/sign-up/; free tier / sandbox documented. Investigated: docs 100%.
- [pass] Description completeness — 33% description completeness. Investigated: spec 100%, sdk 62%.
- [pass] Changelog published — Newest official SDK activity 8 day(s) ago. Investigated: sdk 100%, spec 0%, docs 0%.
- [warn] Quickstart present — Quickstart page reachable (12 variants scanned starting at https://developer.pagerduty.com/quickstart) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [fail] Code samples in docs — No detectable code samples across 1 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/support_pagerduty_main, 771 snippets). Investigated: docs 100%, sdk 67%, mcp 50%, cli 0%, wellknown 0%.
- [warn] Docs reachable, not hard auth-gated — 7 of 7 pages return 200 for non-existent URLs (soft 404). Investigated: docs 50%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developer.pagerduty.com/llms.txt, https://developer.pagerduty.com/docs/llms.txt). Investigated: docs 33%, sdk 0%.
- [warn] Crawlable / AEO — Sitemap present (0 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Only 2 distinct 4xx/5xx codes documented (plus 0 "default" catch-all responses). Investigated: docs 100%, sdk 100%, spec 50%.
- [pass] Operation purpose clarity — 100% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — 7 of 7 pages appear to be client-side rendered SPA shells (___gatsby detected); agents using HTTP fetches will see no content. Investigated: docs 57%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (spec, sdk) is 2% (threshold 35% for full credit).
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [fail] Docs structured data — Neither JSON-LD nor OpenGraph/meta tags detected across 1 sampled pages — likely a CSR-only docs site. Investigated: docs 0%.

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%, spec 0%, docs 0%.
- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%, spec 0%, docs 0%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

PagerDuty's API program shows solid foundations in design, contract readiness, and documentation structure — but partners and their AI agents face real friction where it matters most: finding actionable context, understanding how to use the API correctly, and running real workflows without guesswork. The two weakest areas are agent understanding (missing machine-readable instructions and structured doc signals) and agent usability (no runnable, test-backed collections). Prioritizing these gaps will unlock faster partner integration and make PagerDuty's APIs genuinely agent-ready.