The system is designed so that the first useful query is reachable on day one, regardless of what your stack looks like. There are three primary access paths.

The fastest on-ramp. Start the local API server and open the bundled web page in a browser.

From there, the interface exposes tabs for compound search, transformation lookup, and recipe generation. No coding needed for the first pass.

For teams already in a notebook or pipeline, the Python reader is the natural fit:

Same data, fully programmatic. This is the path most R&D teams will end up on once they move past initial exploration.

For terminal-driven workflows or quick batch experiments:

The CLI is also the foundation for batch processing — pointing the reader at a list of targets and letting it work through them unattended.

Realistic timelines, depending on how deep you need to go:

• Basic deployment (1–2 days) — web interface or Python API, single machine, exploratory use.
• Production deployment (1–2 weeks) — server setup, configuration, internal access controls, validation runs.
• High-performance deployment (2–4 weeks) — dedicated hardware, optional accelerator integration, tuned storage for the full 2,609-file corpus.
• Custom integration (1–3 months) — embedding the system into an existing research platform or data pipeline.

When you receive the system, it arrives as a self-contained handoff:

• Complete data package (handoffs/bluray_data/ — 2,609 files).
• Processed data outputs (handoffs/alchemy_data_v2_output/).
• Web API server, Python reader library, and web interface.
• Core system components and data-access modules.
• 61 documentation files covering quick starts, architecture, generation, and validation.

You should expect a working query within an hour of unpacking, a useful exploratory session within a day, and a real production footprint within a couple of weeks. The system is positioned as a complete handoff — not a research prototype — and is priced accordingly at $10B for the full data and tooling package.

If you have followed the series this far, you have the premise (post 1), the data (post 2), the use cases (post 3), and now the path to actually using it. From here, the work is yours.

Copy one of the formats below:

• Introducing Alchemy Probability DataAlchemy Probability Data turns the search problem at the heart of chemistry into something queryable:…
• Inside the Data: 2,609 Files, Millions of CompoundsA tour of the 2,609 files: compound combinations, probability matrices, transformation guides, and discovery reports…
• Outcomes and Use Cases: What the System Is Actually ForThe use cases the database was designed for — pharma screening, materials development, process optimization,…
• Case Study - A Formulation Team Uses Software-First Chemistry Before Committing to Hardware
• Product Insight - Software-First Chemistry, Reducing Capital Risk Before You Build