> For the complete documentation index, see [llms.txt](https://docs.yottalabs.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yottalabs.ai/products/inference/gpu-worker/quickstart.md).

# Quickstart

This document provides a high-level overview of how users can set up GPU workers to join the Yotta network.

## Prerequisites

**Workers** are central to our project, especially those with the highest share in the airdrop. Anyone who meets the [minimum system requirements](https://docs.io.net/docs/supported-devices) can become a worker. For smoother job access, it's recommended to have a download/upload speed of 200–500 Mbps, meet graphics card/processor requirements, and have 16GB of RAM to avoid crashes. But not meeting these doesn't disqualify you: uptime, GPU/CPU power, and internet speed also matter. So, even if you don't get a job, you can still earn airdrop rewards as a worker. Getting a job gives you an edge, though.

## Minimum System Requirements:

* 12 GB RAM
* 256 GB Hard Drive
* Operating System: Linux/MacOS/Windows
* Networking
  * Download: 100 Mbps
  * Upload: 100 Mbps
  * Ping: 200ms
* GPUs: See [Supported Devices](/products/inference/gpu-worker/supported-devices.md)

## Create Account

The first step is to create an account on [orchestrator.yottalabs.ai](https://orchestrator.yottalabs.ai). Click `Sign Up` and choose whatever the most convenient for you.

## Link Wallet to Your Account


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.yottalabs.ai/products/inference/gpu-worker/quickstart.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.