> For the complete documentation index, see [llms.txt](https://wingbits.gitbook.io/wingbits-ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wingbits.gitbook.io/wingbits-ai/reference/nats-subjects.md).

# NATS subjects & topics

The live stream publishes flight data on a set of NATS **subjects**. Always start with the exact subject in your onboarding email. Your credentials may be restricted to that subject even when other subjects are documented here.

## Scoped trial subjects

A geographically or commercially scoped trial may use a subject such as:

```
flights.customers.trials.<TRIAL>.>
```

Wingbits provides the complete subject string in your onboarding email, including the final wildcard. Do not subscribe to the base subject without the wildcard, and do not broaden it to `flights.>` or `flights.full.>` unless those subjects are also listed in your onboarding email.

Scoped trial credentials are normally subscribe-only. Use direct Core NATS subscription APIs; publishing, request/reply (`_INBOX.*`), and JetStream access are unavailable unless Wingbits explicitly enables them.

## Core subjects

| Subject          | What it carries                                                            |
| ---------------- | -------------------------------------------------------------------------- |
| `flights.full.>` | Full-detail messages for all aircraft (every field)                        |
| `flights.5s.>`   | Throttled snapshots (one update per aircraft every \~5 seconds)            |
| `flights.dd.>`   | Per-aircraft "delta" updates, keyed by ICAO hex (e.g. `flights.dd.abafe4`) |

Replace `>` with a specific ICAO hex to follow a single aircraft, e.g. `flights.full.abafe4`.

## Add-on subjects

These require [add-on access](https://wingbits.gitbook.io/wingbits-ai/data-products/add-ons.md) on your credentials:

| Subject        | What it carries                        |
| -------------- | -------------------------------------- |
| `flights.adsc` | ADS-C oceanic position reports         |
| `flights.acas` | ACAS / TCAS collision-avoidance events |

## Choosing a subject

| Goal                      | Subscribe to            |
| ------------------------- | ----------------------- |
| Everything, full fidelity | `flights.full.>`        |
| Lower bandwidth, periodic | `flights.5s.>`          |
| One specific aircraft     | `flights.full.<hex>`    |
| Oceanic coverage          | `flights.adsc` (add-on) |

Higher-frequency subjects require the subscriber to process more messages. If your application reports slow-consumer warnings or cannot keep up without a growing backlog, switch to a lower-frequency subject if one is already assigned to your account. Otherwise, contact Wingbits to ask whether one is available. Wingbits may disconnect clients that do not drain the live feed quickly enough in order to protect stream latency and performance for other customers. See [Keep your consumer healthy](https://wingbits.gitbook.io/wingbits-ai/build/nats-stream.md#keep-your-consumer-healthy).

## Wildcards & shell gotchas

* `*` matches exactly one token, while `>` matches all remaining tokens.
* `>` only works at the end of a subject, such as `flights.full.>`.
* In zsh/bash, a bare `>` outside quotes is a redirect — always quote subjects: `nats sub "flights.full.>"`.

See [Code examples](https://wingbits.gitbook.io/wingbits-ai/build/code-examples.md) for subscribing in Python, Node.js, and .NET.
