> For the complete documentation index, see [llms.txt](https://docs.deep3.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.deep3.ai/the-business/token-design.md).
# Token Design
Our ecosystem is built around a dual-token model that not only facilitates seamless transactions and access to our cutting-edge AI models but also gives users a meaningful stake in our platform’s success.
At its core, our ecosystem comprises two distinct tokens: the governance token (gD3L) and the utility token (uD3L). The governance token enables community participation in key decisions—ranging from model updates to economic policies—while the utility token powers day-to-day transactions within the marketplace, from purchasing AI models to collateralizing submissions. Complementing these tokens is our innovative staking program, which rewards active participants and ensures that real contributors are recognized in our rapidly evolving digital landscape. Graphically, the ecosystem can be summarized as follows:
Together, all of these components create a dynamic, self-sustaining economy that not only drives the adoption of AI on Web3 but also puts control and value directly in the hands of its users.
{% embed url="" %}
---
# 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.deep3.ai/the-business/token-design.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.