Firecrawl Developer Index

Answer a developer question from the primary source: the issue where the bug was reported, the merged pull request that fixed it, the README or documentation page that states the contract. A blog post that describes a behaviour is a weaker answer than the passage that defines it, so reach for the index first and the open web second.

There is no fixed recipe. Read the question, decide what kind it is, and choose the approach below. A literal error string wants a different move than "how do I do X". Don't run machinery a question doesn't call for.

The tools, and what each is uniquely good at

• HTTP: GET|POST https://api.firecrawl.dev/v2/search/developer MCP: firecrawl_developer_search(query, k?, skills?) CLI: firecrawl developer <query> [--limit <n>] [--skills-only] Ranked results over the whole index. Each carries id (issue:owner/repo#123), type (doc | issue | pull_request | readme), url, title, and the matched passages in markdown, so tables and code blocks survive. The default first move for a developer question. It is the only surface that returns the passages, which is what lets you answer instead of pointing at a page. k / --limit is 1–100 and defaults to 10. skills="only" / --skills-only restricts the search to agent-skill files. Keyless; send Authorization: Bearer $FIRECRAWL_API_KEY for higher rate limits.