Every hard regulatory question in drug development is really the same question: has an agency accepted this before, from whom, and on what evidence? This ranks the tools for answering it.
Guidance tells you what the agency says it wants. Precedent tells you what it has actually accepted. A guidance document describes an endpoint in general terms; the review of the drug approved on that endpoint three years ago tells you what data package satisfied a specific division, what the reviewers pushed back on, and what got negotiated.
That's why the questions that matter most sound like this: Why did the last twenty products in this class do X and none of them do Y? Has FDA ever accepted this surrogate endpoint in this population? What did the CRLs in this therapeutic area actually object to, and what fixed them? Has anything been approved despite missing its primary endpoint — and how? None of those have an answer in a guidance library. All of them have an answer in the record.
And underneath it sits the question nobody asks out loud: have we exhausted it? Not "did we find some precedent" but "is there something we haven't seen that a reviewer will raise, or that would have changed our approach if we'd known?"
The material is scattered across document types that were never designed to be read together:
Three properties make this genuinely hard to search. Most of it is scanned image PDF with no machine-readable text — a crawler and a keyword search both come back empty on documents that plainly contain the answer. The vocabulary doesn't match either: you don't know how the agency phrased your concept, so you can't enumerate the synonyms to search for. And the answer is almost never in one document; it's a pattern across thirty, which surfaces only once all thirty have been read.
Facts are from public materials as of August 2026, plus what regulatory teams tell us directly about how they actually do this work.
We score ourselves 2 of 4 on judgment deliberately: Rhizome shows you what the agency accepted, and what your program does with that is still your call.
Rhizome is a focused, AI regulatory coworker built for exactly this job: what has your regulator said and decided, and what does it mean for your program. Our agents can only state facts pulled from primary-source documents. Memory doesn't count as a source, and we benchmark them on that discipline. So the answer to "has FDA accepted this endpoint?" is assembled from the reviews themselves. A hard precedent question reads hundreds of documents, sometimes thousands, with up to 1,000 citations in a single answer, and each one opens to its exact passage inside the 500-page review.
The corpus is what makes exhaustiveness possible: >45 million documents across >75 health authority databases in >12 markets (as of August 2026 — this increases all the time), with every line indexed and every scanned image processed, because that's where the substance of a review package actually is. No hallucinations have been reported in 18 months — a track record, not a guarantee. There's a free tier and published pricing, and it connects into Claude, ChatGPT, or Copilot over MCP if that's where your team already works.
The right call when the hard part is judgment: a novel pathway, a division relationship, someone accountable in the room. But hours don't scale to exhaustive reading, so the wide scan becomes a billable line item or quietly doesn't happen. The strongest arrangement is a consultant making the call on top of research that was actually exhaustive.
Everything is public and every citation is real. But hunting patterns across twenty or thirty products by hand takes a week, so the scope gets cut to five, and the pattern you needed lived in the twenty-five you skipped.
Genuinely useful for orienting on a well-documented topic. But precedent research is where its structure bites hardest: it answers from memory plus a shallow web pass, the review packages are invisible to that pass, and its economics assume an answer in seconds. You get the famous precedent while the complete record stays buried, and the citations often don't survive being opened. Copilot compounds it by grounding in your own tenant when the whole point is the world outside it.
Excellent at what changed and what the current requirement is in a given market. But they hold curated summaries of policy, while the reviews and letters where decisions actually got recorded sit outside the library. Useful alongside, wrong instrument for this job.
Loading approval PDFs into an internal bot demos well. Then comes OCR for the scanned back catalog, refreshes across authorities, and an evaluation harness proving the agent didn't fall back on memory. Build AI where it differentiates you: a model predicting whether your candidate works is core IP, and reading the public record is something you can buy.