Reference

Use reference pages when you need an exact contract rather than a workflow:

• API authentication
• Events API v2
• Incidents API
• API responses and errors
• API implementation inventory
• Configuration
• Command line
• Permissions
• Service automation fields, rules, versions, and readiness
• Runbook steps, inputs, permissions, and limits
• Notification delivery
• Outbound webhooks
• Health endpoints
• Metrics
• Runtime limits
• Product feature classification
• Keyboard shortcuts
• Accessibility support and validation

Reference content is generated or validated against routes, schemas, types, configuration, deployment manifests, and tests. It must describe implemented contracts without speculative guidance.