Firecrawl API Key

Firecrawl powers every skill’s grounded research path. Without it, skills still run — they just stay assumption-based. With it, every external claim can carry a citation.

1. Create a Firecrawl account

Go to firecrawl.dev and sign up. The signup flow lands you in the dashboard.

2. Generate an API key

In the Firecrawl dashboard:

Open API Keys in the left-hand nav.
Click Create API Key (or copy the default key if one already exists).
Give the key a recognizable name — e.g. solutioneer-local.
Copy the key. It starts with fc-.

You will not be able to see the full key again after leaving the page, so paste it into .env immediately.

3. Add the key to `.env`

In the repo root:

cp .env.example .env

Then set the key:

FIRECRAWL_API_KEY=fc-...

Solutioneer also respects .env.local and process.env, so you can keep the key out of .env if you prefer — whichever file you use, the key must be named exactly FIRECRAWL_API_KEY.

4. Verify

From the repo root:

npm run doctor

The doctor should report FIRECRAWL_API_KEY as present. If not, check that you are editing the right .env and that there is no trailing whitespace on the key.

What Firecrawl is used for

Each skill declares which Firecrawl modes it can use, via its manifest.json:

Skill	Modes
Account Intel Brief	`search`, `scrape`, `crawl`
Demo Scenario Builder	`search`, `scrape`, `interact`
Integration Fit Gap Analyzer	`search`, `map`, `crawl`, `scrape`, `interact`
POC Handoff Orchestrator	`search`, `scrape`

All Firecrawl calls go through repo-local wrappers under tools/firecrawl/ — Codex does not make raw Firecrawl requests.

Cost control

A few practical notes:

crawl and map are the most expensive modes. Expect the Integration Fit Gap Analyzer to consume the most credits.
search and scrape are cheap. Most Account Intel Briefs only need these two.
Codex deduplicates sources before citing. You will not see the same page cited multiple times within one run.