> 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/ai-inference-rewards-system/ai-inference-credits.md).

# AI Inference Credits

Inference requires resources.

AI providers need computing infrastructure, GPUs, electricity, networking, storage, and software infrastructure to process requests.

As a result, AI usage has an economic cost.

Cerebro introduces AI inference credits as the bridge between the token economy and that cost.

Credits represent an allocation that can be used toward supported AI inference services.

Depending on the infrastructure available to Cerebro, credits may provide access to different AI models and services.

The objective is to make AI access a utility generated by participation in the Cerebro ecosystem.

#### No staking required

The intended design is for the wallet itself to represent the user's participation.

Users do not necessarily need to lock their tokens into a separate staking contract simply to qualify for inference rewards.

Eligibility and distribution are determined by the protocol.


---

# 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/ai-inference-rewards-system/ai-inference-credits.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.