Firecrawl
Arcade.dev LLM tools for reading the web via Firecrawl
4.0.1Firecrawl is a web-reading service; this toolkit exposes its capabilities as Arcade tools so agents can scrape, crawl, search, and extract structured data from the web.
Capabilities
- Single-page and multi-page reading: Scrape a known URL for its full content, or crawl an entire site with configurable depth and page limits; long-running crawls return a
job_idfor async tracking. - Crawl management: Check crawl progress, retrieve collected pages so far, or cancel an active crawl by job ID without losing already-fetched content.
- Structured data extraction: Describe the fields you want (products, prices, contacts, etc.) in plain language and receive structured records; long-running extractions are also async via job ID.
- Web and specialized search: Search the open web (optionally scraping each result in the same call), developer docs and repositories (with matched-text quotes), GitHub issues across indexed repos, or a corpus of scientific papers from PubMed, bioRxiv, medRxiv, and arXiv.
- Site mapping: List all URLs on a site without fetching page content, useful for planning crawls or auditing structure.
Secrets
FIRECRAWL_API_KEY — Your Firecrawl API key, used to authenticate every request to the Firecrawl API. Obtain it by signing in to the Firecrawl dashboard, navigating to the API Keys section, and creating or copying an existing key. Free-tier accounts can generate a key immediately; higher-volume usage requires a paid plan. The key is passed with each tool call and is never exposed in results.
For guidance on storing secrets in Arcade, see the Arcade secrets docs. You can manage your secrets at https://api.arcade.dev/dashboard/auth/secrets.
Available tools(12)
| Tool name | Description | Secrets | |
|---|---|---|---|
Stop a crawl that is still running.
Pages the crawl already collected stay readable by its job id. | 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 for checking progress, reading the pages, or cancelling it later. | 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,
rather than the page text itself. An extraction that outruns wait_seconds
keeps running, and the result carries its job_id for collecting the results
later. | 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. | 1 | ||
Read one web page whose URL is already known and return its content.
It reads only the page at the given URL. It does not search the web, crawl
other pages of the site, or pull structured fields out of the page text. | 1 | ||
Search the web and optionally read each result page in the same call.
Use this when no URL is known yet. It searches the open web rather than a
corpus of scientific papers or indexed 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. It searches
indexed repositories, not the open web. | 1 | ||
Search GitHub issues across indexed repositories.
Only issues are searched; documentation, READMEs, and pull requests are not. | 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 |