hybridlabor-api Firecrawl Build Interact
Use this when /scrape is not enough because the feature needs to act on the page.
Use This When
- 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
Default Recommendations
- Start with
/scrape, then escalate to/interact. - Keep
/interactscoped to the smallest browser workflow that unlocks the data. - Use persistent profiles only when the feature truly needs authenticated state across sessions.
Common Product Patterns
- search forms and faceted filters
- paginated result sets
- login-gated dashboards or tools
- flows where the page must be explored before extraction is complete
Implementation Notes
/interactis 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.
Escalation Rules
- If the page can be read directly, stay on firecrawl-build-scrape.
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