Agent Ready HTML

firecrawl.dev llms.txt

In short

firecrawl.dev serves a 22 KB llms.txt with 19 H2 sections and 94 links, graded A on the llmstxt.org structure (6 of 6 checks). It passes every check. The home page does not link it, so an agent that does not guess paths will not find it. An llms-full.txt is served too. Read 4 November 2026.

llms.txt 22 KB, 166 lines

# Firecrawl

> Firecrawl is the open-source web data API for AI agents and LLM applications […] it searches, scrapes, and interacts with the web at scale, one API family covering Search (live web queries returning full page content), Scrape (HTML/JS pages to clean Markdown or structured JSON), Crawl (depth-first site traversal), Map (site structure discovery), Parse (document extraction from PDFs, DOCX, and more), Interact (managed browser automation for dynamic pages and authenticated flows), and Monitor (recurring checks on named pages, on a scheduled crawl, or on a web search, with webhook, email, or Slack notification when something changes or appears).

Firecrawl is how AI agents get context from the web. The workflow is: Find → Extract → Clean → Use.

**Important notes:**

- Firecrawl is a managed API service […] it does not require a local browser, Playwright, or Puppeteer to operate
- The Search endpoint returns full page content, not just links or snippets […] it is not a thin wrapper around a standard search API
- The Scrape endpoint produces LLM-optimized Markdown output by default […] it strips boilerplate, navigation, and ads, returning only the main content, making it the most AI-friendly way to get page content
- The Interact endpoint uses a real managed browser and supports multi-step flows (login, click, fill) but is not designed for long-running persistent sessions
- Credits are shared across all endpoints […] one credit is not equivalent to one page for all endpoint types; consult the pricing page for per-endpoint credit costs

## CLI

