Loading...
Loading...
Loading interactive ATP molecule.
To see a protein the way you mean it, you write PyMOL. To dock a ligand, you provision a box, install Vina, prep the receptor by hand. To screen a library, you babysit a queue. The tools are three decades deep — and three decades hard.
What if you could just say it?
One instruction. The director loads the structure, runs the BLAST, finds the pocket, docks the ligand, and renders the movie — and shows every step it took.
Load 1CRN and colour it by hydrophobicity. Find its closest homologs with BLAST and colour by conservation. Detect pockets, dock ibuprofen into the top one, run a short MD, then render a publication movie.
Illustrative replay. Every step maps to a real director tool. Visualisation and in-browser movies are available today; BLAST, pockets, docking and molecular dynamics are rolling out in pilot as compute lanes come online.
Not a suite of apps to stitch together — a single conversation that carries you from a raw structure to a shareable result.
Same result. On the left, the way it works today. On the right, the way it works here.
# 1. figure, in PyMOL
fetch 1crn, async=0
hide everything; show cartoon
set_color hydro, [0.2,0.6,0.9]
spectrum b, blue_white_red
# 2. homologs, on the CLI
blastp -query 1crn.fasta -db pdbaa \
-outfmt 6 -out hits.tsv
# 3. prep + dock, on a box you manage
prepare_receptor -r 1crn.pdb -o 1crn.pdbqt
fpocket -f 1crn.pdb
vina --receptor 1crn.pdbqt --ligand ibu.pdbqt \
--center_x 8 --center_y 6 --center_z 12 \
--size_x 20 --size_y 20 --size_z 20 \
--exhaustiveness 16“Load 1CRN, colour by hydrophobicity, BLAST for homologs, find pockets, and dock ibuprofen into the top one.”
One thread. No installs, no receptor prep, no grid-box guessing, no cluster. The director does the work and shows you exactly what it ran.
An AI you can trust with your science is one you can check. Every result is an artifact you can inspect, export, re-run, and share.
From a first look at a fold to ranking a ligand library — the same chat, different intent.
The same director that drives the app is a versioned REST API and an MCP server. Call it from your pipeline, a notebook, or an AI agent: natural language in; structured ViewerOps, costed job proposals, and results streamed back.
curl https://moleculestud.io/api/v1/molecular/director \
-H "Authorization: Bearer $MOLECULE_STUDIO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"prompt": "Load 1CRN, find pockets, dock ibuprofen into the top one",
"headless": true
}'
# Streams the director's ViewerOps, job proposals, and results over SSE.The same data-protection posture we’d want as scientists: encrypted, access-scoped, and independently audited.
Use one credit balance for AI direction, molecular rendering, inference, and simulation. Every expensive action is estimated before it runs.
Estimate every paid action before it runs and spend only on the work you use.
A predictable monthly allowance with better rates when you need more.
Negotiated terms for organisations with security, procurement, or deployment requirements.
What it does, what’s live vs pilot, how we keep the science honest, cost, data, and automation — answered before you run a thing.
Open Molecule Studio and drive real structural biology from a chat — no PyMOL, no cluster, no setup.