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

# Welcome to BikeCheck

BikeCheck is a registry for bicycles. Every bike gets a permanent record: who owns it, which parts are fitted, and every service a shop or the owner has done. The record follows the bike when it is sold or handed on, so the next owner knows what they are buying.

On top of the record, BikeCheck connects the people around a bike:

* **Riders** register their bikes, book them into a shop, log their own work, sell them and hand them over to a new owner.
* **Shops** take service bookings, run the work on a task board, and keep their own fleet or showroom.
* **Shop staff** — mechanics, front desk and fleet riders — each get the tools for their job.

## How to use this wiki

Pick the guide for what you do:

| You are…                                | Start here                                                                                                                                                                                    |
| --------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| New to BikeCheck                        | [Create your account](/guide/getting-started/create-an-account.md), [sign in](/guide/getting-started/sign-in.md), then [find your way around](/guide/getting-started/find-your-way-around.md) |
| A rider                                 | [Register your first bike](/guide/riders/register-a-bike.md)                                                                                                                                  |
| A shop owner                            | [Register your business](/guide/shop-owners/register-your-business.md)                                                                                                                        |
| A mechanic, receptionist or fleet rider | [Join a shop](/guide/shop-staff/join-a-shop.md)                                                                                                                                               |

Each tutorial walks through one task, step by step, with screenshots from BikeCheck's test environment. The people, shops and bikes in the pictures are examples: the bikes are real models with their real factory parts, the people and shops are made up.

{% hint style="info" %}
Inside the app, the round **?** button in the bottom-right corner explains whatever is on screen — the page, or the window you have open. Use it whenever a control isn't clear.
{% endhint %}


---

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