Firecrawl
Service domainWEB SCRAPING
Arcade OptimizedBYOCPro
Arcade.dev LLM tools for reading the web via Firecrawl
Author:Arcade
Version:
4.0.0Auth:No authentication required
12tools
12require secrets
Firecrawl Toolkit
Firecrawl is a web-reading service; this toolkit exposes its capabilities as LLM-callable Arcade tools for scraping, crawling, mapping, searching, and extracting structured data from the web.
Capabilities
- Single-page and multi-page reading: Scrape a known URL directly, or crawl an entire site to retrieve content from many pages, with async job management (status checks, partial data retrieval, cancellation) for long-running crawls.
- Site mapping: List all URLs on a website without fetching page content — useful for discovery before scraping or crawling.
- Structured data extraction: Pull specific fields (products, prices, contacts, etc.) from web sources using plain-language descriptions, with async job tracking for extractions that exceed the wait window.
- Web and specialized search: Search the open web (with optional inline page reading), developer documentation and repositories, GitHub issues, and scientific literature (PubMed, bioRxiv, medRxiv, arXiv) through purpose-specific tools.
Secrets
FIRECRAWL_API_KEY — The API key that authenticates all requests to the Firecrawl API. Obtain it by signing in to the Firecrawl dashboard, where you can create and manage API keys under your account. A free tier is available; higher-volume usage requires a paid plan. The key is passed with every request and must be kept confidential.
Configure secrets in Arcade at https://docs.arcade.dev/en/guides/create-tools/tool-basics/create-tool-secrets or directly via https://api.arcade.dev/dashboard/auth/secrets.
Available tools(12)
12 of 12 tools
Operations
Behavior
| Tool name | Description | Secrets | |
|---|---|---|---|
Stop a crawl that is still running.
Pages the crawl already collected stay available through GetCrawlData. | 1 | ||
Read many pages of one website and return each page's content.
A crawl that outruns wait_seconds keeps running: the result carries its
job_id, and GetCrawlStatus, GetCrawlData, and CancelCrawl take it from there. | 1 | ||
Collect structured records from the web from a plain-language description.
Use this when the answer is fields such as products, prices, or contacts.
Use ScrapeUrl or CrawlWebsite when the answer is the page text itself. An
extraction that outruns wait_seconds keeps running, and GetExtractStatus
takes its job_id. | 1 | ||
Read the pages a crawl has collected so far. | 1 | ||
Check how far a crawl has progressed, without fetching its pages. | 1 | ||
Collect the results of an extraction that is already running. | 1 | ||
List the URLs on a website, without reading the pages.
Use CrawlWebsite to read the content of many pages, or ScrapeUrl for one. | 1 | ||
Read one web page whose URL is already known and return its content.
Use Search instead when the URL is unknown, MapWebsite to list a site's
URLs, CrawlWebsite to read many pages of one site, and ExtractData to pull
structured fields rather than page text. | 1 | ||
Search the web and optionally read each result page in the same call.
Use this when no URL is known yet. Use SearchResearchPapers for scientific
literature and SearchDeveloperDocs for API and code documentation. | 1 | ||
Search developer documentation and repositories, quoting the text that matched.
Use this to answer a question about how a library or API works. Use Search
for the open web, and SearchGithubIssues to look only at issues. | 1 | ||
Search GitHub issues across indexed repositories.
Use SearchDeveloperDocs instead to search documentation, READMEs, and pull
requests alongside issues. | 1 | ||
Search published scientific papers and return their abstracts.
This reads a corpus of paper records drawn from PubMed, bioRxiv, medRxiv,
and arXiv. To find ordinary web pages that happen to sit on academic sites,
use Search narrowed to research instead. | 1 |
Last updated on