---
title: "Providers' documentation"
description: "How Halon reads the documentation of the tools you connect, where it comes from, how it stays current and how Halon cites it."
canonical: https://firefight.app/docs/ai/provider-documentation
---

# Providers' documentation

Halon reads the documentation of the providers you connect, such as Northflank, GitHub, Cloudflare or AWS, so it checks how a provider works instead of guessing. Firefight keeps a copy of each provider's documentation, refreshes it every day, and Halon searches it and cites the page each answer came from.

## What Halon does with it

When a question needs a provider's detail, such as which parameters a webhook takes, what an error code means or which API call exists, Halon searches that provider's documentation and reads the one or two sections that answer.

Halon searches the providers your workspace has connected. Ask about another provider by name and it searches that one too.

Each provider's skills, the short recipes Halon follows for common tasks, point at the pages that back them, and Halon opens those when it needs the detail.

When Halon uses something from a page, it names the page and links to it, so you can check the source yourself. In the dashboard the step shows the page it read.

## What it reads

The documentation comes from where each provider publishes it:

| Provider | What Halon reads |
|---|---|
| Northflank | Its product documentation, including workflows, triggers and webhooks, its own agent skill, and its full API reference |
| Cloudflare, Google Cloud, Azure, Fly.io, Kubernetes, GitLab, GitHub | Pages of their documentation on troubleshooting, deploys, rollbacks, security and errors |
| Azure DevOps | Microsoft's pages on troubleshooting pipelines, their logs, runs, stages, approvals, environments and deployment jobs, pull requests and branch policies |
| AWS, PlanetScale, Render, Neon, Supabase, ClickHouse, Upstash, PostHog, Mixpanel, New Relic, Honeycomb, Axiom, Logfire, SigNoz, Netlify, Vercel, Convex, DigitalOcean, Devin, Atlassian Jira | The guides each publishes for AI agents |
| Railway, Trigger.dev, Turso, PagerDuty, Grafana | Their documentation on deploys, runs, limits, on-call and their own tools |
| PostgreSQL | Guides to Postgres itself, on connections, locks, slow queries and vacuum |
| GitHub, GitLab, CircleCI, Netlify, Fly.io, Vercel, DigitalOcean, Trigger.dev, Kubernetes, Railway, AWS, Google Cloud, Azure | The reference of the API calls that read, which Halon checks before it reads anything [through a provider's own API](https://firefight.app/docs/ai/reading-your-platforms.md) |

## How it stays current

Firefight reads every provider's documentation again once a day, so a page the provider changed or removed reaches Halon by the next day.

## What Halon trusts it for

Documentation is reference material. Halon uses it to know how a provider works, never as instructions to follow. A page that tells the reader to do something does not make Halon do it, and Halon still acts only through the tools and permissions it has.

:::note
On a new Firefight installation the documentation is read in the background when Firefight first starts, which needs access to the internet. Until it has been read, or if the server cannot reach the internet, Halon works from its skills and your connected tools alone and tells you the documentation was not available.
:::