> For the complete documentation index, see [llms.txt](https://docs.agego.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agego.com/methods/verification-methods.md).

# Verification Methods

Age verification on websites is performed using **AgeGO’s verification methods**.

Each method is designed to determine either a user’s **exact age** or whether they fall within a **specific age range** (for example, 18+), depending on regulatory and business requirements.

An overview of all available methods can be found here:

**Age Verification Methods** → <https://www.agego.com/verification-methods>

Based on regulation and overall verification performance, AgeGO selects the verification method that best balances compliance and user experience.

## <mark style="color:$primary;">Method 1: Selfie</mark>

This method uses a **selfie-based age estimation** to assess a user’s age.

In some cases, an additional **government-issued photo ID** may be required to increase confidence or meet regulatory expectations.

## <mark style="color:$primary;">Method 2: Selfie + ID</mark>

This method combines a **live selfie** (with liveness detection) and a mandatory **government-issued photo ID** to fully verify a user’s age.

## <mark style="color:$primary;">Method 3: Credit Card</mark>

This method uses **credit card authorization** to confirm that a user is **18 years old or over**.

## <mark style="color:$primary;">Method 4: Digital ID</mark>

This method relies on a **third-party digital identity application**, such as **Yoti Digital ID**.

Requirements:

1. A smartphone or webcam.
2. A government-issued photo ID.

## <mark style="color:$primary;">Save Your Verification (New Users)</mark>

Once a user has successfully verified their age with any of the methods listed above, AgeGO displays the **Save Your Verification** screen before they continue to your website.

Saving the verification creates an AgeGO account, so the user can confirm their verified status on future visits without repeating the full verification process, see [AgeGO Log In below](#agego-log-in-returning-users).

The user can save their verification with:

* **Passkey** – set up a passkey on their device
* **Google** – link their Google account
* **Email** – enter their email address and confirm a one-time code

Or select **Skip For Now** to go straight to your website. In that case, age verification will be required again on their next visit.

{% tabs %}
{% tab title="Passkey" %}
The passkey flow depends on the device the user verified on.

**On a mobile device**

* The user taps **Passkey**.
* The device’s native passkey prompt appears.
* Once confirmed, the user continues to your website.

**On a desktop**

* The user clicks **Passkey**.
* A QR code is displayed. The user scans it with their mobile device.
* The AgeGO page opens on the mobile device and the native passkey prompt appears.
* Once confirmed on mobile, the user continues to your website.

If the passkey isn’t created for any reason, the user can try again, generate a new QR code, or select **Skip For Now** and continue to your website.

{% hint style="info" %}
A passkey can also be added later from the user’s My Account page.
{% endhint %}
{% endtab %}

{% tab title="Google" %}

* The user selects **Google**.
* The user signs in with their Google account.
* The Google account is linked to the user’s AgeGO profile and the user continues to your website.
  {% endtab %}

{% tab title="Email" %}

* The user enters their email address and selects **Continue**.
* A one-time AgeGO code is sent to the provided email address.
* The user enters the received code.
* The verification is saved and the user continues to your website.
  {% endtab %}
  {% endtabs %}

## <mark style="color:$primary;">AgeGO Log In (Returning Users)</mark>

Once a user has verified their age and saved their verification, they can log in on subsequent visits to confirm their previously verified status without repeating the full verification process.

When a user visits a website that uses AgeGO, they select “**Log In**” on the age-verification home screen.

The user can log in with:

* **Passkey** – if previously set up
* **Google** – the Google account linked to their AgeGO profile
* **Email** – a one-time code sent to their email address

{% tabs %}
{% tab title="Passkey" %}

* The user selects **Passkey**.
* **On mobile:** the device’s native passkey prompt appears.
* **On desktop:** the **Log In With Passkey** screen opens with a QR code. The user scans it with the mobile device that holds their AgeGO passkey and confirms the prompt there.
* Access to your website is granted.
  {% endtab %}

{% tab title="Google" %}

* The user selects **Google**.
* The user signs in with the Google account linked to their AgeGO profile.
* Access to your website is granted.
  {% endtab %}

{% tab title="Email" %}

* The user enters their email address and selects **Continue**.
* A one-time AgeGO code is sent to the provided email address.
* The user enters the received code.
* Access to your website is granted.
  {% endtab %}
  {% endtabs %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.agego.com/methods/verification-methods.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.