For a low-Earth constellation, how much beam time a parcel can receive is decided by how often your planes carry a spacecraft over it — and that is a function of latitude. Every longitude passes under a circular orbit eventually.
We measured this rather than assuming it, because the map depends on it. Across three and a half days the longitude pattern does not survive: the correlation is −0.30, and day-to-day variation at a fixed longitude is as large as the variation between longitudes. So the demand layer resolves latitude and refuses to resolve longitude, and a parcel is never shaded as better than its neighbour at the same latitude.
The shading below is the marched sweep — 360 latitude rows, eight longitudes, seven simulated days each — not a closed-form approximation. That distinction is worth about a factor of four and a half at low latitudes.
These are the two bands we are open in today. Not because nothing else works — higher latitudes are genuinely better on beam time — but because these are the regions where a rent figure has a cited comparable behind it. We would rather decline to price a parcel than price it from nothing.
A requirement records the fleet it was posted against, by epoch. That matters more than it sounds: scores move when the element sets move, and a shortlist that cannot say which sky it was computed under is a shortlist you cannot audit later.
The weights are visible on every match. So is the rejection list — the listings that were considered and dropped, and which term dropped them. A ranking you cannot interrogate is a ranking you have to take on trust, and we would rather you did not have to.
One thing the shortlist deliberately does not carry: the owner’s identity. That arrives when you send an approach and they respond to it, not before.
Orbital element sets, ground-station rosters with surveyed horizon masks, weather at every station, catalogue cross-checks, independent pass prediction, and bookable antenna capacity from commercial ground-segment vendors.
Four of the ten need no credentials at all. The rest need an account, and until they have one the console shows them as not configured rather than hiding them — alongside record count, measured latency and the exact URL called.
Every provider path is read-only by construction. Nothing we call can task a spacecraft, book a contact or spend money.
Every figure carries what kind of figure it is. A beam-hour count derived from element sets is a measurement. An indicative rent is an estimate. A battery state of charge is modelled, because no operator publishes bus telemetry and nothing in an element set implies it.
They never render alike, and the tag is on the number rather than in a footnote.
Every standard we cite, and how deeply →Coverage for a coordinate, the standards registry as data, and public listings — under a per-organisation key you can revoke. Listing centroids are rounded to about a kilometre, deliberately.
The same API serves our conformance declaration against BPI, a draft interoperability interface we wrote and are so far the only implementation of. We emit as a broker, never sign, and verify no signatures — so an ingested capability means somebody supplied a file, never that an operator attests to it. Every response says so in the payload.
You need an organisation and a fleet. Everything else — the band, the scores, the rejections — is computed. If nothing matches, the answer says which term emptied the list rather than returning nothing.