> For the complete documentation index, see [llms.txt](https://seat-airlines.gitbook.io/seat-airlines-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://seat-airlines.gitbook.io/seat-airlines-docs/the-cabin/boarding-pass.md).

# Your boarding pass

The one part of the page made to leave it — screenshot it.

Your boarding pass is in the **Check in** section, and it fills in the moment you are seated. It is built to be screenshotted.

| Field              | What it shows                                                                      |
| ------------------ | ---------------------------------------------------------------------------------- |
| **Passenger**      | Your wallet address, shortened — or **Standby** before you check in                |
| **Flight**         | SA350                                                                              |
| **Seat**           | The seat your holding earned, such as **8A** — or **—** in the hold                |
| **Class**          | FLIGHT DECK, FIRST, BUSINESS, EXIT ROW or ECONOMY — or **STANDBY**                 |
| **Boarding group** | 1 for the flight deck and First, 2 for Business, 3 for the Exit Row, 4 for Economy |
| **Boarded at**     | The altitude, in feet, when you were seated on this visit                          |

**Boarded at** is the altitude you boarded at, not the live one, and that is what makes a pass worth keeping: it records the market cap at the moment you took your seat.

Under the tear line:

* **A barcode drawn from your seat number** — the same seat always gets the same bars, and no two seats look alike.
* **Your cabin's line** — see [Cabins and seats](/seat-airlines-docs/the-cabin/cabins-and-seats.md#what-your-boarding-pass-says). Seats **30B** and **30E** get their own: *Middle seat, last row, by the lavatory. Does not recline. Merch this.*
* Without a seat: *No seat claimed. You are on the standby list.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://seat-airlines.gitbook.io/seat-airlines-docs/the-cabin/boarding-pass.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.