diff --git a/docs.json b/docs.json
index c75eecbfe..4bc1eab98 100755
--- a/docs.json
+++ b/docs.json
@@ -327,6 +327,7 @@
                           "integrations/hermes",
                           "integrations/replit",
                           "integrations/lovable",
+                          "integrations/stripe-projects",
                           "integrations/langchain",
                           "integrations/llamaindex",
                           "integrations/crewai",
diff --git a/images/integrations/stripe.svg b/images/integrations/stripe.svg
new file mode 100644
index 000000000..48272a2c5
--- /dev/null
+++ b/images/integrations/stripe.svg
@@ -0,0 +1 @@
+<svg fill="#635BFF" role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><title>Stripe</title><path d="M13.976 9.15c-2.172-.806-3.356-1.426-3.356-2.409 0-.831.683-1.305 1.901-1.305 2.227 0 4.515.858 6.09 1.631l.89-5.494C18.252.975 15.697 0 12.165 0 9.667 0 7.589.654 6.104 1.872 4.56 3.147 3.757 4.992 3.757 7.218c0 4.039 2.467 5.76 6.476 7.219 2.585.92 3.445 1.574 3.445 2.583 0 .98-.84 1.545-2.354 1.545-1.875 0-4.965-.921-6.99-2.109l-.9 5.555C5.175 22.99 8.385 24 11.714 24c2.641 0 4.843-.624 6.328-1.813 1.664-1.305 2.525-3.236 2.525-5.732 0-4.128-2.524-5.851-6.594-7.305h.003z"/></svg>
\ No newline at end of file
diff --git a/integrations.mdx b/integrations.mdx
index 7704864da..590caa51a 100644
--- a/integrations.mdx
+++ b/integrations.mdx
@@ -199,6 +199,21 @@ Connect Firecrawl once, then build on live web data from the platform you deploy
   >
     Add Firecrawl to Vercel projects with automatic API key setup
   </Card>
+  <Card
+    title="Stripe Projects"
+    icon={
+      <img
+        src="/images/integrations/stripe.svg"
+        alt="Stripe"
+        width="24"
+        height="24"
+        style={{ objectFit: "contain" }}
+      />
+    }
+    href="/integrations/stripe-projects"
+  >
+    Provision Firecrawl from the Stripe Projects CLI with automatic API key setup
+  </Card>
 </CardGroup>
 
 ## Agent frameworks
diff --git a/integrations/stripe-projects.mdx b/integrations/stripe-projects.mdx
new file mode 100644
index 000000000..1378228ba
--- /dev/null
+++ b/integrations/stripe-projects.mdx
@@ -0,0 +1,65 @@
+---
+title: "Stripe Projects"
+description: "Provision Firecrawl from the Stripe Projects CLI with stripe projects add firecrawl/api. Credentials sync to .env."
+og:title: "Stripe Projects Integration | Firecrawl"
+og:description: "Provision Firecrawl from the Stripe Projects CLI. One command creates a Firecrawl account and syncs credentials into your project."
+---
+
+Firecrawl is a [Stripe Projects](https://projects.dev/) provider. [Stripe Projects](https://docs.stripe.com/projects) provisions third-party services from the terminal and syncs credentials to `.env`.
+
+Use this guide when you want Firecrawl credentials through Stripe Projects instead of the dashboard or CLI browser auth flow.
+
+## Quickstart
+
+Install the Projects plugin, create a project, add Firecrawl, and pull credentials:
+
+```bash
+stripe plugin install projects
+stripe projects init
+stripe projects add firecrawl/api
+stripe projects env --pull
+```
+
+Install the Stripe CLI first if you do not have it: [Stripe CLI install](https://docs.stripe.com/stripe-cli/install).
+
+`stripe projects add firecrawl/api` is the catalog slug for Firecrawl. Confirm with `stripe projects catalog firecrawl` if needed.
+
+`add` associates a Firecrawl account (or creates one), provisions the resource, and syncs credentials to `.env`. `env --pull` writes the active environment’s credentials to the configured output file (`.env` by default). List variable names with `stripe projects env`.
+
+Firecrawl SDKs, the CLI, and MCP read `FIRECRAWL_API_KEY`. After provisioning, continue with any [quickstart](/introduction) or the [agent onboarding skill](https://www.firecrawl.dev/agent-onboarding/SKILL.md).
+
+The resource lives in a Firecrawl account you own. Manage usage, keys, and billing in the [Firecrawl dashboard](https://www.firecrawl.dev/app), or open it with `stripe projects open firecrawl`.
+
+## Link an existing Firecrawl account
+
+Associate an existing Firecrawl account without provisioning first. This is the recommended first step in agent-driven workflows:
+
+```bash
+stripe projects link firecrawl
+stripe projects add firecrawl/api
+```
+
+## Provision from your coding agent
+
+`stripe projects init` writes Stripe Projects agent skills into the project directory. You can let the agent run the same CLI flow:
+
+```
+Use Stripe Projects to add Firecrawl and wire up the API key.
+```
+
+## Next steps
+
+<CardGroup cols={2}>
+  <Card title="Scrape docs" icon="file-lines" href="/features/scrape">
+    Convert webpages into Markdown, JSON, screenshots, and more
+  </Card>
+  <Card title="Search docs" icon="magnifying-glass" href="/features/search">
+    Search the web and get page content from results
+  </Card>
+  <Card title="Agent onboarding" icon="robot" href="https://www.firecrawl.dev/agent-onboarding/SKILL.md">
+    Auth, CLI, skills, and MCP after you have a key
+  </Card>
+  <Card title="Stripe Projects docs" icon="book" href="https://docs.stripe.com/projects">
+    CLI reference, environments, and billing
+  </Card>
+</CardGroup>