The Launch API — Every Launch on Your Book, Read Before Its Window, by API
For space insurers, reinsurers and brokers — the desks that carry launch risk. Your system registers a mission with one keyed call — vehicle, site, up to…
The Launch API — every launch on your book, read before its window, delivered by API to space insurers, reinsurers and brokers — the desks that carry launch risk
How the API works. Your system registers a mission with one keyed call (vehicle, site, up to fourteen windows, the cover phases as the policy writes them), polls the id, reads its events and seal state (preparing · provisional · requested · sealed · amended · escalated · resealed · graded), requests the principal’s seal when a mission moves toward binding, and receives the grade on the same id after the window. Scale: any number of provisional calls on any registered mission, every mission on the manifest, four projections on every call; the hand’s seals are the scarce good, counted on the annual seat. Before liftoff the principal reads the launch day itself — the one risk variable a readiness review does not weigh — and seals the read before the window, graded after, in public. The service returns ONE object per window: the window in (open, close, planned T-0, site); every minute scored by the engine; the maximal runs of one state (the bands) under four projections — the launch team's overall view and the three cover phases, pre-ignition, launch, operating life (L+1, twelve months); the T-0 exposure in three cuts (the clean set a clean-only line attaches on, the full set with the value at open beside the mean, the bands outside clean cited by id and UTC); the assessment at four addresses, provisional by default, the principal's seal on request.
The sample — USSF-366, a national-security mission, from the engine
The page renders the served object /dataset/la024-window-health.json (241 minutes of the 15 Aug 2026 21:52–01:52Z window at Vandenberg SLC-4E; six bands; engine 0.9.2) and recomputes its SHA-256 in the browser beside the hash printed when the engine drew it. Beside it, what the day delivered from the sealed advisory LA-024: scrub or delay called at 0.90 on 14 Aug; the nominal 14:52 PDT T-0 slipped to 16:47 and then 18:50 — 3 h 58 min of delay inside the four-hour window, liftoff at T+238 of 240 minutes, graded HIT at the webcast. Nothing on the page is drawn by hand.
The record is the credential · the door
Every launch-day call sealed by SHA-256 and Bitcoin-anchored before the window, graded against provider, NASA or FAA statements after; one line to any AI recomputes the record (jyotishintelligence.com/launch-verify.txt). Two seats on one page, every figure rendered from the chair-signed services law: the Launch Seat per mission (never per call; re-seals free on every slip; the principal’s seal on request) and the Annual Seal Seat (one fixed fee a year, one key, any number of provisional calls on any registered mission, 24 sealed missions included, each further sealed mission at the posted line; one-year term, longer by written agreement). A covered call graded MISS makes the next read free; the principal's seal on request). Keyed access only; no free keys; the descriptor is not published. An augmenting input, never go/no-go authority; one principal's signature over a staff of automated systems; procure the output, not the recipe.