Stage this page moves: into stage 1, qualified workflow (page 00). Buyer page to send: workflow fit.
Every reply, talk question, clinic sign-up, referral and inbound email that
describes a setup gets a workflow-fit check the same day. No check, no
stage 1. The check is how we avoid promising a lab something the service will
refuse, and how a needs_review becomes a conversation instead of a surprise.
A no-account endpoint, POST /public/workflow_fit (JSON in, JSON out, no file
upload), and the public checklist page at
/docs/workflow-fit. It returns
one of three verdicts:
| Verdict | Means | What you do |
|---|---|---|
tested |
this geometry and file format are accepted and processed by the service's automated test suite, inside every enforced limit | ask for one frame with its metadata (stage 2) |
needs_review |
plausible, but outside what the test suite covers (phase-shifting, HDF5, frames larger than the standard field, magnified systems, lossy JPEG …) | still stage 1; offer a 20-minute call or the monthly clinic before any pilot talk |
unsupported |
will be refused or cannot be processed as-is | do not qualify; send the next_steps it returns, log unsupported, thank them |
tested is not an accuracy statement; nobody's setup has an established
accuracy yet. Never write "your setup is supported/validated" — write "your
setup is in the tested envelope; here is what that does and does not mean"
and link the buyer page.
To check your setup against what the service runs today, could you tell me:
1. Geometry: in-line, off-axis, phase-shifting, or other?
2. Wavelength (nm or um)?
3. Camera pixel pitch (um), and magnification if there is an objective?
4. Sample-to-sensor distance (mm), or the range you refocus over?
5. File format and bit depth (e.g. 16-bit TIFF, PNG, .npy)?
6. Frame size in pixels?
7. Which of these you record with each frame: wavelength, pitch, distance,
exposure; and whether you can take a blank (sample-free) frame?
8. Any independent measurement of the same target you already trust
(profilometer, interferometer, AFM, calibration target, bead standard)?
curl -s -X POST https://api.apertureapi.com/public/workflow_fit \
-H 'Content-Type: application/json' \
-d '{"geometry":"off-axis","wavelength_um":0.633,"pixel_pitch_um":3.45,
"z_mm":5,"file_format":"tiff","bit_depth":16,
"frame_width_px":1920,"frame_height_px":1080,
"metadata":{"wavelength_recorded":true,"pixel_pitch_recorded":true,
"distance_recorded":true},
"reference_measurement":"profilometer"}' \
> fit-<org>-<YYYYMMDD>.json
Unknown optics may be left out (null). Allowed values: geometry =
inline | off-axis | phase-shifting | other; file_format =
png | tiff | npy | npz | jpg | raw | hdf5 | video | other;
reference_measurement = none | profilometer | interferometer | afm |
calibration_target | bead_standard | other. If the pitch is already divided
by magnification, add "pixel_pitch_basis":"object_space" and
"magnification". A 422 means a field is malformed — fix and re-run; it is
not a verdict.
Artifact: the saved fit-<org>-<date>.json, linked from the log row.
A row moves to stage qualified only when all are true:
tested or needs_review (saved JSON);Exit to stage 2 needs frames; see page 17.
A lab can sit at stage 1 with needs_review for as long as the review takes;
log the open question and a next_action_date.
| What they told you | Send |
|---|---|
| cells, tissue, QPI, DHM, hematology, neuroscience | for biomedical QPI (research tooling, never diagnosis) |
| DH/interferometry methods group, thesis students, papers | for holography labs + methods supplement |
| surface/topography, micro-optics, a reference instrument | for industrial QA (lab-side only) |
Artifact when done: every reply this week has a saved fit response and a stage in the log.