Research Preview
The mechanism between medicine and the plant.
The claim-safe drug-to-plant mechanism engine. Enter a medication and see the plants, fungi, and ethnobotanicals that share its mechanism — with evidence tier, traditional-use context, safety profile, drug-interaction warnings, and a citation on every result.
The reference layer the category doesn't have yet — for the clinicians who answer the question, the platforms that field it, and the people who ask it.
Who it's for
One question. Three people who need a trustworthy answer.
“What plants share mechanism with this medication?” is asked across the whole system — and answered well almost nowhere. Myto is the claim-safe reference layer for each side of it.
For clinicians
A rigorous starting point.
Look up any medication. See the plants that share its mechanism, filtered by evidence tier, with interaction warnings and citations — a claim-safe answer for the moment a patient raises the question.
Open the lookup →For platforms & brands
License the layer. Don't build it.
Telehealth, supplement & CPG, and clinical-software teams field this question at scale. Embed Myto's mechanism graph and claim-safe response template instead of carrying the compliance risk of building it yourself.
Talk to us about embedding Myto →For individuals
In previewUnderstand before you ask.
A cited, claim-safe place to understand the science before you talk to your clinician — never a place to decide what to take, and never a substitute for medical advice. A consumer edition is in preview.
Join the waitlist →The licensable layer
Platforms can't build this safely. So they license it.
Answering the plant-vs-medication question at scale means owning the claim-safety risk that comes with it — the language, the citations, the evidence grading, the disclaimers. That's a regulatory surface most teams can't safely build. Myto is the mechanism layer they can embed instead: one API, claim-safe by construction, cited to the source.
Telehealth
Answer the botanical question inside the visit, without putting a claim in a clinician's mouth.
Supplement & CPG
Educate buyers around your line in mechanism language that stays inside the compliance line.
Clinical software
The botanical layer your EHR / decision-support stack doesn't have — graded, cited, and ready to surface.
It does
- Map plants to specific molecular targets shared with a given drug
- Cite published research with evidence tiers (A–G)
- Surface drug-interaction warnings prominently
- Distinguish clinical evidence from traditional-use records
- Educate on what is — and isn't — known
It does not
- Recommend a plant instead of a medication
- Diagnose, treat, cure, or prevent any disease
- Replace clinical judgment
- Tell anyone what to take
- Suggest stopping or changing any prescription
A note on language
What you will not find here.
The words alternative to, replaces, and instead of appear nowhere on any result page. Every plant entry is framed in terms of shared mechanism, research that has investigated, or traditional-use records — the language of education, not prescription. This is not a stylistic choice; it is the foundation of the system's compliance posture and the basis on which it can be a genuinely useful tool for clinicians.