> 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/cerebro.md).

# Cerebro

## The Economic Layer for AI Inference

AI is becoming a major part of how software is built and used. Behind every model, agent, and AI application is inference, the computing needed to actually run the model.

Cerebro is building around that market.

The idea is to connect AI inference with an onchain economy, starting with $CEREBRO and expanding into a wider ecosystem for AI projects, inference providers, and users.

Cerebro is being developed in three stages:

#### 01 | AI Inference Rewards

Trading activity generates fees, with a portion used to provide AI inference credits to eligible holders.

#### 02 | AI Inference Launchpad

The next step is a launchpad for projects building around AI inference, giving them a way to launch, grow, and build their own token economies around AI usage.

#### 03 | AI Inference Marketplace

The final stage is an open marketplace connecting inference providers with the people, applications, and agents that need AI compute.

Cerebro starts with a simple use case: turning activity around a token into access to AI. From there, the goal is to build the infrastructure for a much larger inference economy.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cerebro-3.gitbook.io/cerebro-docs/cerebro.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.