What problem does it solve? Getting Firecrawl wired into an application requires obtaining an API key, storing it correctly in environment configuration, and choosing the right SDK, which involves several manual steps that are easy to get wrong. ## Core Features & Use Cases - Browser-Based Auth Flow: Guides the user through a PKCE-style browser authorization flow to obtain a FIRECRAWL_API_KEY without manual dashboard copy-paste. - Environment Configuration: Shows how to place FIRECRAWL_API_KEY and optional FIRECRAWL_API_URL (for self-hosted deployments) into .env files safely. - SDK Selection and Installation: Provides install commands for the JavaScript/TypeScript (@mendable/firecrawl-js) and Python (firecrawl-py) SDKs, plus links to per-language source-of-truth docs. - Use Case: A developer starting a new Node.js project that needs web scraping runs the auth flow, saves the key to .env, installs the SDK, and runs a smoke test confirming one real Firecrawl request succeeds. ## Quick Start Ask the agent to set up Firecrawl in this project by obtaining an API key, adding it to the .env file, and installing the appropriate SDK for the project language.