Molecule's AI assistant for the DeSci ecosystem, connected to live project data, market information, and a standalone project evaluation framework.

When we first introduced MIRA, it was a working assistant with a clear job: help people navigate the Molecule Product suite without having to hunt through documentation, data rooms, and market dashboards. Since then, the stack has grown. MIRA now pulls from a wider set of live tools, handles ecosystem-level queries alongside project-specific ones, and drives a new evaluation framework built to answer the question every investor and science team eventually asks: is this project actually ready for what comes next?
MIRA is a real-time system that works in sync with our flagship offering, Molecule Labs. It operates across two core domains, assisting public queries and performing detailed project analyses on the scientific content in Molecule Labs. It draws directly from Molecule Labs' project data, market information, and documentation so responses are useful and specific rather than generalized.
Ask MIRA about any individual Intellectual Property Token, and it pulls together live data from Molecule Lab’s Data Rooms, price, market data, what’s happened in the past month, and recent team activity.
Ask what’s live on Molecule right now and MIRA returns every tracked token with current prices, liquidity, and holder counts. Useful for comparisons or for getting a quick sense of where things stand across the protocol.
MIRA can tell you what has actually happened in a Molecule Labs project’s data room recently: new files, announcements, team updates, without anyone having to go look manually.
How do IP-NFTs work? What is Proof of Invention? What is DeSci? MIRA can answer these from vetted Molecule’s own documentation rather than pulling from generic web results.
When a user is ready to purchase, MIRA surfaces a direct link to the right page rather than making them find it themselves.
About the author

