> For the complete documentation index, see [llms.txt](https://mediax.gitbook.io/mediax/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mediax.gitbook.io/mediax/platform-revenue-and-sources.md). # Platform Revenue and Sources MediaX's revenue model is largely consistent with traditional streaming platforms. However, the integration of Web3.0 technology significantly enhances the efficiency of revenue generation and shortens the economic settlement cycle compared to traditional streaming methods. This allows for faster revenue recycling and maximizes user capital utilization. Creator Economy * Revenue from short films and videos * Tip income IP Creation and Media Placement * Revenue from IP sales * IP copyright benefits Advertising Revenue * Revenue from cryptocurrency project promotions * Revenue from exchange event promotions * Revenue from other forms of Web3.0 ecosystem promotions Traffic Revenue * Earning revenue through traffic guidance services * Earning revenue through traffic distribution and transportation * Earning revenue through traffic interaction with project ecosystems AI Traffic Distribution * Importing external traffic through the MediaX Protocol * Earning revenue from traffic arbitrage and aggregation * Leveraging high-quality AI resources to obtain cheaper computing resources --- # 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://mediax.gitbook.io/mediax/platform-revenue-and-sources.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.