Is pagerduty.com agent ready?
pagerduty.com is largely agent ready: it scores 64/100 (grade B) on the w2agent rubric.
Changed since last check
+5 points since the previous check (2026-09-15)
Fixed: Agent/bot auth documentation, Reachable as Google-Agent
Category scores
Category breakdown not recorded for this audit.
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryPresent
- MCP discoveryPresent
- llms.txt validityPresent
Check results
Bot Accessibility
- ✓No error status codespass
- ✗Response timefail
- ✓XML sitemap existspass
- ✓AI agent accesspass
- ✓Edge treatment of agent user-agentstracked, not scoredpass
- ✓robots.txt existspass
- ✗Content negotiation (Markdown)fail
- —Declared AI usage preferencestracked, not scoredskip
Structured Data
- ✓OpenGraph meta tagspass
- ✓Semantic HTML elementspass
- ✗Appropriate Schema.org typefail
- ✗JSON-LD validfail
- ~Heading hierarchypartial
- ~Schema.org JSON-LD presentpartial
- ✗Schema.org completenessfail
Content Quality
- ✓FAQ contentpass
- ~Answer-first contentpartial
- ✓Content lengthpass
- ✓Token efficiency (HTML-to-text ratio)pass
- ✓Freshness signalspass
- ✗Author attributionfail
- ✓Citation readinesspass
- ✓Lists and tables for structured infopass
Agent Discovery
- ~llms.txt follows specpartial
- ✓llms.txt existspass
- —MCP server cardtracked, not scoredskip
- ✗Markdown alternate linksfail
- ✗/.well-known/agent-card.jsonfail
- ✓llms.txt links resolvepass
Agent Protocols
- ✓Discoverable API endpointspass
- ✓MCP endpointpass
- ✗Action schemasfail
- —/.well-known/ucpskip
- ✓Structured formspass
- —WebMCP imperative APItracked, not scoredskip
- —WebMCP declarative APItracked, not scoredskip
- ✓Reachable as Google-Agentpass
- ✓Reachable as ChatGPT-Userpass
- ✓Reachable as Perplexity-Userpass
Agent Auth
- —MCP authorization (401 challenge → protected resource metadata)skip
- ✗PKCE S256 supportfail
- ✗Public API surfacefail
- —Client ID Metadata Documents (bonus)skip
- —OpenAPI specificationskip
- ✓Agent/bot auth documentationpass
- ~OAuth discovery chain (RFC 9728 → RFC 8414)partial
- ✓Developer portalpass
- ✗Scoped API permissionsfail
- —API catalog (RFC 9727)skip
- —Agent operator signing directorytracked, not scoredskip
Technical
- ✓HTTPSpass
- ✓UTF-8 charsetpass
- ✓Canonical URLspass
- ✓Mobile viewportpass
- ✓Content accessible without JSpass
- ~Security headerspartial
Other
- ✓wp-page-builder-souppass
- ✓wp-rest-api-accessiblepass
- ✓wp-security-blocking-botspass
- ✓wp-robots-default-blockingpass
Score history
- 64/100 · rubric v3.0
- 59/100 · rubric v3.0
- 58/100 · rubric v2.0
- 58/100 · rubric v2.0
- 57/100 · rubric v2.0
- 54/100 · rubric v2.0
- 48/100 · rubric v2.0
- 47/100 · rubric v2.0
- 48/100 · rubric v2.0
- 48/100 · rubric v2.0