> For the complete documentation index, see [llms.txt](https://cerebro-3.gitbook.io/cerebro-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cerebro-3.gitbook.io/cerebro-docs/the-cerebro-flywheel.md).

# The Cerebro Flywheel

It’s built to feed itself. Here’s how the loop actually runs:

1. Cerebro creates real economic activity\
   ↓
2. That activity generates fees\
   ↓
3. A cut of the fees pays for AI inference\
   ↓
4. Users get inference credits\
   ↓
5. People (and developers) actually use the AI\
   ↓
6. New AI projects start building on top of it\
   ↓
7. Those projects launch via the Cerebro Launchpad\
   ↓
8. More inference providers and apps flood into the marketplace\
   ↓
9. Demand and supply both ramp up\
   ↓
10. The whole Cerebro economy gets bigger

Long-term version of the same loop:\
Capital → Inference → Applications → Demand → Marketplace → Even more inference It just keeps spinning.


---

# 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://cerebro-3.gitbook.io/cerebro-docs/the-cerebro-flywheel.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.