retrieve conjunction data messages (cdm) from space-track
domain: space-track.org · 4 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate to Space-Track.org (session login) as with any basicspacedata/expandedspacedata query.
Query the cdm class, e.g. /basicspacedata/query/class/cdm/TCA/%3Enow/orderby/TCA%20asc/format/json, filtering by predicates like TCA (time of closest approach) or the involved object catalog numbers.
Use CREATED (message creation time) or a specific event's identifier to pull updates for a single conjunction event only.
Parse fields such as MISS_DISTANCE, COLLISION_PROBABILITY, SAT_1_ID/SAT_2_ID, and relative velocity/covariance data from each CDM record.
Known gotchas
Space-Track's usage policy limits CDM pulls to about 3/day for the full constellation feed and 1/hour for a specific event — 18 SDS still emails owner/operators directly for urgent close approaches, so this API is not the sole safety channel.
CDM access generally requires an approved Space-Track account tied to a registered owner/operator or research use case; anonymous/basic accounts may see limited or no CDM data.
CDM is a CCSDS-standard message format; numeric covariance/probability fields need domain expertise to interpret correctly — don't feed raw miss-distance numbers into automated decisions without review.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?