Skip to content

Open data

Data library

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

2 datasets

spaceflight
  • 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
  • NEO close-approach risk intelligence (agent-curated)

    Near-Earth object close-approach risk intelligence (monthly)

    Monthly risk intelligence on every Earth close approach within 0.05 AU in the rolling 90-day window, from the official keyless NASA/JPL CNEOS Close-Approach Data API. Each approach event is entity-resolved (canonical designation; an is_named flag marks numbered+named objects vs provisional-only designations), deduped, and unit-normalized (miss distance in AU, lunar distances and km side by side). Diameter is estimated from absolute magnitude H via D = 1329/sqrt(0.14) * 10^(-H/5) and flagged as an estimate (NULL when H is missing); a documented kinetic-energy proxy in megatons of TNT assumes a spherical 3000 kg/m^3 body. A documented PHA-candidate rule (H <= 22 and dist_min <= 0.05 AU — a conservative implementation of NASA's PHA definition, not the official roster) flags potentially hazardous objects. The 0-100 risk_score = 100 * (45% exp(-dist_ld/8) + 30% min(1, log10(diameter_m)/3.3) + 15% min(1, v_rel/72) + 10% PHA bonus) is ranked as risk_rank (1 = riskiest; ties: miss distance asc, approach id asc) with risk_tier bands (elevated >= 70, watch >= 45, routine >= 20, minimal below). Per-object window context (approach count, closest-approach flag) and the exact JPL Small-Body Database lookup URL sit behind every row. Columns: as-of date, ISO week, approach id (primary key), designation, is_named flag, full designation verbatim, orbit id, approach datetime/date (ISO), nominal/min/max miss distance (AU), miss distance (lunar distances, km), relative velocity (km/s), absolute magnitude H (nullable), estimated diameter (m, nullable), diameter source, size class, PHA-candidate flag, energy proxy (MT TNT, nullable), risk score + tier + rank, window approach count, closest-approach flag, JPL lookup URL, row hash. Nullability: abs_magnitude_h, diameter_m and energy_mt_tnt are null where the API carried no value — kept, never invented. Caveats: risk_score is within-snapshot relative, not comparable across months; diameter and energy are order-of-magnitude estimates under documented assumptions, not measurements or impact predictions; pha_candidate is an approximation, not the official JPL PHA list. Sample use: order by risk_rank for the month's most noteworthy approaches, filter pha_candidate for potentially hazardous objects, or group by size_class.

    • spaceflight
    • nasa
    • asteroids
    • risk
    rows
    43
    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.