> For the complete documentation index, see [llms.txt](https://snaps-docs.gitbook.io/white-paper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://snaps-docs.gitbook.io/white-paper/watch-to-earn.md).
# Watch to Earn
{% hint style="info" %}
The Snaps mobile app is in development. All the elements shown in this White Paper will be updated to the start of beta testing.
{% endhint %}
Snaps provides a financial model, in which not only content creators but also ordinary viewers can now monetize their time in the app.
Just view your short video feed, like the videos, subscribe to your favorite content creators and earn energy points for every action you take. Once a day your energy points will be automatically converted into $SNPS tokens and transferred to your wallet. You may sell these tokens, withdraw them to any other wallet in the BEP-20, withdraw them to any CEX. In other words, you may store tokens wherever you feel comfortable. Or you can lock in your profit immediately by selling the tokens.
This is your reward for your time given to our product, and you can use it as you wish!
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://snaps-docs.gitbook.io/white-paper/watch-to-earn.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.