| name | firecrawl-build-scrape |
| description | Integrate Firecrawl `/scrape` into product code for single-page extraction. Use when an app already has a URL and needs markdown, HTML, links, screenshots, metadata, or structured page output. Prefer this skill over broader crawl patterns when the feature is page-level. |
| license | ISC |
| metadata | {"author":"firecrawl","version":"0.1.0","homepage":"https://www.firecrawl.dev","source":"https://github.com/firecrawl/skills"} |
| inputs | [{"name":"FIRECRAWL_API_KEY","description":"Firecrawl API key for hosted Firecrawl requests.","required":true},{"name":"FIRECRAWL_API_URL","description":"Optional base URL for self-hosted Firecrawl deployments.","required":false}] |
Firecrawl Build Scrape
Use this when the application already has the URL and needs content from one page.
Use This When
- 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
Default Recommendations
- 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.
Common Product Patterns
- knowledge ingestion from known URLs
- enrichment from a company, product, or docs page
- pricing, changelog, and documentation extraction
- page-level quality checks or monitoring
Escalation Rules
Implementation Notes
- Keep the integration narrow: one feature, one URL, one extraction contract.
- Treat
/scrape as the default primitive for downstream LLM or indexing pipelines.
- Request richer formats only when the consumer needs them, such as links, screenshots, or branding data.
Docs (Source of Truth)
Read the source-of-truth page for your project language before writing integration code:
See Also
