For biomedical QPI labs

Research tooling only. ApertureAPI is not a medical device. It is not for diagnosis, screening, treatment or any clinical decision, and nothing it returns has been validated for those uses.

Quantitative phase imaging labs lose their reconstruction pipeline in a predictable way: the student who wrote the script graduates, the settings live in a notebook nobody can find, and a reviewer asks how a phase map was made. ApertureAPI makes the "how" a record rather than a memory.

What it gives a lab

• Continuity. The reconstruction runs on a hosted service with pinned software, not on a laptop that leaves with its owner. A new student can see exactly which input, settings and build produced an old phase map.
• A record per phase map. Every result carries provenance.json and evidence.json: the software version, a SHA-256 commitment to the input and to the settings, and IDs anyone can check.
• A methods line you can paste. Each result includes a ready-made methods sentence naming the software version, settings fingerprint and provenance ID. See Methods supplement.
• Plain-language quality bands. quality_report.json marks each metric pass, warn or fail against a published ceiling. A fail describes the image; we report it rather than hide it.

What we do not claim

We do not claim measurement accuracy or repeatability on your microscope. Our own reports state both as not-yet-established. The way that changes for your rig is a comparison against a reference you already trust — a bead or cell standard, or a known calibration target. That is what a design partnership produces.

Next step

Check fit in two minutes with Workflow fit, then read Design partnership. Questions to system@apertureapi.com.