Skip to main content

Build your fleet from the catalog

The public asset catalog holds the satellites and ground stations operators publish: names, operators, fleets, downlink and receive bands, and station positions. Start your network config from it instead of typing every field, then add what only you know.

The catalog fillsYou add
Satellite NORAD ID, name, operator, fleet, downlink bandsThe downlink radio: carrier frequency, bandwidth, EIRP
Ground station position and receive bandsThe antenna: its ID, receive range, G/T, dish size

Your values always win. The catalog never fills a radio value, so nothing is priced on a guess.

In Platform​

  1. Open Fleet, or a page that shows No fleet on this account yet, and choose Add or Start from the catalog.
  2. Search satellites by name, NORAD ID or operator, and ground stations by ID, owner or site. Use the arrow keys and Enter, or click, to pick several. Show more loads the next page.
  3. Choose Add N to fleet. For each pick, enter the radio or antenna values you have. A station's receive range starts from the catalog's band; change it to your antenna's.
  4. Choose Save to fleet. The picks join your fleet on Fleet, and a value they still need is named where a lane cannot price them (below).

Leave a field blank if you do not have it yet. The lanes that need it say so, and you can fill it in later. In the workflow builder, a lane lists the assets it cannot price with Fix in Fleet, which opens that asset on Fleet.

While your account holds the demo fleet, the tabs that show it sit in a frame labeled Demo fleet. With your first picks, Save to fleet asks whether to Replace the demo with these (the default) or Keep the demo beside them, or links to a clean workspace instead; see Move to your own fleet.

With the API​

Search the catalog, then add a pick to your network config with PATCH. Both routes are in Topology config.

curl --fail-with-body -sS \
-H "x-api-key: $CONSTELLATION_API_KEY" \
"https://api.constellation.space/assets/stations?near=64.86,-147.85&within_km=50"
curl --fail-with-body -sS -X PATCH \
-H "x-api-key: $CONSTELLATION_API_KEY" \
-H "Content-Type: application/merge-patch+json" \
-d '{"ground_stations": {"nasa-fairbanks": {"catalog": {"station_id": "nasa/fairbanks"},
"antennas": {"fbk-x-1": {"antenna_diameter_m": 3,
"frequency_ranges": {"x-rx": {"direction": "downlink", "min_ghz": 7.75, "max_ghz": 8.5, "g_t_db_k": 22.7}}}}}}}' \
"https://api.constellation.space/topology/config"

GET /topology/config then returns readiness per satellite and station. Over MCP, an agent does the same with search_catalog and patch_network_config; see Connect an AI agent.

Good to know​

  • The stored network config is complete on its own. It records the catalog version it was filled from, and each workflow run records it too, so a later catalog change never moves a past run.
  • When the catalog changes after you picked assets from it, Fleet says so above the list, with a button that refreshes them all, such as Refresh 3 from catalog. With the API, send the pick again in a PATCH, for example {"satellites": {"norad-43013": {"catalog": {"norad_id": 43013}}}}. A refresh copies the catalog's current name, operator, position and bands into the asset again. Values you set yourself are kept.
  • If your surveyed coordinates are more than 5 km from the catalog's, yours are kept and the write returns a catalog_coordinates_differ issue, in case one of them is a typo.
  • Some catalog stations publish no position. Add latitude_deg and longitude_deg yourself for those.
  • Demand needs a satellite that passes over your stations, and SSA covers orbits from 400 to 2,000 km. Readiness says when an orbit rules a lane out, so you do not wait for a value that cannot come.