> 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/getting-started/verify-your-identity.md).

# Verify your identity

Riders can use BikeCheck without verifying their identity. You can register bikes, book services, log your own work, sell bikes and receive bikes as an unverified rider.

A few actions need a verified identity, because other people rely on them:

* rating a shop's mechanics, or the other side of a bike transfer;
* being hired by a shop (joining as a mechanic, receptionist or fleet rider);
* reporting a bike as stolen;
* creating a parent consent code for a child under 18.

When you try one of these without being verified, BikeCheck takes you to verification instead of showing an error.

## How verification works

1. Choose **Verify my identity** where BikeCheck offers it.
2. You are taken to our verification partner. Follow the steps on your phone or computer: you photograph an identity document and take a short selfie.
3. When the check is approved you return to BikeCheck, and you get a notification and an email.

Once you are verified, your name comes from your document and can't be edited in Settings. If your legal name changes, use **My legal name changed** in Settings to verify again.

{% hint style="info" %}
Businesses are different: a shop must complete **business verification** before it can operate. See [Register your business](/guide/shop-owners/register-your-business.md).
{% 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/getting-started/verify-your-identity.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.