> 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-payments-by-subscribers.md). # TXRS Payments by Subscribers Subscribers use TXRS to pay for receiving the Trend AI Bot Digests they have subscribed to. As mentioned above the price for each Digest is determined by the Data Provider, hence creating a healthy competition among them. Because as of yet there exists no accepted way of implementing recurring payments on-chain, the TXRS staked by Data Providers also serves as a security for Subscribers that they will receive their Digests in the future. Let's assume a Data Provider sets up a Trend AI Bot to which users subscribe and pay for a period of 6 months in advance. If the Data Provider decides to take down this specific Trend AI Bot after 3 months, Subscribers are being compensated for their overpayment from the TXRS staked by the Data Provider. That way staking and payment in TXRS for setting up and subscribing to Trend AI Bots creates an ecosystem that is self-contained and sustainable. --- # 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-payments-by-subscribers.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.