firecrawl

name	firecrawl
description	Scrape pages, crawl public sites, map URLs, and run JSON-schema extraction through managed or self-hosted Firecrawl.
user-invocable	true
requires	{"bins":["node"]}
credentials	[{"id":"firecrawl-api-key","kind":"api_key","required":false,"secret_ref":{"source":"store","id":"FIRECRAWL_API_KEY"},"scope":"api.firecrawl.dev","how_to_obtain":"Create a managed Firecrawl API key in the Firecrawl dashboard. Set `FIRECRAWL_API_KEY` through browser admin at the active `/admin/secrets` route; if browser admin is unavailable, use `/secret set FIRECRAWL_API_KEY \"<fc-api-key>\"` in browser `/chat` or TUI; local console fallback: `hybridclaw secret set FIRECRAWL_API_KEY \"<fc-api-key>\"`."},{"id":"firecrawl-self-host-api-key","kind":"api_key","required":false,"secret_ref":{"source":"store","id":"FIRECRAWL_SELF_HOST_API_KEY"},"scope":"self-hosted Firecrawl","how_to_obtain":"Set this only when your self-hosted Firecrawl instance has API authentication enabled. Set `FIRECRAWL_SELF_HOST_API_KEY` through browser admin at the active `/admin/secrets` route; if browser admin is unavailable, use `/secret set FIRECRAWL_SELF_HOST_API_KEY \"<self-host-api-key>\"` in browser `/chat` or TUI; local console fallback: `hybridclaw secret set FIRECRAWL_SELF_HOST_API_KEY \"<self-host-api-key>\"`."}]
metadata	{"hybridclaw":{"category":"research","short_description":"Firecrawl managed/self-host scrape, crawl, map, and extraction.","tags":["firecrawl","scrape","crawl","extraction","web"],"related_roadmap":["R53","R53.1","R53.2"],"issue":829,"sub_issues":[862,863],"stakes_tiers":{"green":"[Truncated]","amber":"[Truncated]"},"cost_measurement":{"system":"UsageTotals","sub_limit_key":"firecrawl"}}}

Firecrawl

Use this skill for unauthenticated public web ingestion when HTTP fetch and server-side parsing are enough. Firecrawl is the cheap path for public pages and docs. Use the browser skill instead when the task needs login, interaction, form filling, visual inspection, or client-side state. Do not use Firecrawl to bypass access controls.

Credential Rules

For managed mode, set or update the Firecrawl API key in this order:

1. Browser admin: open the active HybridClaw admin URL ending in /admin/secrets and set FIRECRAWL_API_KEY.
2. Browser /chat or TUI fallback: /secret set FIRECRAWL_API_KEY "<fc-api-key>".
3. Local console fallback:

hybridclaw secret set FIRECRAWL_API_KEY "<fc-api-key>"

For a self-hosted Firecrawl instance, set the gateway-reachable base URL in the runtime environment or pass it explicitly to the helper:

export FIRECRAWL_SELF_HOST_BASE_URL="http://firecrawl:3002"

The helper accepts base URLs with or without /v2 and normalizes them to the v2 API path. If your self-hosted Firecrawl deployment enables API authentication, set that token separately in the same order:

1. Browser admin: open the active HybridClaw admin URL ending in /admin/secrets and set FIRECRAWL_SELF_HOST_API_KEY.
2. Browser /chat or TUI fallback: /secret set FIRECRAWL_SELF_HOST_API_KEY "<self-host-api-key>".
3. Local console fallback:

hybridclaw secret set FIRECRAWL_SELF_HOST_API_KEY "<self-host-api-key>"

Use HTTPS for any self-host endpoint outside a trusted private network, especially when --self-host-auth is enabled; plain HTTP can expose bearer tokens on untrusted networks.

For live calls, run the colocated helper to build an http_request payload and pass only the emitted httpRequest object to the built-in http_request tool. The helper sets bearerSecretName: "FIRECRAWL_API_KEY" so the gateway injects the managed token server-side. In self-host mode, pass --self-host-auth only when the deployment requires a bearer token; the helper then uses . Do not use bash/curl for live Firecrawl calls when is available, and never ask the user to paste API keys into chat.