> For the complete documentation index, see [llms.txt](https://doc.auditx.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.auditx.net/features/revenue-sharing-model/distribution-mechanics.md).

# Distribution Mechanics

To ensure a smooth and equitable distribution process, we’ve implemented clear mechanics powered by smart contracts:

1. **Revenue Sources:**
   * Rewards come from multiple streams, including audits, API integrations, and other **AuditX** services. As these streams diversify and expand, the reward pool will grow proportionally.
2. **Automated Distribution:**
   * A secure and **fully automated smart contract** handles the revenue sharing process, eliminating human errors and ensuring accuracy.
3. **Payout Frequency:**
   * Rewards are distributed **monthly**, providing regular, predictable income for token holders.
4. **Transparency in Operations:**
   * Every calculation, distribution, and detail is logged and displayed on the **AuditX dashboard**, ensuring token holders have full visibility into the process.
5. **Dynamic Allocation:**
   * The reward pool allocation adapts based on the revenue generated and the number of participants, maintaining consistency and fairness.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://doc.auditx.net/features/revenue-sharing-model/distribution-mechanics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.