> For the complete documentation index, see [llms.txt](https://docs.singularityfinance.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.singularityfinance.ai/market-opportunity/tokenise-monetise-and-decentralise-the-ai-economy/hardware-layer.md).

# Hardware Layer

The hardware layer serves as the backbone of AI, providing the essential processing power needed for the inference and training of AI models.

Data centres consist of a bespoke setup of land, energy sources and hardware assets such as graphics processing units (GPUs) and central processing units (CPUs) to fulfil the required computation demand. The recent exponential increase in demand for compute has opened a lucrative yield-generation opportunity in the area. Artificial Superintelligence Alliance (ASI) members SingularityNET and Fetch.ai are both investing heavily in data centres, while Cudos provides a decentralised marketplace for AI compute for data centres worldwide to access compute on the blockchain.

<br>


---

# 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://docs.singularityfinance.ai/market-opportunity/tokenise-monetise-and-decentralise-the-ai-economy/hardware-layer.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.