# Firecrawl Setup

Add Firecrawl credentials and its SDK to a project's environment.

- Repository: https://github.com/firecrawl/firecrawl (197658 stars)
- Category: DevOps
- License: ISC
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add firecrawl/firecrawl --skill firecrawl-build-onboarding -g -a claude-code -y`
Codex: `npx skills add firecrawl/firecrawl --skill firecrawl-build-onboarding -g -a codex -y`
Cursor: `npx skills add firecrawl/firecrawl --skill firecrawl-build-onboarding -g -a cursor -y`
Gemini CLI: `npx skills add firecrawl/firecrawl --skill firecrawl-build-onboarding -g -a gemini-cli -y`

## Description

Get Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Firecrawl Build Onboarding

Use this skill for the application-integration path from Firecrawl's onboarding flow.

## Install

If you haven't installed yet, one command sets up both the CLI tools
(for live web work) and the build skills (for app integration):

```bash
npx -y firecrawl-cli@latest init --all --browser
```

This installs the Firecrawl CLI, the CLI skills, and these build skills
together. It also opens browser auth so the human can sign in or create
an account. No separate `npx skills add` step is needed.

## Use This When

- a project needs `FIRECRAWL_API_KEY`
- the user wants Firecrawl wired into `.env`
- you are adding Firecrawl to an app for the first time
- you need to choose the first SDK or REST path

If the human still needs to sign up, sign in, or authorize access in the browser, use the auth flow reference in this skill.

If the project already uses [Stripe Projects](https://docs.firecrawl.dev/integrations/stripe-projects) (a `.projects/` directory, or `stripe projects status` succeeds), the key can come from there instead of the browser flow:

```bash
stripe projects add firecrawl/api --name firecrawl
stripe projects env --pull
```

`--name firecrawl` is what puts the key in `FIRECRAWL_API_KEY`; without it the CLI writes `FIRECRAWL_API_API_KEY`, which the SDKs do not read. Ignore the `FIRECRAWL_API_BASE_URL` the CLI also writes: the SDKs read `FIRECRAWL_API_URL`, and only for self-hosted deployments, so leave it unset for a hosted account. Paid plans are the human's call, since `stripe projects upgrade firecrawl` charges their card. The docs page carries the catalog and troubleshooting.

## Quick Start

If the user already has an API key, place it in `.env`:

```dotenv
FIRECRAWL_API_KEY=fc-...
```

If the project is self-hosted, also set:

```dotenv
FIRECRAWL_API_URL=https://your-firecrawl-instance.example.com
```

Then decide which integration path applies:

The rest: https://github.com/firecrawl/firecrawl/blob/HEAD/skills/firecrawl-build-onboarding/SKILL.md