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

# Premium and garage slots

Every rider starts on the **Basic** plan. **Subscription** in the menu shows your plan and what you can add.

## What Premium adds

* more **garage slots**, so you can register more bikes;
* more setups on each suspension sheet (five instead of two);
* marketplace stalls for selling bikes (the Basic plan has none of its own — a code can add one).

The price shown on the page already includes your **seniority discount**: the longer you have been on BikeCheck, the less Premium costs.

## Upgrade

1. Open **Subscription**.
2. Read and tick the consent boxes.
3. Choose **Upgrade to Premium** and pay in the secure checkout.

## Extra garage slots

Need room for one more bike without Premium, or beyond it? Choose **Add a garage slot**. Slots are billed monthly; adding one to an existing slot subscription is prorated.

## Cancel

* **Cancel subscription** stops renewal. You keep Premium until the end of the period you have paid for.
* **Keep your subscription** undoes a scheduled cancellation.
* **Cancel garage slots** stops renewal of your extra slots. There is no refund; you keep them until the end of the paid period.
* **Update payment method** changes the card on file.

## Codes

A BikeCheck code can add garage slots, marketplace stalls or a discount. Enter it in **Settings** under **Redeem a code**.


---

# 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/subscription.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.