SynapseX Labs

AI for quantum
research. With receipts.

A research agent with its own laboratory: it drafts the experiment, probes it on free simulators first, escalates to paid compute only with your approval — and freezes every run into a reproducible record.

Labs live on every accountFree simulators liveQPU in developmentGPU in development
$0quantum simulation within the Free limits
100simulation runs a month on the Free plan
24 qexact statevector simulation
SHA-256Merkle-sealed record of every run
$0quantum simulation within the Free limits
100simulation runs a month on the Free plan
24 qexact statevector simulation
SHA-256Merkle-sealed record of every run
$0quantum simulation within the Free limits
100simulation runs a month on the Free plan
24 qexact statevector simulation
SHA-256Merkle-sealed record of every run
Research areas

What we study.
What we can show today.

Four lines of work feed the products on this site. Each one says what is measured, on what, and what is still in progress.

01LLM training

LLM training & evaluation

The SynapseX model family behind Chat and the API Platform is trained on European HPC GPU resources, under EuroHPC allocation EHPC-AIF-2025LS13-019. We study what makes a model useful for code, science and quantum work, and how to measure that honestly.

  • in progressNo results published yet. When we publish, the evaluation set ships with the score.
The models on the API Platform
02Quantum compilation

Quantum compilation & routing

Circuit placement, routing and optimisation benchmarks, measured on simulators and labelled as simulation. A method that loses is reported as a loss, and hardware results are reported only once a partner QPU run exists.

  • simulationGHZ-6: fidelity 0.90 in a median of 4 evaluations vs 133 for SPSA, over 3 seeds, on a CPU state-vector simulator.
Inside the quantum lab
03Evidence

Evidence & reproducibility

Every run is frozen into a sha256 manifest of code, dependencies and backend, sealed under a Merkle root. That proves integrity and lets anyone re-run it. It does not prove who ran it.

  • simulationRecords from simulator runs recompute offline with softqcos evidence verify --offline.
Evidence in the control plane
04Genomics

Computational genomics

Variant interpretation as a reproducible lab: the agent gathers the public evidence, writes and runs the analysis, and escalates a subproblem to quantum only where that is honest.

  • in progressThe lab and the public evidence are live. The Substitution Atlas and our own sequence model are in development.
SynapseX Genome
The research loop

From question
to receipt.

I
step 1 / 4running

Brief the agent

Describe the question in plain language. The agent drafts hypotheses, circuits and analysis code in a persistent Labs workspace — Jupyter notebooks included.

Use cases

What researchers run here.

Inside the quantum lab

Algorithm bring-up

Prototype and debug quantum algorithms against exact simulation, sweeping parameters from Jupyter notebooks the agent reads and edits with you — and catch the bug before it costs a paid run.

Error-correction studies

Run error-correction Monte Carlo on repetition and surface codes and compare device topologies on the free tools. Noisy circuit simulation is in development.

Hardware selection

Compare QEC code families and device topologies on the free tools — then let the agent argue the trade-offs for your device.

Chemistry & materials

Small-molecule and small-ansatz studies on the free simulator. Larger electronic-structure runs are in development.

Reproducible papers

Run manifests and evidence bundles designed to be checked by someone who wasn't in the room.

Benchmarks

Numbers
with receipts.

Quantum marketing runs on multipliers. We publish a number only when a run record stands behind it, and every number is labeled simulation or hardware.

4 vs 133
median evaluations to fidelity 0.90, GHZ-6, Autopilot vs SPSA
3
seeds, CPU state-vector simulator
24 q
largest exact simulation
Read the docs
evidence ledgerOperational
GHZ-6 optimisation benchmark
fidelity 0.90 in a median of 4 evaluations vs 133 for SPSA · 3 seeds
simulation
Exact state-vector simulation
CPU, up to 24 qubits · a sealed record per run
simulation
Evidence seal
SHA-256 Merkle root over the run record · shows integrity, not origin
evidence
Hardware validation
not yet: partner QPU access is in development
in development
Publications & releases

Dated, public,
checkable.

Everything here can be opened by someone outside the company. Technical reports join the list when they are public, with what is needed to check them.

Releases link to their public package pages. Compute allocations are listed for context; they are not results.

Why SynapseX

Built for scientists
who check.

Trust in quantum results shouldn't require trusting us. The workflow assumes you'll verify — so every layer leaves something verifiable behind.

sha256 manifests$0 simulatorsapproval before spendsimulation, labeled

Reproducible by construction

Code, dependencies and backend are hashed into a manifest at dispatch — the run is re-runnable, the record tamper-evident.

Cheapest probe first

Free simulation answers most questions. Paid compute, when it opens, will ask for an estimate and your approval before a credit moves.

