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

# View and manage your bids on Ornn

> Track submitted bids from the Portfolio Bids page, view bid details and lifecycle status, update or withdraw editable bids, and understand what happens after acceptance.

Every bid you submit through the reservation flow is tracked under your Portfolio. The **Bids** page gives you a full view of submitted and in-flight offers so you can monitor their progress, update them while they're still editable, or withdraw them before they're reviewed.

## The Bids list

Open **Portfolio → Bids** to see all bids your tenant has submitted. Each row shows:

* **GPU label and quantity**: the GPU model and count you bid on.
* **Operator and site**: the provider and facility associated with the inventory.
* **Term**: the start and end dates you requested.

Selecting a row previews the bid in the right-hand panel, where the current lifecycle status appears as a chip and as a **State** field (see below). The row's **View** link and the panel's **View full bid** link both open the full bid detail page.

<Info>
  If you have no bids yet, the page shows an empty state with a **Reserve now** link. Browse inventory to submit a new bid.
</Info>

## Bid lifecycle and statuses

Bids move through a defined lifecycle. The web app and CLI both surface the underlying status value. The web UI renders underscores as spaces and capitalizes the first letter.

| Label                   | Meaning                                                                     | Underlying status     |
| ----------------------- | --------------------------------------------------------------------------- | --------------------- |
| **Pending deposit**     | The bid was submitted but the down-payment hasn't settled yet.              | `pending_deposit`     |
| **Active**              | Down-payment is settled. The bid is live and visible to the Ornn team.      | `active`              |
| **Accepted**            | The Ornn team accepted the bid. Accepted GPU count and price are locked in. | `accepted`            |
| **Reservation created** | The accepted bid was promoted to a confirmed reservation in your portfolio. | `reservation_created` |
| **Rejected**            | The bid was not accepted.                                                   | `rejected`            |
| **Withdrawn**           | You withdrew the bid before it reached a terminal outcome.                  | `withdrawn`           |
| **Expired**             | The bid timed out before being accepted or rejected.                        | `expired`             |

<Note>
  Acceptance and reservation creation are separate steps. A bid first becomes **Accepted**, and is then promoted to **Reservation created** when the confirmed reservation appears in your portfolio.
</Note>

## Bid detail page

Click **View** on a bid row to open the bid detail page. It shows the full record:

<ResponseField name="bid_price_per_gpu_hour" type="number">
  The price per GPU-hour you offered, in USD.
</ResponseField>

<ResponseField name="gpu_count" type="integer">
  The number of GPUs you requested in the bid.
</ResponseField>

<ResponseField name="min_gpu_count" type="integer">
  The minimum GPU count you stated you would accept. May be `null` if you did not set a minimum.
</ResponseField>

<ResponseField name="start_date" type="date">
  The requested start date for the reservation term.
</ResponseField>

<ResponseField name="end_date" type="date">
  The requested end date for the reservation term.
</ResponseField>

<ResponseField name="status" type="string">
  The current lifecycle status (`pending_deposit`, `active`, `accepted`, `reservation_created`, `rejected`, `withdrawn`, or `expired`).
</ResponseField>

<ResponseField name="accepted_at" type="datetime">
  When the bid was accepted. `null` if it has not been accepted.
</ResponseField>

<ResponseField name="accepted_gpu_count" type="integer">
  The GPU count locked in at acceptance. May differ from `gpu_count` if a minimum was applied. `null` if not yet accepted.
</ResponseField>

## Updating a bid

You can update a bid while it is **Pending deposit** or **Active** (that is, before it's accepted, rejected, withdrawn, or expired).

<Steps>
  <Step title="Open the bid detail page">
    Open **Portfolio → Bids** and click **View** on the bid you want to change.
  </Step>

  <Step title="Edit the bid terms">
    Update the GPU count, minimum GPU count, start date, end date, or price per GPU-hour.
  </Step>

  <Step title="Save your changes">
    Submit the form. All bid fields are saved together; partial updates aren't supported.
  </Step>
</Steps>

## Withdrawing a bid

To withdraw an editable bid, open the bid detail page and click **Withdraw bid**. The status changes to **Withdrawn** and the bid is closed permanently; withdrawn bids cannot be reopened.

<Warning>
  Update and withdraw are only available while the bid is **Pending deposit** or **Active**. Once it's **Accepted**, **Reservation created**, **Rejected**, **Withdrawn**, or **Expired**, no further changes are possible.
</Warning>

## What happens after acceptance

When the Ornn team accepts a bid:

1. The status changes to **Accepted** and `accepted_at` and `accepted_gpu_count` are recorded.
2. The accepted bid is later promoted to a confirmed reservation. At that point the status becomes **Reservation created** and the reservation appears in your **Portfolio** under the **Active** or **Upcoming** view, with details at `/portfolio/[reservationId]`, where you can configure access.

From the moment the reservation is created, you manage the reservation, not the bid. If a bid is accepted at a partial GPU count (`accepted_gpu_count < gpu_count`), the reservation reflects only the accepted count.

## CLI equivalents

Every action on this page maps to a Ornn Compute CLI command:

```bash theme={null}
ornn bid list                     # list all bids your tenant has submitted
ornn bid show <bid-id>            # view a bid's full record
ornn bid show <bid-id> --open     # open the bid in the web app
ornn bid update <bid-id> ...      # update an editable bid (all fields required)
ornn bid withdraw <bid-id>        # withdraw an editable bid
```

Use `--json` on any read command for scripted workflows. See the [Ornn Compute CLI](/cli) for full syntax.

## Secondary market

Ornn supports resale of confirmed reservations through a secondary market. If you hold a reservation you no longer need, you can list it for sale and recover spend on the unused portion.

See [Resell reservations on the secondary market](/guides/resale) for the full workflow.

## What's next

<CardGroup cols={2}>
  <Card title="Portfolio overview" img="https://mintcdn.com/ornn/fNQRwmmR9H-yzza5/images/banners/portfolio.jpg?fit=max&auto=format&n=fNQRwmmR9H-yzza5&q=85&s=f8319c8193ef1d8a2fd406d1c8235280" href="/guides/portfolio-overview" width="1200" height="800" data-path="images/banners/portfolio.jpg">
    View your active reservations, check connection details, and monitor GPU utilization.
  </Card>

  <Card title="Track GPU usage and invoices" img="https://mintcdn.com/ornn/fNQRwmmR9H-yzza5/images/banners/usage-and-billing.jpg?fit=max&auto=format&n=fNQRwmmR9H-yzza5&q=85&s=b2a4aaa944da57d94715dd80942df3f4" href="/guides/usage-and-billing" width="1200" height="800" data-path="images/banners/usage-and-billing.jpg">
    Understand GPU-hour utilization, recent job history, and how to find and pay your invoices.
  </Card>
</CardGroup>