firecrawl-build-search

Use this when the application starts with a query, not a URL. Read the source-of-truth page for your project language before writing integration code: - the user asks a question and the product must discover sources first - the feature needs current web results - you want to turn a search query into a shortlist of pages for later scraping - Use /search first when URL discovery is part of the product behavior. - Keep search and extraction conceptually separate unless scraping search results is clearly required. - Prefer selective follow-up extraction over broad hydration when cost or latency matters. - answer generation with cited sources - company, competitor, or topic discovery - research workflows that produce a shortlist before deeper extraction - query-to-URL pipelines for later /scrape or /interact - If you already have the URL, use firecrawl-build-scrape . - If the result page then requires clicks or form interaction, escalate to firecrawl-build-interact . - Treat /search as discovery, ranking, and source selection. - Be explicit about whether the product needs snippets, URLs, or full result content.