query ground-station observation data via the satnogs network and db apis
domain: satnogs.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
No account is required for read-only access; SatNOGS DB and Network APIs are open under CC BY-SA.
Call GET https://db.satnogs.org/api/satellites/ or /transmitters/ to look up a satellite's metadata and known transmitters/frequencies.
Call GET https://network.satnogs.org/api/observations/ with filters (satellite NORAD id, ground_station, start/end timestamps) to list crowd-sourced observation jobs and their status/waterfall data.
Call GET https://network.satnogs.org/api/stations/ to get metadata (location, antenna, status) about the ground station that produced an observation.
Follow the DRF-style pagination (next/previous links) on list endpoints when iterating large result sets.
Known gotchas
Observation data is community/crowd-sourced from volunteer ground stations, so coverage, signal quality, and demodulated data are inconsistent — treat it as best-effort, not guaranteed telemetry.
SatNOGS DB and SatNOGS Network are separate services with separate API roots and purposes (satellite/transmitter catalog vs. observation scheduling/results) — don't assume one API surface covers both.
Some endpoints support write operations (e.g. transmitter suggestions) that require an authenticated account and community moderation; read-only queries do 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?