pmid:, pmcid:, and doi: references work the same way arxiv: ones do.
- Find papers by topic, method, benchmark, author, or category
- Inspect canonical paper metadata and source ids
- Read the passages in one paper that answer a specific question
- Expand from strong seed papers to related papers, citers, or references
To give your agent access to the Research Index, we strongly recommend using our CLI or MCP, combined with our dedicated research skill, which you can install with:
How this relates to /search
Firecrawl has two things named “research”, and they are not the same feature:
Use the Research Index when you are doing literature work: finding papers, reading them, and following citations. Use
categories: ["research"] when you want ordinary web pages that happen to live on academic domains.
Endpoints
Search papers
Search paper abstracts with a natural-language query. The response returns ranked papers with canonicalpaperId, preferred primaryId, source ids, title, abstract, score, and optional ranking signals.
authors: author substring filter; all filters must matchcategories: paper category filter, such ascs.LGfrom: inclusive created/updated lower bound,YYYY-MM-DDto: inclusive created/updated upper bound,YYYY-MM-DD
Biomedical example
Most of the index is life sciences, so clinical and molecular biology queries work the same way:primaryId in whichever namespace the source uses, so biomedical hits come back as pmid:<id>, pmcid:<id>, or doi:<doi>. Feed that value straight back into the inspect, read, and related endpoints below.
Inspect a paper
Use a canonicalpaperId or a source-specific primaryId. Accepted primaryId forms are arxiv:<id>, pmid:<id>, pmcid:<id>, and doi:<doi> — for example curl -s ".../v2/search/research/papers/pmid:<id>" for a PubMed record.
Read paper passages
Addquery to the same paper path to retrieve the top full-text passages for a question. This is useful for verifying whether a candidate paper actually contains a method, dataset, constraint, or result before you include it.
Find related papers
Expand from one or more seed papers through semantic expansion and rank the candidates against a natural-languageintent.
similar: co-citation and bibliographic-coupling neighborhoodciters: papers that cite the seedreferences: papers cited by the seed
Search GitHub history
Issues, merged pull requests, and repository READMEs now live in the Developer Index, which ranks them with the matched passages and adds curated documentation sources alongside them. UseGET or POST /search/developer, or /search with categories: ["developer"].
