Back to Details

firecrawl-developer-index

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

firecrawl developer

firecrawl developer

Answer a developer question from the primary source: the issue, the merged pull request that fixed it, or the README/docs passage that states the contract.
从一手来源回答开发者问题：相关问题、修复该问题的已合并Pull Request，或说明契约的README/文档段落。

Quick start

快速开始

bash
mkdir -p .firecrawl
firecrawl developer "how do I configure retries" --limit 10 -o .firecrawl/developer.json --json
jq -r '.results[] | .id, .url, .passages[].text' .firecrawl/developer.json
Run 
firecrawl developer --help
for the full option list.
HTTP: 
GET|POST https://api.firecrawl.dev/v2/search/developer
. MCP: 
firecrawl_developer_search
. Each hit carries 
id
, 
url
, 
passages
. Kind is the 
id
prefix (
doc:
, 
issue:
, 
pull_request:
, 
readme:
). Hits do not carry a 
type
field.
Done when: the answer quotes a matched passage and cites its 
url
(fall back to 
url
when 
title
is absent), or you have moved to the open web because the index had nothing to say.
bash
mkdir -p .firecrawl
firecrawl developer "how do I configure retries" --limit 10 -o .firecrawl/developer.json --json
jq -r '.results[] | .id, .url, .passages[].text' .firecrawl/developer.json
运行 
firecrawl developer --help
获取完整选项列表。
HTTP接口：
GET|POST https://api.firecrawl.dev/v2/search/developer
。MCP命令：
firecrawl_developer_search
。每条结果包含
id
、
url
、
passages
。类型由
id
前缀标识（
doc:
、
issue:
、
pull_request:
、
readme:
）。结果不包含
type
字段。
完成条件： 答案引用匹配的段落并注明其
url
（当标题缺失时，回退使用
url
），或索引中无相关内容时转向公开网页搜索。

Tips

提示

  • Default first move is 
    firecrawl developer
    . Use 
    search --categories developer
    only when you are already running a web search and want developer hits in the same call (no passage control, no index filters).
  • Literal error or stack trace: search the string plus the library name. On HTTP, 
    types=["issue","pull_request"]
    . Strip paths, line numbers, and ids, then retry.
  • API contract: 
    readme
    and 
    doc
    are authoritative. A merged PR supersedes an issue report. Never answer from an opening report alone.
  • Scope last: search the whole index, then narrow with HTTP 
    types
    , 
    repos
    , or 
    sources
    . If a scoped search is empty, read the echoed 
    indexed
    flag before concluding the repo is missing.
  • Repository filters (
    language
    , 
    topic
    , 
    license
    , 
    min_stars
    , …) drop 
    doc
    results unless you also pass 
    sources
    . 
    types
    , 
    repos
    , 
    sources
    , 
    passages
    , and those repository filters are HTTP-only.
  • Comparison, opinion, news, or an unindexed project: 
    firecrawl search
    , then 
    firecrawl scrape
    .
  • 默认首选操作是
    firecrawl developer
    。仅当你已在进行网页搜索且希望在同一调用中获取开发者相关结果（无段落控制、无索引筛选）时，才使用
    search --categories developer
    。
  • 字面错误或堆栈跟踪：搜索该字符串加上库名称。在HTTP请求中，设置
    types=["issue","pull_request"]
    。移除路径、行号和ID后重试。
  • API契约：
    readme
    和
    doc
    是权威来源。已合并的PR优先级高于问题报告。切勿仅根据初始问题报告作答。
  • 最后再缩小范围：先搜索整个索引，再通过HTTP参数
    types
    、
    repos
    或
    sources
    缩小范围。如果限定范围的搜索结果为空，先查看返回的
    indexed
    标记，再判断仓库是否未被收录。
  • 仓库筛选器（
    language
    、
    topic
    、
    license
    、
    min_stars
    等）会排除
    doc
    结果，除非同时传入
    sources
    参数。
    types
    、
    repos
    、
    sources
    、
    passages
    以及这些仓库筛选器仅支持HTTP请求。
  • 如需进行对比、获取观点、新闻或查找未被索引的项目：使用
    firecrawl search
    ，然后调用
    firecrawl scrape
    。

See also

另请参阅

  • firecrawl-search — open web, or 
    search --categories developer
    in the same call
  • firecrawl-scrape — full page when a hit is right but you need all of it
  • firecrawl-research-index — papers, not this index
  • firecrawl-search — 公开网页搜索，或在同一调用中使用
    search --categories developer
  • firecrawl-scrape — 当找到相关结果但需要完整页面内容时使用
  • firecrawl-research-index — 用于搜索论文，而非本索引