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

# Stations Mobile

<figure><img src="/files/O4Nz5AOKjLOD0XTxeIG3" alt=""><figcaption><p>Own your content &#x26; Build Your Audience</p></figcaption></figure>

The Stations mobile app is launching with powerful built-in features like pay-per-view content and flexible membership tiers, giving creators the tools they need to monetize their work and engage their audiences effectively. Looking ahead, we plan to enhance the platform further with an in-app NFT marketplace, enabling creators to offer unique digital assets directly to their fans, and live streaming capabilities to foster real-time interaction and deeper connections. Stations is not just a platform—it’s a dynamic ecosystem designed to empower creators and revolutionize fan engagement.


---

# 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://docs.memusic.io/stations/stations-mobile.md?ask=<question>&goal=<endgoal>
```

`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.