> For the complete documentation index, see [llms.txt](https://docs.nusa.nissology.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nusa.nissology.ai/credit-and-earnings/withdrawing.md).

# Withdrawing

{% hint style="warning" %}
**You can't withdraw during Beta.** Your earnings are recorded from your first rental and kept. Withdrawing opens after Beta; there's no date for it yet.
{% endhint %}

Until then, you can move Available earnings into Credit and rent with them. See [What hosting earns](broken://pages/78518dfe06985c61d1ba71b7e77509bd7eb2ab01#moving-earnings-into-credit).

## What can be withdrawn

Only your **Available earnings** from hosting. Credit can never be withdrawn.

## Conditions for withdrawing

These are the conditions as they stand now. They may change before withdrawing opens.

* **Each withdrawal is at least 100 USD.**
* **Your machines have been rented for 300 hours in all.** Only rentals that earned count, including rentals during Beta.
* **You can withdraw at most once a day.**

How withdrawing works, including any fee, will be explained here before withdrawing opens.


---

# 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.nusa.nissology.ai/credit-and-earnings/withdrawing.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.