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

# Glossary

| Term                                 | Meaning                                                                                                                   |
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------- |
| **Bike log**                         | A bike's permanent history: registration, services, part changes, corrections and ownership changes. It is never deleted. |
| **Booking**                          | A request for a shop to work on a bike, from Pending to checked out.                                                      |
| **Check-in code**                    | The rider's one-time 8-digit code, read to the shop when dropping a bike off.                                             |
| **Pickup code** / **check-out code** | The shop's one-time 8-digit code, typed in by the rider when collecting the bike.                                         |
| **Custody**                          | Who has the bike right now: the owner, or a shop while it is checked in.                                                  |
| **EUID**                             | A business's registration number in the official business register.                                                       |
| **Fleet**                            | Bikes a business owns and uses.                                                                                           |
| **Fleet rider**                      | A team member who rides one fleet bike.                                                                                   |
| **Frame serial**                     | The number stamped on the frame. It is the bike's identity on BikeCheck and can't be changed.                             |
| **Garage slot**                      | Room for one bike in a rider's garage.                                                                                    |
| **KYC**                              | Identity verification for a person.                                                                                       |
| **KYB**                              | Verification of a business against the official business register.                                                        |
| **Marketplace stall**                | Room for one listing on the marketplace.                                                                                  |
| **Seniority discount**               | A lower subscription price the longer an account has been on BikeCheck.                                                   |
| **Showroom**                         | Bikes a business sells.                                                                                                   |
| **Staff seat**                       | Room for one team member (or one unused invite code) in a business.                                                       |
| **Step-up**                          | A password check before an action that can't be undone, such as a transfer.                                               |
| **Transfer token**                   | A one-time code, valid 15 minutes, that lets one named person claim a bike.                                               |
| **Unique ID**                        | Your public account ID (`BC-USR-…`), shared to receive a transfer.                                                        |
| **Walk-in**                          | A customer served without a booking, often without an account.                                                            |


---

# 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/reference/glossary.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.
