Skip to content

Open data

Data library

Open datasets, fully documented — searchable here, and readable by any LLM.

  • The Space Devs Launch Library 2 (launch intelligence)

    Orbital launch manifest intelligence (weekly)

    Every upcoming orbital launch on The Space Devs Launch Library 2 manifest (keyless official API), joined with each launch provider's trailing-12-month reliability record — typically ~360 launches/week. Each row is one planned launch: launch and mission names, status (TBD/TBC/Go/Hold), NET no-earlier-than date and launch window, NET precision class + precise flag, T-minus countdown in hours and its bucket (imminent/this_week/this_month/later), provider + type, rocket name/family/variant, mission type + coarse mission class (human_spaceflight, cargo_logistics, science, connectivity, security, tech_test, operations), orbit, launch pad + location, country (canonical name + ISO alpha-3; empty when LL2's pad country code is unresolvable), webcast flag, provider 12-month attempts / success rate / current success streak / dense reliability rank (null for providers with no trailing-year history — never imputed), per-row LL2 source URL, and a row hash. Primary key: launch_id (LL2 UUID). Cadence: weekly; as_of is the run's UTC date, so identical input produces an identical content hash. Caveats: NET dates and statuses are planning values and shift; LL2 carries no accuracy guarantee; provider join is on LL2-canonical names (exact string match). Terms allow any use with encouraged attribution -> commercial_use = yes. Sample use: filter countdown_bucket = 'imminent' for this week's launches, or order by provider_reliability_rank for the most reliable rides.

    • spaceflight
    • technology
    • signals
    • weekly
    rows
    367
    Quality
    100
    Updated
    Sep 25, 2026
    Fresh
    License
    Commercial use OK

Use your own AI key

Once today's free allowance is used up, AI features can run on your own provider account.

Kept in this browser tab only (cleared when you close it) and sent with each AI request. Our servers use it for that request and never store or log it.