> For the complete documentation index, see [llms.txt](https://docs.fairmarkit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fairmarkit.com/buyers/auctions/english-classic-auction.md).

# English (classic) auction

In an English auction, you list the items or services you need to purchase, and suppliers submit bids in real time. Suppliers can see how their bid ranks against others and decide whether to adjust their bid to stay competitive. At the end of the event, you select the winning supplier based on price and other factors. This is the original reverse auction format.

### How English (classic) auctions work <a href="#howenglishclassicauctionswork" id="howenglishclassicauctionswork"></a>

#### Open the auction

Create your auction by adding line items and inviting suppliers.

#### Suppliers submit bids

Suppliers place bids and can see how their bid ranks against others. They can adjust their prices throughout the auction to stay competitive.

#### Award the auction

When the auction closes, you review supplier's final bids and select the winner based on price and other factors.

### Get started <a href="#getstarted" id="getstarted"></a>

* [Create an English auction](/buyers/auctions/english-classic-auction/create-an-english-auction.md)
* [Edit an English auction](/buyers/auctions/english-classic-auction/edit-an-english-auction.md)
* &#x20;[Review and award an English auction](/buyers/auctions/english-classic-auction/review-and-award-an-english-auction.md)

<br>


---

# 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.fairmarkit.com/buyers/auctions/english-classic-auction.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.