Obtain a FireHydrant API token from Settings > API Keys; authenticate all requests with Authorization: Bearer YOUR_TOKEN and Content-Type: application/json
List available severities and environments: GET /v1/severities and GET /v1/environments to retrieve IDs required for incident creation
Declare an incident: POST /v1/incidents with name, severity.id, and optionally impacted_services (array of service IDs from GET /v1/services) and environments
Attach and trigger a runbook: POST /v1/incidents/{id}/runbook_actions to manually trigger a runbook step, or configure the runbook in FireHydrant UI to auto-attach based on conditions like severity or impacted service
Add a timeline event or status update: POST /v1/incidents/{id}/events with type and body to document decisions or communications during the incident
Resolve the incident: PATCH /v1/incidents/{id} with state: resolved and a resolution summary; this triggers any configured resolution runbook steps
Known gotchas
FireHydrant was acquired by Freshworks in December 2025 and is being integrated into Freshservice; API endpoint URLs and authentication may change during this transition — monitor FireHydrant changelog for breaking changes
Runbooks auto-attach based on conditions evaluated at declaration time; if a service or severity is added after declaration, the runbook must be manually triggered or re-attached
FireHydrant has 350+ documented API endpoints; use the OpenAPI spec (available in their docs) to generate typed clients rather than handwriting requests
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