# New Utility for TATSU TaτsuOS introduces the first deflationary, demand-driven utility for the TATSU token outside of staking and validator operations. Access to the platform is structured as a subscription: users burn TATSU on a monthly basis to maintain their tier, and each burn period generates a fresh set of cryptographic receipts that authorize the features included in that tier. The burn is permanent and non-refundable regardless of whether the period is renewed. ### Subscription Tiers TaτsuOS is designed around subscription tiers, each with a progressively higher monthly TATSU burn requirement and a broader feature set. Exact burn amounts will be announced at mainnet launch. ### Economic Effects **Effect 1: A direct, recurring link between adoption and token demand.** Unlike a one-time purchase, a subscription model creates a steady, predictable burn tied directly to the active installed base. As the number of active TaτsuOS deployments grows, so does the monthly burn volume — non-speculative, anchored in real usage. **Effect 2: TATSU as the unit of account for IoT platform access.** TaτsuOS denominates subscription access in TATSU rather than in fiat. The platform fee is not a dollar amount that can be quietly raised; it is a published TATSU burn requirement, transparently recorded on-chain every billing period. **Effect 3: A practical, real-world anchor for the token.** TaτsuOS gives TATSU a use that is visible, measurable, and continuous — every active subscription is a recurring source of demand tied to actual product usage rather than to speculative cycles. --- # Agent Instructions: 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: ``` GET https://tatsu.gitbook.io/tatsu-whitepaper/new-utility-for-tatsu.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.