> For the complete documentation index, see [llms.txt](https://organic-1.gitbook.io/organic-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://organic-1.gitbook.io/organic-docs/treasury/revenue-sources.md). # Revenue Sources Revenue is where Organic should feel different. If you’re waiting for "revenue sources" to go live, you’re already late. \ \ We’re building a system that scales communities in a decentralized way, and that platform itself becomes a service we can rent or white-label to other projects. Our AI agent is built to spot bot-like behavior and score authenticity and can be licensed to teams and agencies that care about clean growth. \ \ As the coin grows, we’ll onboard more builders, test their tools with the community, and share upside through creator fees, partner campaigns, tool subscriptions, and (later) merch/licensing. \ \ Exact terms and splits will be proposed in the open and decided by vote. If you want to see the pipeline or float ideas, jump into Discord as nothing beats asking the people building it. **Revenue Sources** * Creator fees * Studio services and partner campaigns * Tool subscriptions and bounties * Merch and licensing when ready --- # 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://organic-1.gitbook.io/organic-docs/treasury/revenue-sources.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.