> For the complete documentation index, see [llms.txt](https://crowdmuse.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://crowdmuse.gitbook.io/docs/creator-docs/how-do-creator-splits-work.md).

# How do creator splits work?

As part of the Creator Splits feature, each creator earns a percentage of revenue from the sales and secondary royalties of a product drop, based on their contribution.

Each time a product NFT is purchased via wallet or credit card, the funds flow into the smart contract, ready to be distributed to the creators involved. Read more [here](/docs/creator-docs/how-to-distribute-funds.md) about how the smart contract distributes funds.

<figure><img src="/files/Yk3QsDYJTPJqD8IiIawS" alt=""><figcaption></figcaption></figure>

Each creator involved in the collaboration are attributed onchain with programmed revenue splits and creator artifacts. The artifacts submitted by creators as part of the product creation flow can be open source or gated, depending on the creator’s product drop strategy. Once an artifact has been submitted into the CrowdmuseProduct NFT smart contract, it will forever be authenticated to that profile.&#x20;

This results in the development of onchain co-ownership models that distribute risk amongst the collective to provide asymmetric risk reward ratio: the chance of exponential return is slightly higher than dealing with financial risk individually. &#x20;

As these creator networks scale and become more open, new players entering can tap into their favorite creator libraries to compose new experiences.


---

# 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://crowdmuse.gitbook.io/docs/creator-docs/how-do-creator-splits-work.md?ask=<question>&goal=<endgoal>
```

`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.
