> For the complete documentation index, see [llms.txt](https://docs.taurusbot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taurusbot.io/the-taurus-trend-ai-ecosystem/txrs-utility.md). # TXRS Utility Data Providers will earn TXRS on the usage of the Trend AI Agents that they provide to the community on the Taurus AI Marketplace. The Marketplace being a venue of open community engagement, Data Providers will set the price for subscription of their Trend AI Agents themselves which again helps to hold up healthy competition on the Marketplace. Taurus AI suggests that Data Providers choose a price level that will compensate them duly for the initial effort needed to set up a Trend AI Agent that is of relevance to the community. At the same time Data Providers should keep in mind a price threshold that should not be crossed in order for their Trend AI Agents to be still economically rewarding for their Subscribers. If in doubt—check out the communities acceptance for a specific Trend AI Agent at a given price. Data Providers need to stake a specific amount of TXRS to make sure quality guidelines are being met. Obvious rules are the ones that common sense dictate like no token shilling, no mere advertising, no offensive or illegal content, no political content etc. If content quality guidelines are violated Taurus AI reserves the right to slash part or all of the TXRS token amount which has been staked for a given Trend AI Agent. It is also important to note the each Data Provider by setting up a Trand AI Agent agrees to indemnify Taurus AI from all claims by third parties in connection with the infringement of copyright or any other intellectual or material rights that may be harmed by Trend AI Agents set up by them. --- # 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.taurusbot.io/the-taurus-trend-ai-ecosystem/txrs-utility.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.