[
  {
    "id": "rootly-docs-1",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com",
    "excerpt": "Declare, run, and resolve an incident from Slack, Google Chat, and Microsoft Teams.",
    "fetchedAt": "2026-09-07T04:53:56.435Z"
  },
  {
    "id": "rootly-docs-2",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com",
    "excerpt": "Bring your schedules, escalation policies, and more without a rebuild.",
    "fetchedAt": "2026-09-07T04:53:56.435Z"
  },
  {
    "id": "rootly-docs-3",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/help-and-documentation.md",
    "excerpt": "Migrating from Opsgenie",
    "fetchedAt": "2026-09-07T04:53:56.435Z"
  },
  {
    "id": "rootly-docs-4",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/help-and-documentation.md",
    "excerpt": "Migrating from PagerDuty",
    "fetchedAt": "2026-09-07T04:53:56.435Z"
  },
  {
    "id": "rootly-docs-5",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/on-call/on-call.md",
    "excerpt": "Every critical signal reaches the right human, right away, with zero manual coordination.",
    "fetchedAt": "2026-09-07T04:53:56.435Z"
  },
  {
    "id": "rootly-docs-6",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/on-call/schedules.md",
    "excerpt": "These schedules determine **who is on-call at any given time** and control the **rotation** of on-call duties across users or teams.",
    "fetchedAt": "2026-09-07T04:53:56.435Z"
  },
  {
    "id": "rootly-docs-7",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/on-call/escalation-policies.md",
    "excerpt": "Escalation Policies define **how Rootly notifies responders when an alert requires attention** and what happens if that alert is not acknowledged in time.",
    "fetchedAt": "2026-09-07T04:53:56.435Z"
  },
  {
    "id": "rootly-docs-8",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/on-call/live-call-routing.md",
    "excerpt": "Turn a phone call into a page. Route inbound calls to the on-call responder, or drop them to voicemail with an automatic alert.",
    "fetchedAt": "2026-09-07T04:53:56.435Z"
  },
  {
    "id": "rootly-docs-9",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/alerts/alert-deduplication.md",
    "excerpt": "Collapse repeat events from the same monitor into a single open Rootly alert using a stable identifier, so responders aren't paged twice.",
    "fetchedAt": "2026-09-07T04:53:56.435Z"
  },
  {
    "id": "rootly-docs-10",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/alerts/alert-routing.md",
    "excerpt": "Use Alert Routes to determine which teams, services, and escalation policies receive incoming alerts from your monitoring tools based on conditions you define.",
    "fetchedAt": "2026-09-07T04:53:56.435Z"
  },
  {
    "id": "rootly-docs-11",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/incidents/creating-incidents/creating-incidents-via-api.md",
    "excerpt": "The Rootly API allows you to create incidents automatically from monitoring tools, CI/CD pipelines, internal services, or any external automation system.",
    "fetchedAt": "2026-09-07T04:53:56.435Z"
  },
  {
    "id": "rootly-docs-12",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/incidents/incident-timeline/incident-timeline.md",
    "excerpt": "The incident timeline is the **authoritative record of what happened during an incident**.",
    "fetchedAt": "2026-09-07T04:53:56.435Z"
  },
  {
    "id": "rootly-docs-13",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/retrospectives/retrospectives.md",
    "excerpt": "sections like Summary, Impact, Root Cause, Mitigation, Resolution, and Curated Timeline get drafted automatically from the incident's data, Slack channel, and bridge-call transcripts",
    "fetchedAt": "2026-09-07T04:53:56.435Z"
  },
  {
    "id": "rootly-docs-14",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/retrospectives/retrospectives.md",
    "excerpt": "Rootly lets you define multiple processes and route each incident to the right one based on severity, type, or team, so a SEV0 gets full formal treatment while a SEV3 gets a lightweight review.",
    "fetchedAt": "2026-09-07T04:53:56.435Z"
  },
  {
    "id": "rootly-docs-15",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/collaborative-retrospectives/overview.md",
    "excerpt": "Real-time collaboration so multiple authors can wo",
    "fetchedAt": "2026-09-07T04:53:56.435Z"
  },
  {
    "id": "rootly-docs-16",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/workflows/workflows.md",
    "excerpt": "Workflows are Rootly's automation engine. They let you run structured actions automatically (or manually) based on: **Trigger events**",
    "fetchedAt": "2026-09-07T04:53:56.435Z"
  },
  {
    "id": "rootly-docs-17",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/workflows/actions-reference.md",
    "excerpt": "Reference for all 152 Rootly workflow action types, grouped by category: Slack, Google Chat, Jira, on-call, AI, and incident operations.",
    "fetchedAt": "2026-09-07T04:53:56.435Z"
  },
  {
    "id": "rootly-docs-18",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/configuration/status-pages.md",
    "excerpt": "It only takes about a minute to set up a status page, so set one up soon after you've signed up.",
    "fetchedAt": "2026-09-07T04:53:56.435Z"
  },
  {
    "id": "rootly-docs-19",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/configuration/status-page-public-api.md",
    "excerpt": "Rootly exposes a public JSON API on your status page's custom domain, allowing you to programmatically retrieve current status and incident data.",
    "fetchedAt": "2026-09-07T04:53:56.435Z"
  },
  {
    "id": "rootly-docs-20",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/ai/ai-summaries.md",
    "excerpt": "AI Summaries writes it for you, from what the incident already knows: metadata, alerts, timeline events, action items, and (when permitted) Slack messages and meeting transcripts.",
    "fetchedAt": "2026-09-07T04:53:56.435Z"
  },
  {
    "id": "rootly-docs-21",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/ai/ask-rootly-ai.md",
    "excerpt": "Rootly AI in Web is an AI chat built into the incident page of the Rootly web app. Open it on any incident and ask questions in natural language.",
    "fetchedAt": "2026-09-07T04:53:56.435Z"
  },
  {
    "id": "rootly-docs-22",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/integrations/mcp-server.md",
    "excerpt": "This means you can query incidents, check on-call schedules, find similar past incidents, and take action \u2014 all from within Cursor, Windsurf, Claude Code, Gemini CLI, or any other MCP-compatible environment.",
    "fetchedAt": "2026-09-07T04:53:56.435Z"
  },
  {
    "id": "rootly-docs-23",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/integrations/mcp-server.md",
    "excerpt": "**`find_related_incidents`** \u2014 uses TF-IDF similarity analysis to surface historically similar incidents",
    "fetchedAt": "2026-09-07T04:53:56.435Z"
  },
  {
    "id": "rootly-docs-24",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/api-reference/overview",
    "excerpt": "To generate a new API key, navigate to: **Organization dropdown** > **Organization Settings** > **API Keys > Generate New API Key**.",
    "fetchedAt": "2026-09-07T04:53:56.435Z"
  },
  {
    "id": "rootly-docs-25",
    "tier": "claimed-docs",
    "url": "https://rootly.com/changelog",
    "excerpt": "Atlassian is shutting down Opsgenie and we've made it even easier to switch to Rootly.",
    "fetchedAt": "2026-09-07T04:56:21.614Z"
  },
  {
    "id": "rootly-docs-26",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/on-call/schedules.md",
    "excerpt": "Create, manage, and maintain on-call schedules in Rootly with rotations, layers, overrides, restrictions, and previews to keep coverage clear and predictable.",
    "fetchedAt": "2026-09-07T04:56:21.614Z"
  },
  {
    "id": "rootly-docs-27",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/retrospectives/retrospectives.md",
    "excerpt": "sections like Summary, Impact, Root Cause, Mitigation, Resolution, and Curated Timeline get drafted automatically from the incident's data, Slack channel, and bridge-call transcripts.",
    "fetchedAt": "2026-09-07T04:56:21.614Z"
  },
  {
    "id": "rootly-docs-28",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/collaborative-retrospectives/overview.md",
    "excerpt": "Rootly includes a rich text editor in retrospectives that supports live incident data and real-time collaboration - all without leaving the platform.",
    "fetchedAt": "2026-09-07T04:56:21.614Z"
  },
  {
    "id": "rootly-docs-29",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/workflows/workflows.md",
    "excerpt": "Workflows are Rootly's automation engine. They let you run structured actions automatically (or manually) based on: **Trigger events**... **Run conditions**... **Actions**",
    "fetchedAt": "2026-09-07T04:56:21.614Z"
  },
  {
    "id": "rootly-docs-30",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/ai/ai-summaries.md",
    "excerpt": "Run `/rootly summary` in the incident channel.",
    "fetchedAt": "2026-09-07T04:56:21.614Z"
  },
  {
    "id": "rootly-docs-31",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/integrations/mcp-server.md",
    "excerpt": "you can query incidents, check on-call schedules, find similar past incidents, and take action \u2014 all from within Cursor, Windsurf, Claude Code, Gemini CLI, or any other MCP-compatible environment.",
    "fetchedAt": "2026-09-07T04:56:21.614Z"
  },
  {
    "id": "rootly-docs-32",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com",
    "excerpt": "Migrate from another tool Bring your schedules, escalation policies, and more without a rebuild.",
    "fetchedAt": "2026-09-07T04:58:10.475Z"
  },
  {
    "id": "rootly-docs-33",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/integrations/mcp-server.md",
    "excerpt": "you can query incidents, check on-call schedules, find similar past incidents, and take action \u2014 all from within Cursor, Windsurf, Claude Code, Gemini CLI, or any other MCP-compatible environment",
    "fetchedAt": "2026-09-07T04:58:10.475Z"
  },
  {
    "id": "rootly-docs-34",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/help-and-documentation.md",
    "excerpt": "Automation that runs your response: channels created, stakeholders updated, tickets filed, retros started, the same way every time.",
    "fetchedAt": "2026-09-07T04:58:10.475Z"
  },
  {
    "id": "rootly-docs-35",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/on-call/live-call-routing.md",
    "excerpt": "Live Call Routing gives your team a phone number that pages the right person. A caller dials the number, Rootly figures out who's on call, and either connects the two live or takes a message and pages the on-call responder.",
    "fetchedAt": "2026-09-07T04:58:10.475Z"
  },
  {
    "id": "rootly-docs-36",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/alerts/alert-deduplication.md",
    "excerpt": "Alert Deduplication collapses those repeat events onto a single open alert, so the responder sees the count climbing instead of getting paged again.",
    "fetchedAt": "2026-09-07T04:58:10.475Z"
  },
  {
    "id": "rootly-docs-37",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/alerts/alert-routing.md",
    "excerpt": "Rootly provides a unified routing layer that works across all alert sources, enabling consistent on-call workflows.",
    "fetchedAt": "2026-09-07T04:58:10.475Z"
  },
  {
    "id": "rootly-docs-38",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/configuration/status-pages.md",
    "excerpt": "Status pages allow you to quickly communicate information about the health of your services and applications to internal stakeholders and external customers.",
    "fetchedAt": "2026-09-07T04:58:10.475Z"
  },
  {
    "id": "rootly-docs-39",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/on-call/escalation-policies.md",
    "excerpt": "Configure Rootly escalation policies with multi-step targets, time delays, and round robin to make sure on-call alerts get acknowledged and acted on.",
    "fetchedAt": "2026-09-07T04:58:10.475Z"
  },
  {
    "id": "rootly-docs-40",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/incidents/incident-timeline/incident-timeline.md",
    "excerpt": "The incident timeline is the authoritative record of what happened during an incident.",
    "fetchedAt": "2026-09-07T04:58:10.475Z"
  },
  {
    "id": "rootly-docs-41",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/workflows/workflows.md",
    "excerpt": "Workflows are Rootly's automation engine. They let you run structured actions automatically (or manually) based on: Trigger events... Run conditions... Actions",
    "fetchedAt": "2026-09-07T05:00:36.460Z"
  },
  {
    "id": "rootly-docs-42",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/collaborative-retrospectives/overview.md",
    "excerpt": "Incident metadata that resolves to actual values and stays in sync as you write... Real-time collaboration so multiple authors can wo",
    "fetchedAt": "2026-09-07T05:00:36.460Z"
  },
  {
    "id": "rootly-docs-43",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/help-and-documentation.md",
    "excerpt": "Rootly mobile app for iOS and Android on-ca",
    "fetchedAt": "2026-09-07T05:00:36.460Z"
  },
  {
    "id": "rootly-docs-44",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/integrations/mcp-server.md",
    "excerpt": "The Rootly MCP Server implements the Model Context Protocol to expose Rootly incident data and actions as tools that any MCP-compatible client can use.",
    "fetchedAt": "2026-09-07T05:02:27.131Z"
  },
  {
    "id": "rootly-docs-45",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/workflows/workflows.md",
    "excerpt": "Create or manage an incident communication channel (Slack or Microsoft Teams)",
    "fetchedAt": "2026-09-07T05:02:27.131Z"
  },
  {
    "id": "rootly-docs-46",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/configuration/status-pages.md",
    "excerpt": "Rootly has two types of status pages available: public status pages and private status pages.",
    "fetchedAt": "2026-09-07T05:02:27.131Z"
  },
  {
    "id": "rootly-docs-47",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/ai/ai-summaries.md",
    "excerpt": "Run /rootly summary in the incident channel.",
    "fetchedAt": "2026-09-07T05:02:27.131Z"
  },
  {
    "id": "rootly-docs-48",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/ai/ai-summaries.md",
    "excerpt": "The summary, expanded and delivered privately to responders joining midstream. Only you see it.",
    "fetchedAt": "2026-09-07T05:02:27.131Z"
  },
  {
    "id": "rootly-docs-49",
    "tier": "claimed-docs",
    "url": "https://docs.rootly.com/api-reference/overview",
    "excerpt": "Global API Keys are assigned an On-Call and Incident Response role when they\u2019re generated.",
    "fetchedAt": "2026-09-07T05:02:27.131Z"
  },
  {
    "id": "rootly-comm-1",
    "tier": "community",
    "url": "https://news.ycombinator.com/item?id=31653985",
    "excerpt": "User: 'Just built out Rootly and it's fantastic product. JJ and team are responsive and heavily engaged with customers... Having trialed Rootly against competing products Rootly won out for the customer engagement. The competition just wasn't responsive.'",
    "fetchedAt": "2026-09-07T05:06:42.532Z"
  },
  {
    "id": "rootly-comm-2",
    "tier": "community",
    "url": "https://news.ycombinator.com/item?id=31653985",
    "excerpt": "User: after implementing Rootly, incident volume increased rapidly as teams began treating issues as real incidents; though metrics looked worse, it actually led to better problem management and stability.",
    "fetchedAt": "2026-09-07T05:06:42.532Z"
  },
  {
    "id": "rootly-comm-3",
    "tier": "community",
    "url": "https://news.ycombinator.com/item?id=31653985",
    "excerpt": "Multiple commenters complained about Rootly's lack of upfront pricing: 'no pricing, no thanks' and 'the lack of transparency on cost led me to immediately dismiss it as an option.'",
    "fetchedAt": "2026-09-07T05:06:42.532Z"
  },
  {
    "id": "rootly-comm-4",
    "tier": "community",
    "url": "https://news.ycombinator.com/item?id=31653985",
    "excerpt": "Commenter questioned Rootly's value beyond basic automation: 'how is this more than a glorified Slack workflow to a generic ticketing system? ... This could be easily done with an engineer/tech following a runbook.'",
    "fetchedAt": "2026-09-07T05:06:42.532Z"
  },
  {
    "id": "rootly-comm-5",
    "tier": "community",
    "url": "https://news.ycombinator.com/item?id=31653985",
    "excerpt": "Feedback on Rootly's Slack-centric design: 'why base everything on Slack? ... it indirectly adds cost to your product; if I want to use Rootly I also have to pay for Slack (which is expensive).'",
    "fetchedAt": "2026-09-07T05:06:42.532Z"
  },
  {
    "id": "rootly-comm-6",
    "tier": "community",
    "url": "https://news.ycombinator.com/item?id=31653985",
    "excerpt": "User comparing workflow preference: 'Took a quick look at your loom. Very cool. In practice, we prefer just looking through a single channel with threads, but perhaps that's because we're a small team.'",
    "fetchedAt": "2026-09-07T05:06:42.532Z"
  },
  {
    "id": "rootly-comm-7",
    "tier": "community",
    "url": "https://news.ycombinator.com/item?id=39606393",
    "excerpt": "Commenter skeptical of Rootly On-Call launch: 'Not even the best competitor to pagerduty released in the last 72 hours... Any engineering team worth their weight realises that its not a drop-in solution to PD and barely solves any hard problems.'",
    "fetchedAt": "2026-09-07T05:06:42.532Z"
  },
  {
    "id": "rootly-comm-8",
    "tier": "community",
    "url": "https://news.ycombinator.com/item?id=42431144",
    "excerpt": "User praised Rootly's CEO JJ as unusually customer-focused: 'This dude is relentless... I don't know I've seen a CEO as deeply customer focused in quite some time, he really is a pro.'",
    "fetchedAt": "2026-09-07T05:06:42.532Z"
  },
  {
    "id": "rootly-probe-1",
    "tier": "probe",
    "url": "https://docs.rootly.com/llms.txt",
    "excerpt": "PROBE llms.txt: HTTP 200 at https://docs.rootly.com/llms.txt # Rootly\n\n> Rootly is an incident management platform that helps engineering teams detect, respond to, and learn from in",
    "fetchedAt": "2026-09-07T05:07:08.489Z"
  },
  {
    "id": "rootly-probe-2",
    "tier": "probe",
    "url": "https://docs.rootly.com/openapi.json",
    "excerpt": "PROBE openapi: all candidate paths 404 (https://docs.rootly.com/openapi.json, https://docs.rootly.com/swagger.json, https://docs.rootly.com/api/openapi.json, https://docs.rootly.com/.well-known/openapi.json)",
    "fetchedAt": "2026-09-07T05:07:08.489Z"
  },
  {
    "id": "rootly-probe-3",
    "tier": "probe",
    "url": "https://docs.rootly.com/integrations/mcp-server",
    "excerpt": "official MCP server documented at https://docs.rootly.com/integrations/mcp-server",
    "fetchedAt": "2026-09-07T05:07:08.489Z"
  },
  {
    "id": "rootly-probe-rt-1",
    "tier": "probe",
    "url": "https://docs.rootly.com/integrations/mcp-server",
    "excerpt": "PROBE runtime (recorded 2026-09-06): Rootly's hosted remote MCP server is live \u2014 a keyless JSON-RPC initialize POST to https://mcp.rootly.com/mcp returned HTTP 401 with WWW-Authenticate Bearer resource_metadata=https://mcp.rootly.com/.well-known/oauth-protected-resource.",
    "fetchedAt": "2026-09-07T05:12:52.000Z"
  },
  {
    "id": "rootly-probe-rt-2",
    "tier": "probe",
    "url": "https://github.com/rootlyhq/rootly-mcp-server",
    "excerpt": "PROBE runtime (recorded 2026-09-06): the official rootly-mcp-server installed keylessly from pypi via uvx and started far enough to log its server_start audit event (tool_count 124, transport stdio, write_tools_enabled with 135 write paths), then cleanly gated on the documented ROOTLY_API_TOKEN environment variable.",
    "fetchedAt": "2026-09-07T05:12:52.000Z"
  }
]