Create a Statuspage automation token: navigate to Manage Account > API and generate a page-scoped automation token for use in scripts
Map monitoring alerts to component IDs: GET /v1/pages/{page_id}/components to retrieve all component IDs; build a lookup map from service/component name to Statuspage component ID in your alerting glue code
On alert fire: POST /v1/pages/{page_id}/incidents with status: investigating, body with the alert summary, and components hash mapping affected component IDs to partial_outage or major_outage
On alert resolve: PATCH /v1/pages/{page_id}/incidents/{incident_id} with status: resolved and a resolution body; set component_ids to reset them to operational
Configure subscriber notifications: set deliver_notifications: true on incident creation to immediately notify email and webhook subscribers
Implement idempotency: store the Statuspage incident_id in your alerting system when creating; on subsequent alerts for the same issue, update the existing incident rather than creating a new one
Known gotchas
Statuspage incidents and maintenance windows share the same 100 open-incident limit; if your monitoring pipeline creates per-alert incidents, you can hit this limit within hours during an incident storm
Component status updates in the incident payload update the public component status immediately, even before subscribers are notified; ensure the component status accurately reflects customer impact before setting it
Automation tokens are distinct from user API tokens; they have page-scoped permissions and are the correct credential for machine-generated status updates
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp