Query scheduled and completed satellite pass observations from the SatNOGS Network API
domain: network.satnogs.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Send a GET request to https://network.satnogs.org/api/observations/ to list observations, filterable by satellite NORAD ID, ground station, or status.
Send a GET request to https://network.satnogs.org/api/stations/ to retrieve metadata (location, antenna, status) for community ground stations in the network.
Send a GET request to https://network.satnogs.org/api/jobs/ to see scheduled observation jobs, the mechanism ground-station operators use to know what to record next.
Make read-only requests to observation/station data with no authentication required; submitting new observation data as a station operator requires an authenticated account tied to a registered ground station.
Parse observation records for recorded audio/waterfall artifact URLs, vetted/unvetted status, and the associated transmitter/frequency metadata pulled from SatNOGS DB.
Known gotchas
This is a distinct API from SatNOGS DB (satellite/transmitter reference data); Network is about scheduling and recording actual passes, so don't conflate the two when building an integration.
Submitting new observation data requires operating, or having access to, a registered SatNOGS ground station, not just an API key; read access is open, write access is not.
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?