Report card

Do AI agents pick FireHydrant?

How often agents choose FireHydrant when a developer needs incident management — measured across Claude, GPT, Gemini.

FireHydrant

#6 of 6 incident mgmt
1%Pick Rate
95% CI 1%4%

When developers ask an AI agent for incident mgmt, FireHydrant is picked 1% of the time — ranking #6 of 6 measured across Claude, GPT, Gemini.

Picked 1% Named, not picked 25% Never surfaced 73%

Beaten by PagerDuty (17%), incident.io (9%), Grafana OnCall (3%), Rootly (3%), Opsgenie (2%).

Awareness

0 docs in FineWeb (10BT sample) · 2 URLs in Common Crawl

In the raw web crawl, but thin in the filtered corpus models actually train on — an awareness gap at the source.

Agent readiness

Level 0 · Not Ready · 1/16 agent standards

FireHydrant is missing robots.txt, Link headers, DNS-AID records, Markdown for agents. Readiness is what a site publishes for agents, not whether agents pick it — across our corpus the two barely correlate. Scored by Cloudflare's Agent Readiness score.

Get the full report

The per-model and per-surface breakdown for FireHydrant — where it wins, where it loses, and to whom — plus an alert when the Pick Rate moves.

About FireHydrant

Install

Links and summary verified from public sources.

The rest of the Incident Management ranking

← Full Incident Management leaderboard · How this is measured

FireHydrant — do AI agents pick it? · Pickrate