Skip to main content

Quickstart: a free audit of your passes

Upload a log of the passes you flew last week, and Passes reports what they delivered against what they could have: the share delivered, the passes lost and how, and how often each landed inside its forecast range. On the free Explore plan, your first audit run starts a 48-hour free audit.

1. Open the audit​

Sign in, open Passes, choose Past, then Audit. On the demo fleet, Upload 7 days of pass logs, in the line under the top bar, leads to the same place. The audit runs through your sign-in session, so you need no API key of your own.

2. Describe your fleet​

A pass log is matched against your network config, so the audit needs your satellites and ground stations first. With no fleet yet, it offers Start from the catalog, to pick your own from the public asset catalog, or Load the demo fleet. See Planned fleet. On Explore, your network config holds up to 2 satellites of your own.

3. Upload a pass log​

Drop a CSV on Upload a pass log, or choose Choose CSV. One row per pass you flew, columns in any order:

ColumnHolds
satellite_idA satellite in your network config
antenna_idA ground antenna in your network config
aos_utc, los_utcWhen the pass started and ended, ISO 8601 with a UTC offset, such as 2026-11-02T14:20:00Z
bytes_deliveredWhat the pass delivered, a whole number of bytes
statusok, failed or missed

A log with a bad row writes nothing, and the upload lists the bad rows grouped by problem. On Explore an audit run covers at most 2 satellites of your own, so log up to 2. Any run covers at most 7 days, so log a week at most. On the demo fleet, Use a sample pass log uploads one for you.

4. Run the audit​

With no audit workflow yet, Run the audit makes it first: it saves the audit-ledger template as yours, with only its predictions output, so it sends results nowhere else. It reads the days your pass log covers (Your pass log's days), or the last 7 days, in UTC, before you upload one; choose Change to set other days in From, UTC and To, UTC. Then choose Run the audit.

On Explore, the first run starts the clock: Free audit beside the run shows the time left and when it ends. For 48 hours you can upload more logs and run the audit again; after that, new audit runs are refused with 403 free_audit_ended and need Operator, and the reports you ran stay readable. A run over more than 2 satellites of your own is refused with 403 plan_required.

5. Read the report​

The report opens under Past on Passes, labeled Audit:

  • Delivered: the share of possible GB your passes delivered, by ground station, satellite or day, with the dead passes and whether each failed or was missed;
  • In range: how often a pass delivered inside its forecast range, against the 80% aim, and the typical miss in GB, by model or ground station;
  • logged contacts that matched no computed pass, so you can check for a wrong ID, a wrong time, or a pass your network config does not describe.

Open a pass for its breakdown. Copy report link gives a link that opens the report for anyone signed in to your account. Accuracy explains the numbers.

With the API​

Upload with POST /telemetry/pass-logs, then run audit-ledger over the past window with POST /predictions, dataset: "audit" and, on Explore, deliver: false:

curl --fail-with-body -sS -X POST \
-H "x-api-key: $CONSTELLATION_API_KEY" \
-H "Content-Type: text/csv" \
--data-binary @passes.csv \
"https://api.constellation.space/telemetry/pass-logs"

The rules, including the free audit's limits and free_audit_ended, are in Audit passes against forecasts.

Next: call the API with a key of your own.