firecrawl-build-interact

Use this when /scrape is not enough because the feature needs to act on the page. Read the source-of-truth page for your project language before writing integration code: - content appears only after clicks, typing, or navigation - the feature needs forms, pagination, filters, or multi-step flows - the product must stay in the same browser context after scraping - Start with /scrape , then escalate to /interact . - Keep /interact scoped to the smallest browser workflow that unlocks the data. - Use persistent profiles only when the feature truly needs authenticated state across sessions. - search forms and faceted filters - paginated result sets - login-gated dashboards or tools - flows where the page must be explored before extraction is complete - /interact is the right tool when the page must be manipulated, not just read. - Keep prompts or action code specific to the product flow. - If the use case is fully open-ended browser automation, evaluate whether a browser sandbox is a better product fit. - If the page can be read directly, stay on firecrawl-build-scrape .