Firecrawl Build Scrape
Use this when the application already has the URL and needs content from one page.
Use This When
- the feature starts from a known URL
- you need page content for retrieval, summarization, enrichment, or monitoring
- you want the default extraction primitive before considering
/interact
Default Recommendations
- Return
markdownunless the feature truly needs another format. - Use
onlyMainContentfor article-like pages where nav and chrome add noise. - Add waits or other rendering options only when the page needs them.
Common Product Patterns
- knowledge ingestion from known URLs
- enrichment from a company, product, or docs page
- pricing, changelog, and documentation extraction
- page-level quality checks or monitoring
Escalation Rules
- If you do not have the URL yet, start with firecrawl-build-search.
- If content requires clicks, typing, or multi-step navigation, escalate to firecrawl-build-interact.
Implementation Notes
- Keep the integration narrow: one feature, one URL, one extraction contract.
- Treat
/scrapeas the default primitive for downstream LLM or indexing pipelines. - Request richer formats only when the consumer needs them, such as links, screenshots, or branding data.
Docs (Source of Truth)
Read the source-of-truth page for your project language before writing integration code:
- Node / TypeScript: docs.firecrawl.dev/agent-source-of-truth/node
- Python: docs.firecrawl.dev/agent-source-of-truth/python
- Rust: docs.firecrawl.dev/agent-source-of-truth/rust
- Java: docs.firecrawl.dev/agent-source-of-truth/java
- Elixir: docs.firecrawl.dev/agent-source-of-truth/elixir
- cURL / REST: docs.firecrawl.dev/agent-source-of-truth/curl
