> For the complete documentation index, see [llms.txt](https://bikecheck.gitbook.io/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bikecheck.gitbook.io/guide/riders/sell-a-bike.md).

# Sell a bike

You list a bike for sale from the bike itself. The ad shows the bike's full record — parts and service history — so buyers know what they're getting.

## List the bike

1. Open the bike's page in your **Garage** and choose **Sell**.
2. Set the **asking price** and its currency.
3. Under **Where the bike is**, pick the county and city where a buyer can see it. The country comes from your account.
4. Write a **description** of at least 20 characters: condition, history, what's included, why you're selling.
5. Add **photos**. The bike's card photo is always the ad's first picture; add more of your own.
6. Choose **List for sale**.

![Listing Lena's Turbo Levo for sale](https://3342305839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUV849rO8Um1JqzscvFEf%2Fuploads%2Fgit-blob-b7008375b1ad91d7f02ffcd3c85a5ba3265cd5f5%2Fsell.jpg?alt=media)

Each listing uses a **marketplace stall**; the window shows how many you use, for example *Market stalls: 0/1 in use*. If you have no free stall, BikeCheck tells you before you start. Stalls come with Premium or with codes — see [Premium and garage slots](/guide/riders/subscription.md).

## When a buyer is interested

1. Buyers press **Contact seller** and may add a message. You get a notification.
2. On the bike's page, open the interest you received and **accept** the buyer you want to talk to. Only then can they see your contact details.
3. Arrange the viewing, price and payment directly with the buyer. BikeCheck doesn't handle the money.
4. Changed your mind about that buyer? **Call off the deal** — the listing reopens to others.

## Hand the bike over

When you've agreed, hand the bike over with a [transfer](/guide/riders/transfer-a-bike.md) to the buyer's ID. The transfer closes the ad automatically.

To take the ad down without selling, choose **Close ad** on the bike's page. **Edit ad** changes the description and the extra photos.


---

# 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://bikecheck.gitbook.io/guide/riders/sell-a-bike.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.