Public where it can be

Releases link to their public PyPI pages, and the evidence seal can be recomputed offline by anyone.

Honest results policy

Every number is labeled simulation or hardware, and nothing is called hardware until it ran on hardware.

Toolchain

Works where
you already work.

Install from PyPI, keep your notebooks, script the same lab the agent uses.

synapsexPython SDK · PyPI
softqcos-sdkquantum SDK · PyPI
synapsex-platformplatform SDK · PyPI
softqlibalgorithm library · PyPI
Jupyternotebooks, native
MCPagent protocol
Python3.10+ runtime
SynapseX CLIterminal
SynapseX DesktopmacOS · Linux · Windows
synapsexPython SDK · PyPI
softqcos-sdkquantum SDK · PyPI
synapsex-platformplatform SDK · PyPI
softqlibalgorithm library · PyPI
Jupyternotebooks, native
MCPagent protocol
Python3.10+ runtime
SynapseX CLIterminal
SynapseX DesktopmacOS · Linux · Windows
synapsexPython SDK · PyPI
softqcos-sdkquantum SDK · PyPI
synapsex-platformplatform SDK · PyPI
softqlibalgorithm library · PyPI
Jupyternotebooks, native
MCPagent protocol
Python3.10+ runtime
SynapseX CLIterminal
SynapseX DesktopmacOS · Linux · Windows
SynapseX DesktopmacOS · Linux · Windows
SynapseX CLIterminal
Python3.10+ runtime
MCPagent protocol
Jupyternotebooks, native
softqlibalgorithm library · PyPI
synapsex-platformplatform SDK · PyPI
softqcos-sdkquantum SDK · PyPI
synapsexPython SDK · PyPI
SynapseX DesktopmacOS · Linux · Windows
SynapseX CLIterminal
Python3.10+ runtime
MCPagent protocol
Jupyternotebooks, native
softqlibalgorithm library · PyPI
synapsex-platformplatform SDK · PyPI
softqcos-sdkquantum SDK · PyPI
synapsexPython SDK · PyPI
SynapseX DesktopmacOS · Linux · Windows
SynapseX CLIterminal
Python3.10+ runtime
MCPagent protocol
Jupyternotebooks, native
softqlibalgorithm library · PyPI
synapsex-platformplatform SDK · PyPI
softqcos-sdkquantum SDK · PyPI
synapsexPython SDK · PyPI
FAQ

Questions researchers ask
before the first run.

It drafts them. The agent turns a question in your own words into candidate circuits, parameter sweeps and analysis code inside a persistent workspace, then runs the cheapest probe that can tell the candidates apart. You review the reasoning and the code — nothing runs on paid hardware without your approval.

Nothing, within the Free limits: exact statevector simulation up to 24 qubits runs at 0 credits, up to 100 simulation runs a month, one at a time, up to 60 seconds each, on CPU only. That is the product, not a trial — most research questions are answered and most dead ends discarded before anything is billable.

No. Describe the problem in your field's language — chemistry, materials, optimization, machine learning. The agent decides what is classical, what is quantum, and what is not worth running at all, and explains the trade-off before spending anything.

Every dispatch freezes a manifest: a sha256 hash of each input file, the dependency set, the entrypoint, the execution mode and the backend identifier, hashed over canonical JSON. The record travels with the result, so a reviewer who was not in the room can re-run the same job and detect if anything was altered.

Today, CPU simulators: exact state-vector simulation up to 24 qubits through QCOS, our hybrid, hardware-agnostic scientific engine. Partner QPU gateways, GPU simulation and managed HPC execution are in development. The catalog lists only what is actually live.

An SDK gives you a circuit library. This gives you the laboratory around it: an agent that plans the experiment, a metered runtime designed to pick the cheapest backend able to answer, credits that reserve before a run and settle for actual usage, and a reproducible record at the end. Our Python SDKs are published on PyPI if you would rather script it yourself.

Partner QPU access is in development, so today every run goes to a free simulator. When it opens, the run will park with an estimate and wait for you: nothing is reserved until you approve it; on approval, credits reserve before execution and settle for what was actually consumed, with the remainder released. GPU and HPC tiers are in development and labeled as such everywhere on the platform.

Yes. The runtime is MCP-native, so any MCP-capable agent can list backends, request an estimate, submit a job and fetch the resulting record. There is also a headless HTTP API and a CLI. Our models are tenants of the lab, not the only ones.

Put an AI scientist
in your lab.

Start free: simulators cost 0 credits within the Free limits, up to 100 simulation runs a month, one at a time, up to 60 seconds each, on CPU only. Partner QPU access is in development.

SynapseX Labs · pip install synapsex · chat.synapsex.ai