BSc(Hons) in Biochemistry and Materials Science. A communicator working at the intersection of biotechnology and web3.
Separate from everything above, we’ve built a standalone tool that reads a project’s data room files and answers a question that funders and science teams both care about: where is this project actually at, and what needs to happen next?
This will be displayed on project pages as a ‘Technology Readiness Score’ (TRL); a system invented by NASA and now widely applied to technological inventions. Projects have the opportunity to improve their scores by uploading relevant documentation.
It works as a four-step process. Each step builds on the previous one, and you can run the whole thing in a single session once the relevant documents are available. View the GitHub repository.
A quick read of the project that places it at the right level of research maturity: early idea, early evidence, or approaching clinical readiness, based on what the documents actually show, not how the team describes it. This takes about five to ten minutes and sets the frame for everything that follows.
Output: TRL 1, 2, or 3 classification
| TRL Rating | Rationale |
|---|---|
| Pre-TRL | The idea exists on paper and the scientific rationale is there, but no experimental work has been done yet. In the arena of pure scientific research with no lens towards developing certain technology. |
| TRL 1 | Basic research. The science itself may be identical to what existed at pre-TRL, but the framing has shifted; how might this science underpin the development of a piece of technology? |
| TRL 2 | Applied research. There is experimental work underway or early data in hand. The concept has been tested enough to know whether it's worth pursuing, but it hasn't been validated at scale. |
| TRL 3 | Proof of concept. The science has been demonstrated in a controlled setting. The team is moving toward clinical or commercial development and has enough evidence to support that transition. |
This is where the framework does most of its real work. Once a project has been placed at the right TRL, it gets scored against a set of criteria matched to that stage, and each criterion carries a weight that reflects how much it actually matters at that point in a project's life. The weights are not uniform - what separates a strong early-stage project from a weak one is different from what separates a strong late-stage project from a weak one, so the scoring has to reflect that.
Output: Score (0–5) with a breakdown by criterion
| Criterion | Weighting |
|---|---|
| Relevance of Therapeutic Mechanism of Action | 45% |
| Utility of Candidates | 20% |
| Intellectual Property Position | 15% |
| Prospects for Safety | 15% |
| Therapeutic Optionality | 5% |
The rationale behind these weights is that at the early feasibility stage, the single most important question is whether the mechanism actually works in a lab, which is why therapeutic relevance carries 45%. Hence, a project can have a compelling IP strategy and a wide range of potential indications, but none of that matters if the experimental data doesn't support the underlying hypothesis!
Utility of candidates sits at 20% because identifying specific molecular entities with reproducible activity becomes meaningful at this stage, although it is still secondary to whether the mechanism holds up.
IP position and safety are both weighted at 15%, reflecting that they become consequential by the time a project reaches TRL 2, without yet being decisive.
Therapeutic optionality is deliberately held at 5%, because multi-indication potential is largely speculative this early and over-weighting it would reward storytelling over evidence.
The score maps to a clear recommendation: move forward, hold and reassess, change direction, or stop, directed at potential funders and project evaluators. Each outcome comes with a written rationale grounded in the scoring from Step 2, so the decision has something concrete behind it rather than being a gut call.
Output: Promote / Supplement / Pivot / Pause + written rationale
| Recommendation | Rationale |
|---|---|
| Promote | The project scores well across key criteria and is ready to move forward, either to the next TRL stage, a funding round, or a formal development programme. |
| Supplement | The science is sound but something is blocking progress, for example missing data, an unresolved IP question, a capability gap on the team, or a regulatory uncertainty. The project should address those specific issues before moving forward. |
| Pivot | The underlying science or asset has merit, but the current approach, indication, or market thesis isn't working. The recommendation is to reframe the direction (different target, different application, different partner, etc) rather than push harder on what isn't working. |
| Pause | The project has fundamental weaknesses across multiple criteria that can't be fixed with more time or money. The recommendation is to stop and reallocate resources elsewhere. |
When a team needs more than a recommendation, this step produces a practical advancement plan built around the criteria where the project scored lowest.
It covers: the specific experiments or milestones needed to reach the next TRL level, what resources and expertise are required, rough timelines, the biggest risks and how to mitigate them, and suggested partners or collaborators where relevant. If projects upload the relevant data, their TRL score improves.
The output is structured so it can go directly into a grant application, an investor update, or the team's internal planning.
Output: Action plan with tasks, resources, timelines, and risks
MIRA can be connected to any Claude project, which means everyone working in that project gets access to all the live tools above without any extra setup per conversation. Setup instructions and the current configuration are in the mira-knowledge repository.
MIRA is live and ready to use. Head to molecule.xyz to ask it about any project in the ecosystem, explore tokens by research area, or get a full briefing on a specific IPT. For project teams, uploading documentation to your data room is the fastest way to improve your TRL score and unlock the full evaluation stack.
These are the tools available through the MIRA server today. Each one is a specific thing MIRA knows how to do - the AI figures out on its own which one to use based on what you ask.
| Tool | What it does |
|---|---|
| molecule-knowledge-search | Searches across Molecule’s documentation, blog posts, and DeSci.Codes to answer questions about how the protocol works, what IP-NFTs and IPTs are, how Proof of Invention functions, and what’s happening in the broader ecosystem. Good for anything conceptual or explanatory. |
| molecule-get-ipts | Pulls a full list of all IPTs from the Molecule ecosystem, including prices, market caps, how many people hold each token, and liquidity across different chains. A useful starting point when you want to explore what’s out there or get an overview of the ecosystem’s current state. |
| molecule-get-all-tokens | Does the same as above but casts a wider net, returning IPTs alongside other DeSci tokens tracked by the protocol. Useful for exploring available IPTs or summarizing Molecule ecosystem statistics. |
| molecule-get-ipt-categories | Will let you browse tokens by research area (longevity, fertility, brain health, and so on) with market data for each. |
| molecule-get-ipt-summary | Pulls everything about a single project into one response: project updates, non-confidential data stored in Molecule Labs, price, market data, what’s happened over the past month, and recent activity from the team. It comes out formatted and ready to read or share. The right tool when someone wants a full picture of a project without asking multiple questions. |
| molecule-get-project-activity | Shows project updates only: new updates, files added to the Molecule Labs Data Room, updates from the team. You give it the project’s token symbol (like VITA-RNA or VITA-FAST) and it returns a timeline of recent activity. |