> For the complete documentation index, see [llms.txt](https://whitepaper.frak.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.frak.id/zhong-wen-ban-ben-the-sybel-ecosystem-white-paper/xi-bei-er-sheng-tai-xi-tong/chuang-shi-ji/why-the-sybel-ecosystem.md). # Why the Sybel Ecosystem? There are already dozens of projects around for Creators, mainly for musical artists. But none of them bring what **The Sybel Ecosystem** offers: * A total decentralization of economic rewards, but also a decentralization of the governance of the ecosystem. Token holders can decide the level of revenue sharing with Creators with no minimum nor maximum (*see details below*). They can choose the economic models to access content (subscription, free, advertising, one-time payment, gamification...). They can also choose the features to be developed. But above all, they can profit from all the benefits offered by the platform. All of this is impossible with social tokens platforms or music NFTs marketplaces. * No go to market phase: **The Sybel Ecosystem** has already revenue and this revenue is shared with Creators. * The possibility to fractionalize their content to allow their community and investors to own a part of the Creator's Work and engage with 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://whitepaper.frak.id/zhong-wen-ban-ben-the-sybel-ecosystem-white-paper/xi-bei-er-sheng-tai-xi-tong/chuang-shi-ji/why-the-sybel-ecosystem.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.