> 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/rewards.md).

# Rewards & Wallets

Your rewards are shown in the "Rewards ($WINGS)" box at the top left of the [Overview](https://wingbits.com/dashboard) page:

* "Claimable" is what you can claim now. Click "Claim rewards" to [claim it](https://docs.wingbits.com/general-help/rewards/claiming-rewards.md).
* "Other balances" shows what is still pending (in the 7 day grace period) and what you have already claimed.
* "This week" compares your rewards with the 7 days before.

Rewards for a day are calculated after midnight UTC, so they show up the next day.

The [Wallets](https://wingbits.com/dashboard/wallets) page is where you add your owner wallet and see your rewards history:

* "Earnings overview" shows what you have earned, what you can claim now, what is still pending and what you have claimed.
* "Reward Details" breaks your rewards down by day, station and source.
* "Ledger" lists every change to your balance, including claims. Click a claim's amount to see its breakdown by station.

Both tables can be downloaded with the "Export CSV" button.


---

# 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/rewards.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.
