> For the complete documentation index, see [llms.txt](https://build-ai.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://build-ai.gitbook.io/docs/buildai-revenue-sharing-overview.md).

# BuildAI Revenue Sharing Overview

**Revenue Distribution Strategy:**

**·   30% Buybacks and Burns:** A significant portion of the revenue, 30%, will be allocated towards buybacks and burns of our tokens, enhancing value for all stakeholders.

**·    40% Marketing:** To ensure our growth and visibility in the competitive landscape, 40% of the revenue will be invested back into marketing.

**·    30% Development:** Continuing to innovate and improve our offerings, 30% of our revenue will fund ongoing development efforts.

 

**Revenue Streams:**

* **Build Extension**: The Build Extension offers premium features and includes a transaction fee of 0.3% on each transaction processed. This creates a steady revenue stream while delivering value to our users.
* **AI Agents**: BuildAI’s AI Agents will operate on a **subscription model**, offering advanced AI-driven capabilities to enhance productivity and creativity. Businesses and individuals can subscribe to access AI Agents’ powerful features, creating a recurring revenue stream for the platform.


---

# 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://build-ai.gitbook.io/docs/buildai-revenue-sharing-overview.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.