feat(integrations): add support for Firecrawl

[JuampiHernandez]

Hey, I'm Juampi from the Firecrawl team. Thanks for making it this easy to add a new API. This PR adds Firecrawl as an API_KEY provider.

Describe your changes

Adds Firecrawl (https://www.firecrawl.dev), an API to search, scrape, and interact with the web that returns clean Markdown and structured data for AI systems.

• packages/providers/providers.yaml: firecrawl entry. Bearer auth against https://api.firecrawl.dev (no version in the base URL); verification calls GET /v2/team/queue-status, a cheap authenticated read that used no credits in my tests, with GET /v2/team/credit-usage as a fallback. The key pattern accepts current fc- keys and older UUID-format keys, which the API still accepts. Categories: dev-tools, analytics.
• docs/api-integrations/firecrawl.mdx and docs/api-integrations/firecrawl/connect.mdx: integration page (first request is POST /v2/search through the proxy) and connect guide (the key is under API Keys in the Firecrawl dashboard), with form.png.
• docs/docs.json: nav entry after finta.
• docs/api-catalog.txt, docs/llms.txt, docs/llms-full.txt: catalog row and provider count, generated with npm run docs:generate:llms.
• docs/snippets/generated/firecrawl/: generated with scripts/docs-gen-snippets.ts.
• packages/webapp/public/images/template-logos/firecrawl.svg: logo.

Public API reference: https://docs.firecrawl.dev/api-reference/introduction

Issue ticket number and link

n/a

Testing instructions

npx tsx scripts/validation/providers/validate.ts: all providers valid. mintlify broken-links from docs/: no broken links.

Verified end to end locally with docker compose up:

• Integrations -> Configure New Integration -> Firecrawl, then Connections -> Add Test Connection -> Firecrawl. The Connect UI renders the form with logo, key field, masked placeholder and connect guide link.
• An invalid key (fc-000...) is rejected by the verification call with connection_test_failed. A valid key creates the connection, in both the fc- and the older UUID format.
• POST /proxy/v2/search with {"query": "firecrawl", "limit": 3} returns 200 with 3 web results, and the Node snippet from the docs page (nango.post to /v2/search) returns the same.
• GET /proxy/v2/team/queue-status returns 200.

Both docs pages checked in mintlify dev.

[cubic-dev-ai]

1 issue found across 11 files

Confidence score: 4/5

• In docs/api-integrations/firecrawl/connect.mdx, implying all valid keys use the fc- prefix could lead existing customers with valid UUID-format legacy keys to regenerate them unnecessarily; clarify that only newly generated keys use the prefix.

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="docs/api-integrations/firecrawl/connect.mdx">

<violation number="1" location="docs/api-integrations/firecrawl/connect.mdx:22">
P2: This excludes the UUID-format legacy keys the provider accepts, so existing customers may regenerate valid keys unnecessarily. Clarify that only newly generated keys start with `fc-` and legacy keys may use UUID format.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

P2: This excludes the UUID-format legacy keys the provider accepts, so existing customers may regenerate valid keys unnecessarily. Clarify that only newly generated keys start with fc- and legacy keys may use UUID format.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At docs/api-integrations/firecrawl/connect.mdx, line 22:

<comment>This excludes the UUID-format legacy keys the provider accepts, so existing customers may regenerate valid keys unnecessarily. Clarify that only newly generated keys start with `fc-` and legacy keys may use UUID format.</comment>

<file context>
@@ -0,0 +1,32 @@
+1. Log in to the [Firecrawl dashboard](https://www.firecrawl.dev/signin?utm_source=nango&utm_medium=integration&redirect=%2Fapp%2Fapi-keys).
+2. Navigate to **API Keys**.
+3. Copy an existing key, or click **Create API Key** to generate a new one.
+4. Your API key starts with `fc-`.
+
+#### Step 2: Enter credentials in the Connect UI
</file context>

Suggested change

	4. Your API key starts with `fc-`.
	4. New API keys start with `fc-`; legacy keys may use UUID format.