> 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/order-management.md).

# Order Management

How to create and manage your GPU rentals on Clore.ai.

## Creating an Order

1. Pick a server on the [marketplace](https://clore.ai/marketplace) and press **Rent**.
2. The rent dialog walks you through three steps: **choose a Docker image** (or one of your saved templates), **configure it** (ports, environment variables, SSH key, Jupyter token), and **Confirm & pay**. At the last step you either rent on-demand at the listed price or switch to **Rent on spot** and place your bid (at least 1% above the current top bid in that currency, if the server has one).
   * The image picker groups a curated line-up by use case (dev, image and video, LLM, and mining), and each image lists the VRAM, CUDA version, and download size it needs where those are known.
   * The **Cost estimate** on the Confirm & pay step shows what the rental would cost over a duration you pick and how long your balance in the chosen coin will last. The duration is only for the estimate and doesn't stop or limit the rental.
3. Confirm to pay from your balance (available currencies depend on which coins the server accepts). If you are not signed in or short on funds, you can sign in and top up right inside the dialog, no need to leave checkout.

> On servers showing an **N/M GPUs free** badge you can rent a subset of the GPUs and pick them in the GPU allocation step. See [Partial GPU Rental](/for-renters/partial-gpu-rental.md).

## Viewing Your Orders

1. Go to **My Orders** in the navigation
2. See all your active and past orders
3. Click on any order for details

### Order Statuses

| Status         | Meaning                               |
| -------------- | ------------------------------------- |
| **Pending**    | Order is being set up                 |
| **Running**    | Server is active and accessible       |
| **Completed**  | Rental period ended normally          |
| **Terminated** | Ended early (by you, host, or system) |
| **Outbid**     | Spot order - someone outbid you       |

## Order Details

Each order shows:

* Server specifications (GPU, RAM, storage)
* Connection info (IP, port, credentials)
* Start/end time
* Cost breakdown
* Logs and history

## Extending a Rental

To extend an active On-Demand order:

1. Go to **My Orders**
2. Click on your active order
3. Click **Extend**
4. Select additional hours (up to max 3000h total)
5. Confirm payment

> **Note:** Spot orders cannot be extended - create a new order instead.

## Canceling an Order

### On-Demand Orders

1. Go to **My Orders**
2. Click on the active order
3. Click **Terminate**
4. Confirm termination

You stop being charged immediately upon termination.

### Spot Orders

Same process - but remember, with Spot you can also be terminated if outbid.

## Order History

View your complete rental history:

1. Go to **My Orders**
2. Filter by status or date
3. Click on any order for full details

### Exporting History

Order history can be viewed in your account for tracking expenses and usage patterns.

## Billing & Costs

### How Billing Works

* **On-Demand:** Charged per minute while the order runs; terminate anytime to stop the charges
* **Spot:** Charged per minute at your bid price while your offer holds the server

### Cost Breakdown

Each order shows:

* Base rental cost
* Platform fee
* Total paid

> **Creation fee:** a small one-time fee applies per order (see [Fee Structure](/for-renters/fee-structure.md)). It is charged only if the order stays active longer than 10 minutes, so quickly cancelled orders pay none.

### Refunds

* Early termination: You stop paying immediately
* Server issues: Contact support for potential refunds

## Communication with Host

### In-Order Chat

1. Open your active order
2. Use the **Chat** feature
3. Communicate directly with the host

### When to Contact Host

* Server not responding
* Specs don't match listing
* Need specific configuration
* Technical issues

## Order Logs

View what happened during your rental:

1. Open order details
2. Go to **Logs** section
3. See events like:
   * Order created
   * Server started
   * Connection established
   * Termination reason

## Tips for Managing Orders

1. **Monitor active orders** - Check regularly for any issues
2. **Set budget alerts** - Track your spending
3. **Save server favorites** - For easy re-rental
4. **Review before extending** - Make sure you still need the server
5. **Terminate promptly** - Don't pay for unused time

## Common Questions

### Can I pause a rental?

No, rentals run continuously. Terminate and create a new order if needed.

### What happens if I run out of balance?

The order will be terminated after a grace period (\~5 minutes).

### Can I transfer an order to another user?

No, orders are tied to your account.

### How long until I can access a new order?

Usually 2-5 minutes after order creation.


---

# 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/order-management.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.