Research Preview
iOS app in developmentThe mechanism between medicine and the plant.
Enter metformin. Berberine surfaces at AMPK — the same molecular target the drug acts on — with the human trials that studied it and a citation you can open. Enter an SSRI, and St John's Wort appears with the interaction warning. That's the whole idea: the shared mechanism between a medication and a plant, shown with its evidence.
Every result carries an evidence tier and a source citation. Myto teaches, compares, and cites — it never makes the decision. That belongs to the patient and their licensed provider. It is not a substitute for medical advice.
Who it's for
One question. Three people who need a trustworthy answer.
“Can I take this plant with my medication?” gets asked across the whole system — in exam rooms, in support tickets, at kitchen tables — and answered well almost nowhere. Myto is the cited, claim-safe reference for every 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.
For clinicians →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.
For platforms & brands →For individuals
Understand 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. Free to start; no NPI, no card.
For individuals →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.