Firecrawl
Service domainWEB SCRAPING
Arcade OptimizedBYOCPro
Arcade.dev LLM tools for reading the web via Firecrawl
Author:Arcade
Version:
4.0.1Auth:No authentication required
12tools
12require secrets
Firecrawl toolkit lets Arcade agents read, crawl, scrape, and extract structured data from the web via the Firecrawl API. No OAuth flow is required — access is controlled entirely by an API key.
Capabilities
- Single-page and multi-page scraping: Scrape a known URL directly, or crawl an entire site with configurable depth; long-running crawls return a
job_idfor async management. - Crawl lifecycle management: Check crawl progress, retrieve collected pages, or cancel a running crawl by its job ID.
- Site mapping: Enumerate all URLs on a site without fetching page content.
- Structured data extraction: Describe desired fields in plain language (products, prices, contacts, etc.) and extract them as structured records; supports async via
job_id. - Web and specialised search: Search the open web (with optional inline page reading), indexed developer docs and repositories, GitHub issues, and a corpus of scientific papers (PubMed, bioRxiv, medRxiv, arXiv).
Secrets
FIRECRAWL_API_KEY— An API key issued by Firecrawl that authenticates every request to the Firecrawl API. To obtain one, create an account at firecrawl.dev, then navigate to the API Keys section of your dashboard and generate a new key. Free-tier keys are available; higher-volume or production usage requires a paid plan. Copy the key immediately after creation — it is not shown again. Register the key as a secret in Arcade following the guidance at https://docs.arcade.dev/en/guides/create-tools/tool-basics/create-tool-secrets (you can also manage secrets directly in the Arcade dashboard at 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 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 |
Last updated on