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

# Introduction

Artificial intelligence is becoming one of the largest consumers of computing resources.

Every time an AI model answers a question, writes code, analyses information, generates an image, or powers an autonomous agent, inference is taking place.

Inference is where AI becomes useful.

Today, access to inference is largely controlled by individual AI providers. Users and developers pay for API calls, subscriptions, or computing resources directly.

Cerebro introduces another model.

Instead of treating AI as completely separate from the crypto economy, Cerebro creates a system where economic activity can help fund access to AI inference.

The first step is the Cerebro Inference Rewards System.

Trading activity generates fees. A portion of those fees is allocated toward AI inference credits. Eligible holders can earn those credits and use them to access supported AI infrastructure.

From there, Cerebro expands into a launchpad and eventually an open inference marketplace.


---

# 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/introduction.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.