> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gpuoutlet.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Reserve and confirmation requests

> What the Reserve button on a Radar card does, when it appears, and how it differs from requesting confirmation or bidding.

**Reserve** starts a deal on one listing. Pressing it puts your demand in front of that listing's seller as an opportunity. The seller sees what you need but not who you are. If they accept, the two companies are introduced and contract directly.

Reserving does not set capacity aside, and nothing is charged. GPU Outlet takes no money for a deal at any point. The contract that secures the hardware is the one you sign with the seller after the introduction.

## The three buttons on a card

Each [Radar](/buying/radar) card carries one button. Which one you see follows from the listing.

| Button | When it appears | What it does |
| - | - | - |
| **Reserve** | The seller is verified and has proven the right to sell this capacity, and the listing states a minimum term. | Offers your demand to this listing's seller as an opportunity. |
| **Bid Now** | A lot on this listing is taking bids. | Opens the lot, where you bid. See [Bidding](/buying/bidding). |
| **Request confirmation** | The listing is **Indicative**: nobody has proven a right to sell it yet. | Opens the listing's page, where you can state your demand for it as a request. |

<Note>
  **Reserve** needs a stated minimum term. A deal has to have a length, and neither side can size one from a listing that names none. A seller who wants the button on their listing states the minimum term on it. See [Listings](/selling/listings).
</Note>

## Reserve a listing

<Steps>
  <Step title="Press Reserve">
    A dialog opens with the listing's details already filled in: the number of nodes, the start date and the term.
  </Step>

  <Step title="Adjust what you need">
    Change the number of nodes, the start date or the term if they differ from the listing. The dialog keeps you inside what the listing offers: no more nodes than it has, no start before it is available, and no term shorter than its minimum. A demand outside those would be one the listing has already refused.

    You can add a note for the GPU Outlet team. The seller does not see it: the seller reads your demand without your company's name, and free text is where a name slips in.
  </Step>

  <Step title="Send it to the seller">
    Your demand is created as a request of your company and offered to this seller. You land on that request, where its status shows it is with the seller.
  </Step>
</Steps>

Reserving the same listing twice does not send the seller a second offer. While your first one is still open, pressing **Reserve** again takes you back to it.

## What happens next

* **The seller accepts.** Both companies are introduced: you see the seller in [Introductions](/buying/introductions), and they see you. From there you agree the contract directly.
* **The seller declines.** Nobody is told who asked. Your request returns to open, and the GPU Outlet team can match it to other listings.
* **The seller has not signed their agreement yet.** They can see your opportunity but must sign before they can accept it. Their side tells them so.

## Request confirmation

On an **Indicative** listing the seller has not yet proven the right to sell the capacity, so there is nothing to reserve. **Request confirmation** opens the listing's page instead. There, **Request this capacity** starts a request with the GPU and region filled in from the listing, and the GPU Outlet team takes it forward once the capacity is confirmed.

## Reserve, or a request?

* **Reserve** is about one listing you have already found. It goes to that listing's seller only.
* A **request** states what your company needs without naming a listing. The GPU Outlet team matches it to listings from any seller. See [Requests](/buying/requests).

Both end the same way: a seller accepts, and you are introduced.

## Related

<CardGroup cols={2}>
  <Card title="Radar" icon="radar" href="/buying/radar">
    Browse listings and read what each card shows.
  </Card>

  <Card title="Bidding" icon="gavel" href="/buying/bidding">
    What to do when a listing is sold by auction.
  </Card>

  <Card title="Requests" icon="file-lines" href="/buying/requests">
    State what your company needs and be matched to sellers.
  </Card>

  <Card title="Introductions" icon="handshake" href="/buying/introductions">
    What you see once a seller accepts.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.