What it can do

Match Components: Reverse search over a typed spec layer: pass a category and engineering requirements, get every catalogued item grouped as A (meets all stated requirements), B (fails a named require

Build Budget: Engineering budget for a component stack: pass product ids (from the other tools) and your bus voltage, get total mass, total steady-state power, per-item data interfaces, voltage-compat

Get Component Specs: The full typed layer of a category — every item with every value (number, canonical unit, bound, measurement condition, datasheet source page, confidence L0/L1) plus the property

Typed, datasheet-sourced spacecraft component specifications: 2,500+ flight hardware products across 24 categories (reaction wheels, star trackers, propulsion, radios, antennas, structures, ground stations and more) with 19,900+ values that each cite the vendor datasheet page they came from. Underneath sits the datasheet layer itself: 26,000+ facts read from 800+ datasheets, each anchored to a quoted page.

Tools

match_components — reverse search: pass engineering requirements, get every catalogued item grouped A (meets all), B (fails a named requirement, both figures quoted) or C (could fit, data missing). Optional price ceiling and export-control filter.
get_component_specs — the full typed layer of a category for your own comparison or trade study.
build_budget — mass and steady-state power of a stack, with bus-voltage checks and an honest list of what could not be counted.
get_datasheet_digest — facts machine-read from one product's datasheet, by section (electrical, interfaces, mechanical, thermal, qualification, commercial), each with page and verbatim quote.
search_datasheet_facts — one fact key across a whole category (connector, protocol, TID, flight heritage, lead time, price): one row per product with page and quote.
ask_datasheet — ask a datasheet a question and get the closest excerpts with page numbers, or scan every datasheet of a category for an exact term.
design_stack — a whole spacecraft bus from a plain-language task; pass fixed product ids to lock parts you have already chosen.
find_data_gaps — what is missing for a product, company or category and where to get it: already in the digest, in the datasheet text, or only from the vendor.

Three rules that make it usable by a machine

Nothing is guessed. A missing property means the vendor does not publish it, and the item is reported as "data missing" rather than filled with a typical value.
Conditions are kept apart — idle, steady-state and peak power are separate records with their measurement condition attached.
Every value is traceable: source file and page, plus a confidence level (L0 machine-extracted, L1 human-verified).

Data licence CC BY 4.0, attribution "NewSpace Market". Open dataset and examples: https://github.com/newspacemarket-com/mrd

NewSpace Market MRD

What it can do

What data it sees

Do you need an account

match_components	Reverse search over a typed spec layer: pass a category and engineering requirements, get every catalogued item grouped as A (meets all stated requirements), B (fails a named requirement, both figures quoted) or C (could fit, data missing). Verdicts cite the datasheet page. Omit parameters you do not care about. Categories: reaction-wheels, star-trackers, obc-computers, batteries, radios, solar-panels, propulsion, sun-sensors, magnetometers, magnetorquers, imus-gyros, gnss-receivers, eps, deployers, thermal, antennas, sdr-modems, cameras, structures, ground-stations, sadm, tanks-valves, separation-systems, pointing-mechanisms.
build_budget	Engineering budget for a component stack: pass product ids (from the other tools) and your bus voltage, get total mass, total steady-state power, per-item data interfaces, voltage-compatibility verdicts and an honest list of what could NOT be counted because the vendor does not publish it. Use it to assemble and sanity-check a subsystem, e.g. 3-4 reaction wheels for an ADCS.
get_component_specs	The full typed layer of a category — every item with every value (number, canonical unit, bound, measurement condition, datasheet source page, confidence L0/L1) plus the property dictionary grouped by interface port (perf/power/data/mech/thermal/env/supply) — for arbitrary comparison, budgeting or trade studies on your side.
get_datasheet_digest	Facts machine-read from a product datasheet, by section (identity, performance, electrical, interfaces, mechanical, thermal, environmental, qualification, lifetime, options, compliance, commercial). Each fact carries unit, condition, the page and a verbatim quote it was verified against (confidence L0) plus a link into the PDF. Use it for what the typed layer does not hold: connectors, protocols, survival temperature, vibration, radiation, heritage, options, export control, lead time. Pass product_id from match_components or a product name.
search_datasheet_facts	One fact key across a whole category: which products state it in their datasheets and what value — e.g. connector, data_interface, protocol, survival_temperature, tid_tolerance, flight_heritage, trl, export_control, lead_time, price, design_life. One row per product with page and quote. Reports coverage (how many products of the category have a digested datasheet).
ask_datasheet	Ask a product datasheet a question and get the closest excerpts with page numbers (pre-indexed text), or scan ALL datasheets of a category for an exact term (term + category) and get the exact list of products mentioning it with an excerpt each.
design_stack	Assemble a whole spacecraft bus from a plain-language task: the service plans the subsystems, matches every item deterministically against the stated requirements, computes the mass/power budget and writes an evidence-bound rationale. Pass fixed = product ids you have already chosen (from match_components or get_datasheet_digest): they stay in their subsystems, are checked against the requirements (selected.fixed, fixed_verdict, fixed_fails) and the rest is assembled around them. LLM-backed and rate-limited (6/min, 30/h anonymous).
find_data_gaps	What is missing for a product, a company or a category and where to get it: in_digest (already read from the datasheet — value, page), in_datasheet_text (the datasheet mentions it — page, excerpt), not_in_datasheet (ask the vendor), no_datasheet (ask the vendor for a datasheet). For vendors: what to publish; for buyers: what to ask.