# Swift Navigation

> Precise positioning for mass-market applications. Swift Navigation's Skylark service streams
> real-time GNSS corrections over NTRIP to take positioning from metres to centimetres, and its
> Swift Binary Protocol (SBP) is the open, machine-readable wire protocol for its GNSS receivers and
> the Starling positioning engine.

generated: 2026-08-29
method: generated
source: apis.yml plus the artifacts in this repository. Swift Navigation publishes no llms.txt of
its own; https://www.swiftnav.com/llms.txt 301s to the homepage (a site-wide catch-all), so this
file is generated by API Evangelist and is NOT a Swift Navigation document.

## What is actually callable

Three things can be called today. Two need no credentials at all.

- **Skylark NTRIP sourcetable — no auth.** `GET http://<region>.<freq>.skylark.swiftnav.com:2101/`
  returns `content-type: gnss/sourcetable` listing every correction stream, its RTCM message
  numbers and its constellations. Regions: `na`, `eu`, `ap`. Frequencies: `l1l2`, `l1l5`,
  `all-freq`. Ports: 2101 plain, 2102 TLS, 2103 mTLS (NTRIP v2 required).
- **Web data endpoints — no auth.** `GET https://www.swiftnav.com/wp-json/e4lm6SFEc9/data/`
  (134-receiver Skylark compatibility catalog) and
  `GET https://www.swiftnav.com/wp-json/gy9i81x4mh/data` (per-country Nx/Cx/Dx availability).
- **Skylark correction streams — HTTP Basic, per device.** `GET` a mountpoint on a caster with the
  NTRIP username and password issued when a device is created in the Skylark User Portal. The caster
  writes RTCM 3.x frames continuously; the client pushes NMEA GGA back up the same connection.

## What is NOT callable

- There is **no REST API and no OpenAPI**. Probed on www.swiftnav.com, account.swiftnav.com,
  account-service.skylark.swiftnav.com and subscription-service.skylark.swiftnav.com — all miss.
- There is **no MCP server** and **no A2A agent card**.
- The **Sora gRPC API** has a complete, public contract on the Buf Schema Registry (34 RPCs), but
  `grpc.sora.swiftnav.com` serves a placeholder Kubernetes ingress certificate. The contract is live;
  the endpoint is not. Do not build against it.
- The Skylark portal's backend services exist and are named in the portal's own runtime config, but
  publish **no contract**. Device creation, credential issuance and subscription changes cannot be
  automated from published material.

## Things an agent must know before acting

- **Deleting a device is permanent.** Swift Navigation states it cannot be undone and no refund is
  issued for the remaining subscription term.
- **NTRIP passwords are not recoverable.** They are shown once. Generating a new one invalidates the
  old one and every receiver configured with it stops receiving corrections.
- **The 14-day trial has a variant deadline.** Whichever Skylark variant is selected at the moment
  the trial expires becomes the permanent variant for that device.
- **Reference frame is chosen by mountpoint name**, not by a parameter — `NXRTK-NAD83-MSM5` is
  NAD83(2011) epoch 2010.0 and US-only; `NXRTK-DREF91-MSM5` is Europe-only. Picking the wrong one
  produces a confidently wrong position.
- **Altitude omitted means local ground level**, not zero, in the Sora contract.
- **There is no status page.** If corrections stop, there is nowhere public to check.

## Specifications and contracts

- Swift Binary Protocol spec (YAML, 29 packages, 242 messages): spec/
- SBP JSON Schema (draft-06, 225 documents): json-schema/
- Sora gRPC / protobuf contract (2 services, 34 RPCs): grpc/
- Skylark stream catalog (probed): asyncapi/swift-navigation-skylark-ntrip-streams.yml

## Client libraries

All generated from one spec and released together at 6.5.1 (2026-07-08): `sbp` on PyPI, npm,
crates.io and Hackage. **The Java binding `com.swiftnav:sbp` is stuck at 5.0.7 (2024-03-27)** and is
missing every message added since. See packages/.

## Documentation

- Support / knowledge base: https://support.swiftnav.com/support/solutions
- SBP library docs: https://swift-nav.github.io/libsbp/
- NTRIP client configuration: https://support.swiftnav.com/support/solutions/articles/44002519397-ntrip-client-configuration-for-skylark-corrections
- Skylark Portal user guide: https://support.swiftnav.com/support/solutions/articles/44002287337-skylark-portal-user-guide
- Skylark quick start: https://www.swiftnav.com/skylark-quick-start-guide
- GNSS glossary (69 terms): https://www.swiftnav.com/glossary
- GitHub: https://github.com/swift-nav
- Sign up: https://account.swiftnav.com/sign-up

## Commercial

Per-device subscription, monthly or annual, Stripe self-serve, 14-day free trial once per account,
no device minimum or maximum. **No prices are published anywhere** — the amounts only appear inside
the portal after sign-in.

## Standards

RTCM SC-104 v3.x, NTRIP 1.0/2.0, NMEA 0183 (GGA), ITRF2020 / WGS84(G1674) / NAD83(2011) / ETRS89,
ISO 26262:2018 (Skylark certified by UL Solutions, 2024-06-04), OAuth 2.0 + OIDC + RFC 8628
(Auth0 tenant skylark-prod.us.auth0.com), gRPC/proto3, JSON Schema draft-06.