.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: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 or the agent onboarding skill.
The resource lives in a Firecrawl account you own. Manage usage, keys, and billing in the Firecrawl dashboard, 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: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:
Next steps
Scrape docs
Convert webpages into Markdown, JSON, screenshots, and more
Search docs
Search the web and get page content from results
Agent onboarding
Auth, CLI, skills, and MCP after you have a key
Stripe Projects docs
CLI reference, environments, and billing

