# Aethir Introduction

Aethir is best described as distributed cloud compute infrastructure. It aggregates enterprise-grade GPU chips into a single global network to increase the supply of on-demand cloud compute resources for the AI, gaming, and virtualized compute sectors.

What this means is that:

1. **Enterprise GPU Owners** can unlock the potential of their underutilized GPU chips by becoming their own cloud compute provider.
2. **End Users** get access to the affordable on-demand compute resources they need to power their AI training and inferencing workloads, real-time rendering applications, and other virtualized compute operations.

### How it works <a href="#docs-internal-guid-c239a324-7fff-d86e-4dde-de30f9116232" id="docs-internal-guid-c239a324-7fff-d86e-4dde-de30f9116232"></a>

<figure><img src="/files/5Zp4tX0fLKYE0G7Okajt" alt=""><figcaption></figcaption></figure>

On the supply side, the process for resource owners is straightforward. They simply register their compute resources with the network, have the resource specifications evaluated and confirmed, and then stake $ATH to be eligible to service requests.&#x20;

On the demand side, end users submit requests to the network which are matched with the most appropriate, high-performance resources. For gaming use cases, the end users are the gamers themselves and are matched to a high-performance resource that contains their requested gaming experience.

Upon delivery and confirmation of satisfactory request completion, rewards flow from the compute buyer and the Aethir treasury to the resource owner.


---

# Agent Instructions: 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:

```
GET https://docs.aethir.com/aethir-introduction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
