firecrawl-build-scrape

Use this when the application already has the URL and needs content from one page. Read the source-of-truth page for your project language before writing integration code: - 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 - Return markdown unless the feature truly needs another format. - Use onlyMainContent for article-like pages where nav and chrome add noise. - Add waits or other rendering options only when the page needs them. - knowledge ingestion from known URLs - enrichment from a company, product, or docs page - pricing, changelog, and documentation extraction - page-level quality checks or monitoring - 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 . - Keep the integration narrow: one feature, one URL, one extraction contract. - Treat /scrape as the default primitive for downstream LLM or indexing pipelines.