> For the complete documentation index, see [llms.txt](https://docs.wingbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wingbits.com/general-help/stations.md).

# Stations

All of your stations and reservations are on the [My Stations](https://wingbits.com/dashboard/stations) page. Click the 3 dots on the far right of a station to edit or delete it, manage its host or extend its reservation. The bell icon next to it sets up [station alerts](https://docs.wingbits.com/general-help/stations/station-alerts.md).

Click a station to open its page, which has these tabs:

* "Rewards History" shows the station's rewards by day. The lines over the bars show its "Base + EPR Rank" and "LAR Rank" (Low Altitude Rewards), as a percentile of the network. Higher is better, so 90% means the top 10%.
* "Map overview" shows the station on the map along with the flights it is tracking.
* "Statistics" shows the station's current health, like GPS, location and data flow.
* "Heartbeats" lists the station's check-ins (one every 10 minutes) and flags any problems.
* "Configuration" is where you set up [remote access](https://docs.wingbits.com/get-started/how-to-setup-remote-access-for-a-station.md). Only the station owner sees this tab.

Not sure what a status or warning means? See [Station status and warnings](https://docs.wingbits.com/general-help/stations/station-status.md). If your station is offline, see [Station troubleshooting](https://docs.wingbits.com/general-help/stations/station-troubleshooting.md).


---

# 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://docs.wingbits.com/general-help/stations.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.
