firecrawl-build-search

Integrate Firecrawl /search API into applications for query-driven web discovery.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/webdevarif/claude-skills --skill firecrawl-build-search-webdevarif
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: firecrawl-build-search
Source: https://github.com/webdevarif/claude-skills/tree/main/firecrawl-build-search
Command: npx skills add https://github.com/webdevarif/claude-skills --skill firecrawl-build-search-webdevarif

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Applications that start with a user query rather than a known URL need a way to discover relevant web sources before any extraction can happen. This Skill guides the integration of the Firecrawl /search endpoint so products can turn queries into shortlists of pages for downstream scraping or answer generation. ## Core Features & Use Cases - Query-to-URL Discovery: Convert a search query into a ranked list of candidate pages using the Firecrawl /search endpoint. - Selective Hydration: Optionally fetch full result content, with guidance on when to prefer snippets or URLs over full extraction to control cost and latency. - Escalation Paths: Clear rules for handing off to scraping or browser-interaction workflows when a URL is already known or a page requires clicks and form input. - Use Case: A research assistant feature receives a user question, searches the web for current sources, and produces a cited shortlist that a later /scrape step turns into extracted content. ## Quick Start Ask the agent to integrate Firecrawl /search into your app so a user query returns a shortlist of source URLs for later scraping.

Frequently Asked Questions about firecrawl-build-search

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add web search to my app with Firecrawl?

Use the Firecrawl /search endpoint to send a query and receive a ranked list of result pages. Set your FIRECRAWL_API_KEY, then follow the language-specific source-of-truth docs for Node, Python, Rust, Java, Elixir, or cURL before writing integration code.

When should I use Firecrawl search instead of scrape?

Use /search when your workflow starts with a query and you need to discover URLs first. If you already have the target URL, go directly to the /scrape endpoint instead, since search is meant for discovery and source selection.

Can Firecrawl search return full page content?

Yes, /search can optionally hydrate results with full content, but the guidance is to prefer selective follow-up extraction over broad hydration when cost or latency matters. Decide explicitly whether your product needs snippets, URLs, or full result content.

Does Firecrawl search work with self-hosted deployments?

Yes, you can point the integration at a self-hosted Firecrawl instance by setting the optional FIRECRAWL_API_URL environment variable. The hosted API only requires the FIRECRAWL_API_KEY.

What if a search result page needs clicks or form input?

Escalate to the firecrawl-build-interact workflow when a discovered page requires browser interaction such as clicks or form submission. Search handles discovery only; interaction is a separate step in the pipeline.