> For the complete documentation index, see [llms.txt](https://docs.w.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.w.ai/compute-rentals/introduction.md).

# Introduction

**Introduction to w\.ai Compute Rentals**

w\.ai offers an innovative solution for accessing rental Jupyter Notebook and SSH containerized environments, allowing users to leverage powerful AI and machine learning frameworks using w\.ai points. With options like Apple's MLX for Python and NVIDIA's Torch with CUDA for transformers and other advanced computations, these environments provide flexible compute capabilities. Workers on the network can seamlessly make their resources available for rent around the globe, earning w\.ai points upon successful rental completions. This approach enables distributed compute resources to drive AI research and development, optimizing both resource utilization and user engagement.<br>

* [Rent Compute](https://app.w.ai/compute)
* [Contribute as a w.ai worker](https://download.w.ai)
* [w.ai Compute Rental Service Terms](https://app.w.ai/compute/terms)
* [Learn about Jupyter Notebooks](https://docs.jupyter.org/en/latest)
* [Learn about SSH](https://docs.w.ai/compute-rentals/ssh)

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

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

```
GET https://docs.w.ai/compute-rentals/introduction.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.