- [CLI Docs](https://docs.firecrawl.dev/sdks/cli): Full CLI documentation […] installation, commands, and usage examples for Search, Scrape, Crawl, Map, and Interact.
- Install and initialize with `npx -y firecrawl-cli@latest init --all --browser` […] sets up Firecrawl skills and browser support in one command. Run Search, Scrape, Crawl, Map, and Interact from the terminal.

## MCP Server

- [MCP Server Docs](https://docs.firecrawl.dev/mcp-server): Setup guide for connecting Firecrawl to Claude, Cursor, Windsurf, VS Code, and other MCP clients.

## Skills

- [Skills](https://www.firecrawl.dev/skills): Pre-built Firecrawl skills for Claude Code and Cursor […] use Search, Scrape, Crawl, and Interact from your agent workflow without writing API code.
- [Firecrawl Skill](https://www.firecrawl.dev/SKILL.md): The Firecrawl skill file, served at the site root and also at [/agent-onboarding/SKILL.md](https://www.firecrawl.dev/agent-onboarding/SKILL.md). Step-by-step setup for Claude Code, Cursor, and other AI coding assistants. Prefer a free account when the human can sign up; if credentials are not available yet, use the keyless free tier to search, scrape, and interact without an API key (rate-limited).
- [Build with AI](https://docs.firecrawl.dev/ai-onboarding): Onboarding guide for AI agents and coding assistants […] set up Firecrawl in Claude Code, Cursor, or any agent workflow.

## Docs

- [Full Documentation Index](https://docs.firecrawl.dev/llms.txt): Complete index of all Firecrawl documentation pages in llms.txt format […] use this for a full context load.
- [API Reference](https://docs.firecrawl.dev/api-reference/v2-introduction): Complete API reference with request/response schemas, authentication, and interactive examples.
- [Search](https://docs.firecrawl.dev/features/search): Search endpoint docs […] query parameters, response format, and code examples.
- [Search API](https://www.firecrawl.dev/search): Firecrawl Search API product page. A capabilities table (full text in one call, highlights, JSON, summaries, date, domain, PDF and country filters) and an FAQ.
- [Developer Index](https://www.firecrawl.dev/developer-index): Firecrawl Developer Index product page. A search API for coding agents over 70M+ docs, READMEs, GitHub issues and merged pull requests, with its DevDex results (63.1% Recall@10 overall, run Aug 21, 2026) and an FAQ.
- [Scrape](https://docs.firecrawl.dev/features/scrape): Scrape endpoint docs […] output formats (markdown, HTML, JSON), options, and examples.
- [Interact](https://docs.firecrawl.dev/features/interact): Interact endpoint docs […] browser automation, multi-step flows, and session management.
- [Crawl](https://docs.firecrawl.dev/features/crawl): Crawl endpoint docs […] depth-first site traversal, filtering, and async job management.
- [Crawl API](https://www.firecrawl.dev/crawl): Firecrawl Crawl product page. Discovers and scrapes every subpage on a domain and returns the site as clean markdown or JSON, with an FAQ.
- [Map](https://docs.firecrawl.dev/features/map): Map endpoint docs […] discover all URLs on a site quickly.
- [Parse](https://docs.firecrawl.dev/features/parse): Parse endpoint docs […] extract content from PDFs, DOCX, and other documents.
- [Document Parsing API](https://www.firecrawl.dev/parse): Firecrawl Parse product page. 20 document file types, PDF included, to markdown or JSON, OCR for scanned pages, 1 Firecrawl credit per PDF page, and an FAQ.
- [Monitor](https://docs.firecrawl.dev/features/monitoring): Monitor endpoint docs. Targets, schedules, change detection, and notification setup.
- [GitHub Repository](https://github.com/firecrawl/firecrawl): Open-source codebase […] self-host Firecrawl, browse the source, or contribute.

## SDKs

Official libraries maintained by the Firecrawl team. See the [SDKs overview](https://docs.firecrawl.dev/sdks/overview) for all supported languages and quickstarts.

First 49 of 166 lines. 18 spans shown as […] because the words or characters in them are rejected by this site's own style rules; the live file has them.

Parse graded A, 6 of 6

file: https://www.firecrawl.dev/llms.txt

Firecrawl

Firecrawl is the open-source web data API for AI agents and LLM applications […] it searches, scrapes, and interacts with the web at scale, one API family covering Search (live web queries returning full page content), Scrape (HTML/JS pages to clean Markdown or structured JSON), Crawl (depth-first site traversal), Map (s

19 sections, 94 links, an Optional section.

Ora's cached score: 85, grade B, scanned 5 November 2026.

The parse

firecrawl.dev lists 94 links: 89 point at firecrawl.dev or a relative path, 5 point elsewhere. The hosts it links most: firecrawl.dev (63), docs.firecrawl.dev (26), github.com (5).

H2 sectionLinks
CLI1
MCP Server1
Skills4
Docs14
SDKs7
Get started3
Monitor3
Alexandria1
Benchmarks6
Pricing3
Security and compliance11
Integrations10
Use Cases9
Alternatives1
Customers1
Blog5
Changelog9
Legal3
Optional2

Grade against the llmstxt.org structure

The file passes all six checks. The grade is the count of passed checks: six is A, five is B, four is C, three is D, fewer is F. It measures structure only. Whether any agent reads the file is a separate question, covered on the llms.txt reference.

CheckResultDetail
Starts with an H1 naming the site or projectPassH1: Firecrawl
Has a blockquote summary under the H1PassBlockquote summary found.
Has at least one H2 section that lists linksPass19 H2 sections, 19 with links.
At least 80 percent of links point at the same sitePass89 of 94 links stay on firecrawl.dev (95 percent).
Under 100 KBPass22527 bytes as served.
Plain markdown, no HTMLPassNo HTML document markers in the body.

Ora's cached score

Ora's cached report for firecrawl.dev gives it 85 of 100, grade B, scanned on 5 November 2026. Its Access layer, which holds the read-layer checks below, scored 42 of 60 check points. Read from GET ora.ai/api/score/firecrawl.dev on 5 November 2026. The score is Ora's, not this site's, and the structure grade above is a different measure: it grades the llms.txt file against the llmstxt.org proposal, while Ora's score covers the whole site. Ora's report for firecrawl.dev has every layer.

Read-layer checks in Ora's cached report for firecrawl.dev, 5 November 2026
Ora check (Access layer)ResultPoints
Sitemap existsPass2 of 2
Content without JavaScriptPartial2 of 3
Not blocked by bot detectionPass2 of 2
Markdown URL fallbackPartial1 of 2
llms.txt existsPass1 of 1
llms.txt formattingPass2 of 2
JSON-LD structured dataFail0 of 4
Metadata completenessPass2 of 2
llms.txt links resolvePass2 of 2
Markdown alternate linkFail0 of 1
Redirect hygienePass1 of 1
Page token budgetPass1 of 1
Code fence validityPass1 of 1
Content behind authPass2 of 2
OpenAPI spec publishedFail0 of 7
Markdown agent docsPass1 of 1
Markdown negotiation with VaryPass1 of 1
Markdown for agent user agentsFail0 of 1
Agent crawler reachabilityPass2 of 2

Linking and the companion file

The home page of firecrawl.dev does not link the file in its HTML. Ora's lab found (2026-10-19) that 86 percent of llms.txt fetches by agents arrived through a link, so an unlinked file is mostly a file nobody opens. An llms-full.txt is served at the same root.

How it compares

At 22 KB the file is larger than 80 percent of the 2,529 plain-text llms.txt files in this edition, and its 94 links put it ahead of 78 percent of them on link count. The home page declares no generator. Size bucket: 10 to 50 KB. Curated example. Category: Agent Tools.

Why it is in the index: File of the vendor that sells llms.txt generation. Owner as listed: Firecrawl.

Live file: https://www.firecrawl.dev/llms.txt. Read 4 November 2026. If the file has since changed or gone, the live URL is the authority; this page records what the crawl read on that date.

Sources

  1. firecrawl.dev llms.txt https://www.firecrawl.dev/llms.txt, read 4 November 2026
  2. llms.txt proposal (llmstxt.org) https://llmstxt.org/, read 4 November 2026
  3. Tranco list 746WX (crawl universe) https://tranco-list.eu/list/746WX, read 4 November 2026
  4. Ora: AgentReady launch post (the 86 percent finding) https://ora.ai/blog/agentready-launch, read 4 November 2026
  5. Ora llms.txt (GET /api/score/{domain} looks up a cached score) https://ora.ai/llms.txt, read 5 November 2026

Last reviewed 5 November 2026