> For the complete documentation index, see [llms.txt](https://docs.rad.live/rad/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rad.live/rad/getting-started-creators-studios-publishers/sell-subscription-video.md).

# Sell Subscription Video

Add Your Content to Rad TV's Premium Subscription to Reach an Existing Audience

[Approved Creators](/rad/getting-started-creators-studios-publishers/get-approved-for-subscription-payments.md) have the option to monetize content through Rad TV's Premium Subscription.[ ](/rad/getting-started-creators-studios-publishers/become-an-approved-creator-legacy.md)

* The Premium Subscription pays creators on a percentage basis of the minutes watched of their content.
* Only Rad TV Premium Subscribers are able to view content included in the Premium Subscription. 

For example, Rad TV splits the monthly subscription revenue 70/30 with creators. 70% for the creators and 30% for Rad TV. That 70% is then split among all Approved Creators included in the subscription based on minutes watched. If you're a creator whose content is watched 20% of the total minutes for the month, you will receive 20% of the 70% set aside each month for creators.

[Become an Approved Creator](/rad/getting-started-creators-studios-publishers/get-approved-for-subscription-payments.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.rad.live/rad/getting-started-creators-studios-publishers/sell-subscription-video.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.