The 48-hour loop

When a hologram arrives, the single strongest thing you can do is send the reconstruction back within 48 hours. Speed of response is the strongest conversion signal we have. This page is the exact sequence.

Step 1 — acknowledge (same day, 2 minutes)

Reply: "Got it — I'll send your reconstruction and its provenance record within two days." Nothing else. Start the clock in the prospect row (reply received at ⟨timestamp⟩).

Step 2 — reconstruct their data

You need four numbers from them: wavelength (µm), pixel pitch (µm), and a distance range (z min / z max, mm). If they gave only an approximate distance, bracket it with z_min_mm / z_max_mm.

The no-account path, exactly (two calls — the first fetches a page token, then you wait out the 3-second dwell, then submit):

TOKEN=$(curl -sS https://api.apertureapi.com/public/form_token \
  | grep -o '"token":"[^"]*"' | cut -d'"' -f4)

sleep 3

curl -sS -X POST https://api.apertureapi.com/public/reconstruct \
  -F "file=@their_hologram.png" \
  -F "form_token=$TOKEN" \
  -F "wavelength_um=0.635" \
  -F "pixel_pitch_um=1.85" \
  -F "z_min_mm=0.5" \
  -F "z_max_mm=3.0" \
  -o reconstruction.zip

Replace the four values with theirs. The token is bound to your IP and User-Agent and is single-use, so both calls must come from the same machine; do not collapse them into one. (Prefer clicking? Open https://api.apertureapi.com/, pick their file, wait ~3 seconds after the page loads, and submit — same result, no token handling.)

If it refuses with HTTP 507: that is the size ceiling answering predictably with an estimate instead of dying mid-request. Ask them for a center crop, or use an API account for the larger-input path. Do not treat a 507 as a failure to hide — it is a feature you can mention.

One guard to pre-empt: the service requires pixel_pitch_um strictly greater than wavelength_um. If a lab quotes an object-referred pitch (sensor pitch divided by magnification) it can trip this. If you see that rejection, ask whether the pitch they gave is at the sensor or at the object.

The ZIP contains the height map, a 3-D mesh, and the provenance record — the receipt with the content-addressed result ID, the software version, and the SHA-256 commitments to the input and config.

Step 3 — send it back, watermarked, with ONE question

Attach a watermarked preview image of the height map (mark it "ApertureAPI — preview"). In the email body, give them the result ID from the provenance record so they can see it re-computes, and close with exactly one question:

Which of these four brought you here — a person leaving who owned the setup, a reviewer asking how the numbers were made, not getting the same answer twice, or just that reconstruction is a pain to set up?

That question sorts them into the four pains and starts a real conversation. Nothing in this email claims accuracy, agreement to ground truth, or a speed — you are showing a result and a receipt, not asserting a measurement.

Step 4 — log

In the prospect row: time from reply to result (the number that matters), the result ID you sent, and their answer to the one question. Roll time-to-result into the weekly report.

Artifact when done: a saved reconstruction.zip with its provenance record, a logged time-to-result under 48 hours, and the prospect's pain answer recorded. A prospect who answers the question is a trial candidate — go to page 20.

Buyer pages to pair with this page: reproducibility bundle · methods supplement · workflow fit. Pipeline stages and KPIs: page 00.