> 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/renting/ending-a-rental.md).

# Ending a rental

A rental lasts for the hours you paid for. It can't be extended: to keep going, rent again once it ends.

## Before it ends

* **20 minutes before the end**, you see a warning with the exact end time. Nothing in the rental is saved after it ends, so copy anything you want to keep before then.
* **Nusa also emails you** before the end, so you know even if you're calling the API from your own code and don't have the website open.

## When the time runs out

The Playground and the API stop working, and the rental's key stops working. The machine goes back on the market for other renters.

From the screen that says the job has ended, or from **Jobs**, you can rent again. Renting again starts from the same model, and offers the same machine first if it's still available. It's a new rental, with its own price and key.

## Ending a rental early

To end a rental before its time is up, choose **End job**. Nusa asks you to confirm first: access ends at once, and **the time left isn't refunded**.

The same goes if your own connection or code stops while the machine is still running fine: that's you stopping early, not an interruption.

## When a rental ends unexpectedly

If a rental ends before its time for a reason other than you, it's refunded in full to your Credit, and you're emailed. See [Refunds](broken://pages/dd006d856fc6112506772b72512b8f2fa0fc8285).

## When Nusa ends a rental for breaking the terms

If you break Nusa's terms, Nusa can end your rental. It isn't refunded. You're told, on the website and by email. If you think it was a mistake, [contact Nusa support](mailto:support@nissology.ai) to appeal.


---

# 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/renting/ending-a-rental.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.
