# Ecosystem  (Flywheel)

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

This flywheel demonstrates the self-reinforcing cycle of the $GRAFI ecosystem, where each component drives growth and value for the next, creating a continuous loop of demand, rewards, and adoption.

1. **AI Agents:** These are the AI Application and Agents utilizing the Grafilab ecosystem, including AI models and developers. As more usesrs, create more demands. Their activity generates demand for GPU resources and infrastructure.
2. **Grafi GPU Cloud Inference API:** This component fulfills the demand by providing scalable GPU power for AI tasks, enhancing the capabilities of AI agents and models. More demand leads to more revenue for the ecosystem.
3. **$GRAFI Token:** Revenue generated from GPU usage is tied to the $GRAFI token. Increased demand for services drives token value and usage within the ecosystem.
4. **Contributors:** Token rewards and economic incentives attract contributors such as GPU owners and developers, who supply GPU power and contributions to the network. This strengthens the infrastructure.&#x20;
5. **Co-Builder:** Contributors and resources support the Co-Builder platform, enabling the deployment and scaling of AI models. This increases value creation and rewards for developers and contributors.&#x20;
6. **More Deployment & Rewards:** As more AI models and applications are deployed, the ecosystem grows, attracting additional users and generating further demand.


---

# Agent Instructions: 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:

```
GET https://docs.grafilab.io/home/whitepaper/ecosystem-flywheel.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
