What you get
Evidence attached to every cell of a screening matrix. Not interactive search: a pipeline that walks tens of thousands of pairs, retrieves the literature for each, and produces a structured result you can rank and filter.Who it’s for
Computational biology and platform teams running systematic screens, and anyone whose “search” is really a batch job with a six-figure cell count.How Phylo runs it
Phylo is an AI-native IDE for biology built by researchers from Stanford. One internal team uses the Consensus API to screen roughly 20,000 targets across hundreds of diseases, pulling literature evidence for every target-disease pair.“It’s very robust, with almost zero errors. It gives you genuinely useful results, and it embeds into a high-throughput agentic workflow easily.” — Kexin Huang, Co-founder & CEO, PhyloLiterature is not a side feature of that product — it is underneath nearly everything it does:
“Even in analysis tasks, there’s literature research underneath. For single-cell annotation, you need to find marker genes. To compare a paper’s findings against your own dataset, you need literature. To brainstorm a hypothesis, to understand a mechanism of action for a particular drug and disease, all of this requires a large volume of literature. That’s why we spent so much time making sure our literature search was the highest quality.” — Kexin Huang, Co-founder & CEO, Phylo
Building the screen
1
Separate the template from the entity lists
One query template crossed with two entity lists is auditable and cheap to change. Hundreds of hand-written queries are neither.
2
Decide the evidence question per cell
“Is there any literature linking this target to this disease” and “is there strong human evidence” are different screens with different filters. Pick one and hold it constant, or your cells are not comparable.
3
Pace to the rate limit, not to your ambition
This is where batch pipelines fail. The ceiling is per user, per second — see rate limits. Build a bounded work queue with backoff and jitter before you scale the matrix, not after.
4
Cache on the full parameter set
Screens have enormous overlap — the same target appears against hundreds of diseases. Cache on every parameter with a short TTL and you cut a large fraction of the calls.
5
Score, don't just count
Paper count is a poor signal. Weight by study design, recency, and whether the evidence is human. A cell with one strong trial outranks a cell with forty in vitro papers.
6
Record the empty cells
A pair with no literature is a finding — it is either a genuine gap worth investigating or a terminology problem in your template. Distinguish them by spot-checking.
What to check before you trust it
- Validate the template on 50 cells first. A template that produces noise at cell 50 produces noise at cell 50,000, expensively.
- Watch for entity-name collisions. Short gene symbols and common disease words pull in unrelated literature. Spot-check the highest-volume cells — anomalously high counts usually mean an ambiguous name.
- Distinguish a plan cap from a real result. If responses report finding more than they returned, your matrix is measuring your ceiling, not the literature.
- Alert when a whole run returns nothing. Silence looks identical to a broken job.
Related
Answer one question with many parallel searches
The interactive counterpart to this batch pattern.
Track new papers across many topics on a schedule
Re-run a screen on a cadence and report only the delta.
Best practices
Exhaustive sweep, rate limits, and the five primitives.
All use cases
Browse the gallery by persona.