> For the complete documentation index, see [llms.txt](https://astrai-1.gitbook.io/astrai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://astrai-1.gitbook.io/astrai/vision-and-pain-points.md).

# Vision & Pain Points

**ASTRAI** is a decentralized protocol for on-chain AI compute and model collaboration, powered by crypto-native incentives and verifiable infrastructure. It provides an open and censorship-resistant alternative to cloud monopolies, enabling:

* Distributed GPU/ASIC compute markets
* On-chain model training with contributor rewards
* Tokenized AI models with programmable royalties
* Transparent, DAO-governed infrastructure for AI

> **We believe the future of AI should be open, permissionless, and owned by its contributors.**

## **Problem Statement**

#### Centralized AI suffers from:

1. **Compute concentration**

   > AI development is restricted to those who can afford large cloud infrastructure (Big Tech), leaving independent devs and DAOs out.
2. **No creator ownership**

   > Model developers, fine-tuners, and data providers can’t claim or monetize ownership of the models they contribute to.
3. **No training incentives**

   > There is no way for regular users to earn rewards by improving, customizing, or training AI models.


---

# 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://astrai-1.gitbook.io/astrai/vision-and-pain-points.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.