# FireHydrant

> FireHydrant helps teams plan, respond, and learn from incidents via AI‑enriched automation, alerts, retrospective tooling, and status pages.

## Navigation & Core Site Sections
Below are the main public pages / navigation links of the site:
- [Our Objective](https://firehydrant.com/our-objective/)
- Platform
  - [Overview](https://firehydrant.com/platform/)
  - [Plan](https://firehydrant.com/plan/)
  - [Respond](https://firehydrant.com/respond/)
  - [Improve](https://firehydrant.com/improve/)
  - [Why Firehydrant](https://firehydrant.com/why-firehydrant/)
- Documentation
  - [Quickstart](https://docs.firehydrant.com/docs/admin-quickstart)
  - [Integrations](https://firehydrant.com/integrations/)
  - [Documentation](https://docs.firehydrant.com/docs/what-is-firehydrant/)
  - [API Reference](https://developers.firehydrant.com/)
- Resources
  - [Customer Stories](https://firehydrant.com/customer-stories/)
  - [Blog ](https://firehydrant.com/blog/)
  - [Guides and Events](https://firehydrant.com/resources/)
  - [Changelog](https://firehydrant.com/changelog/)
  - [4 Minute Demo ](https://firehydrant.com/4min-demo/)
- [Pricing](https://firehydrant.com/pricing/)
## Documentation & Developer Resources
This section links to their documentation and API reference materials:

- [Docs Home](https://docs.firehydrant.com) — central docs site (moved from Zendesk)
- **Guides & Tutorials**
  - Web UI Responder Guide — managing incidents via the UI
  - User Administration — managing accounts, roles, permissions
  - Miscellaneous Settings — org settings, features toggles
  - Shortcut Integration — mapping to external ticketing tool
- **API & Reference**
  - [FireHydrant API Reference](https://docs.firehydrant.com/reference/firehydrant-api) — endpoints, authentication, usage
- **Product / Feature Docs**
  - Status Pages Setup & Configuration — setting up status pages in FireHydrant
- **Changelog / Release Notes**
  - Changelog (as above) — incremental updates & features

## Sitemap / Structural Resources
These are resources the LLM should prioritize for building site structure or crawling deeper:

- `https://firehydrant.com/sitemap-index.xml` — for all indexed pages
- Documentation site structure (e.g. Table of Contents pages in docs)
- API reference introspection pages (for parameter / schema discovery)

## Optional / Lower Priority Resources
These are additional pages or contexts that may be useful if context or token budget allows:

- Migration or competitive guides (e.g. “Migrate from PagerDuty”)
- Blog posts, announcements beyond changelog
- Press / news mentions (e.g. TechCrunch article on FireHydrant acquiring Blameless ([techcrunch.com](https://techcrunch.com/2024/08/21/two-incident-management-startups-join-forces-as-firehydrant-nabs-blameless/)))

## Bot Access Policy

FireHydrant's preferences for AI/LLM access, training, and content usage:

- **User-agent: gptbot**
  Allow-Training: yes
  Allow-Retrieval: yes

- **User-agent: claudebot**
  Allow-Training: yes
  Allow-Retrieval: yes

- **User-agent: google-extended**
  Allow-Training: yes
  Allow-Retrieval: yes

- **User-agent: perplexitybot**
  Allow-Training: yes
  Allow-Retrieval: yes

- **User-agent: neevabot**
  Allow-Training: yes
  Allow-Retrieval: yes

- **User-agent: youbot**
  Allow-Training: yes
  Allow-Retrieval: yes

- **User-agent: ccbot**
  Allow-Training: yes
  Allow-Retrieval: yes

- **User-agent: duckduckbot**
  Allow-Training: yes
  Allow-Retrieval: yes

- **User-agent: yandexbot**
  Allow-Training: yes
  Allow-Retrieval: yes

- **User-agent: archive.org_bot**
  Allow-Training: yes
  Allow-Retrieval: yes

### Default Rule for Unspecified or Future Bots

- **User-agents:**
  Allow-Training: yes
  Allow-Retrieval: yes