Firecrawl Scrape Pages

Mode and routing

• run: one ordinary URL uses synchronous /scrape; multiple URLs use asynchronous /start-scrape. A nonempty actions, parsers, or waitFor, or a JSON/screenshot/audio/video/question/query format also selects async conservatively. Lightweight JSON can explicitly use --mode sync.
• --mode sync|async overrides automatic selection. Sync requires exactly one URL. start always submits async and returns immediately; run waits for async completion.
• Async uses urls (including for one URL); sync uses url. A batch shares all options and has one job ID. No silent splitting into multiple paid jobs.
• /start-scrape does not accept provider timeout. If auto mode selects async and the input includes timeout, remove it explicitly or choose sync; the helper rejects it instead of silently dropping it.

Examples

bash {baseDir}/scripts/firecrawl.sh run --url 'https://example.com' --output ./out/page.json
bash {baseDir}/scripts/firecrawl.sh run --url 'https://example.com' --url 'https://example.com/about'
bash {baseDir}/scripts/firecrawl.sh run --mode sync --url 'https://example.com/product' --json '{"formats":[{"type":"json","prompt":"Extract name and price","schema":{"type":"object","properties":{"name":{"type":"string"},"price":{"type":"number"}}}}]}'
bash {baseDir}/scripts/firecrawl.sh start --json @batch.json --idempotency-key my-batch-001

Authentication and execution