> For the complete documentation index, see [llms.txt](https://codico-dispatch.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codico-dispatch.gitbook.io/documentation/locations-and-rules/airports.md).
# Airports
Add the airports you serve and set the meeting point for passengers.
The **List of Airports** holds every airport you serve. Open it with **Locations & Rules → List of Airports**.
The List of Airports (demo data).
The list shows the **Airport ID**, **Airport name**, **Address**, **Location** (coordinates) and the date it was **Created**. Use **Search** to find an airport, **Add new** to add one, **Edit** to change it and **Delete** to remove it.
## Add or edit an airport
| Field | What it does |
| ------------- | --------------------------------------------------------------------------- |
| **Name** | The airport name, for example *Brussels Airport (BRU) - Belgium*. Required. |
| **Meetpoint** | Where the driver meets the passengers. |
| **Order** | The display order of the airport. |
| **Location** | The airport's position on the map. Required. |
Each airport is linked to a zone in **Custom Zones/Areas**. The form shows the **Linked zone**. If the airport is no longer linked to a zone, use the button in the form to create a new zone for it. This does not change the existing zone, which you remove manually in [Custom Zones](/documentation/locations-and-rules/custom-zones.md) if you no longer need it.
## Companies that serve the airport
Click **Operators** in the airport form to see the companies that serve this airport, with their **Direction** and whether they are the **Main** company. You can add or remove companies here. The same list is maintained per company in **People & Companies → Companies**. See [Companies](/documentation/people-and-companies/companies.md#list-of-airports-that-you-service).
---
# 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://codico-dispatch.gitbook.io/documentation/locations-and-rules/airports.md?ask=&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.
