> For the complete documentation index, see [llms.txt](https://docs.fraktal.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fraktal.io/marketplace/get-started/distributing-royalties.md). # Distributing Royalties A core component of the Fraktal Protocol is distributing royalties to multiple owners. For example, 3 artists could collaborate on a piece, or a band could have multiple members each which should own a piece of the NFT they create. Fraktal splits up royalties based on ownership percentage. For example, if you own 30% of an NFT, you receive 30% of the royalty payments. This enables creators to do some very cool things such as selling a piece of their work for upfront ETH, while retaining ownership of some of it for future royalties. **Example** 3 Artists collaborate on a piece and own 33% of the NFT each. Each will receive 33% of royalties to their wallet. Now if 1 artist needs some cash, but does not have time to wait on future royalties, she could sell 10% of the NFT to her fans via a fixed-price or auction listing. This results in 2 artists owning 33%, 1 artist owning 23%, and fans owning 10%. When royalties are distributed, the artist still receives 23% of her royalites, while the fans now receive 10% in exchange for the ETH they paid to buy the Fraktions from the artist. --- # 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.fraktal.io/marketplace/get-started/distributing-royalties.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.