> For the complete documentation index, see [llms.txt](https://docs.clore.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.clore.ai/for-renters/how-to-use-templates-mass-rent.md).
# How to use templates (Mass rent)
{% hint style="info" %}
Template management has moved since these screenshots were taken: you now add, edit, and delete templates from the marketplace sidebar, pick saved ones from the **My templates** tab at the image step of the rent dialog, and quick-rent with the selected template. The general idea below still applies.
{% endhint %}
1\. Navigate to the [Clore Marketplace](https://clore.ai/marketplace).
2\. Select the preferred server from which you would like to start your rental.
3\. Click the “Rent” button next to the chosen server.
4\. Configure your server image. For this example, select Ubuntu Jupiter.
5\. Once the configuration is complete, click “Save Template.”
6\. Assign a name to your template and click “Create.”
7\. Return to the [Clore Marketplace](https://clore.ai/marketplace), and you will now see a template icon.
8\. Click “Use Templates,” then pick your template and hit “Use for Rent.”
9\. Click on every desired server. The rental process will automatically begin.
---
# 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.clore.ai/for-renters/how-to-use-templates-mass-rent.md?ask=&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.
