> For the complete documentation index, see [llms.txt](https://docs.openbisea.com/dexstudio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbisea.com/dexstudio/business-model.md).

# Business model

#### DEX Studio's business model is structured as follows:

* 65% of the revenue is generated from our flagship games, MotoDEX and DexGO, reflecting the core profitability derived from our game offerings.
* 10% comes from DTOKEN, showcasing the significance of our native token in contributing to the overall revenue stream.
* D Chain contributes 15% to the revenue, emphasizing the importance of our blockchain infrastructure in driving financial success.
* The remaining 10% is attributed to the Accelerator, underlining its role in fostering innovation and contributing to the studio's overall financial landscape.

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


---

# 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.openbisea.com/dexstudio/business-model.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.