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

# AgeGO Age Verification Solution

## <mark style="color:$primary;">Why am I seeing AgeGO?</mark>

Some websites and online services are required to verify that users are old enough to access age-restricted content or products. That’s why you may be asked to complete an age verification process powered by AgeGO.

AgeGO helps you verify your age quickly, securely, and with full respect for your privacy.

## <mark style="color:$primary;">Verify Once. Access Easily.</mark>

AgeGO makes age verification quick, simple, and privacy-friendly so you can access online content with less friction.

Verify your age for free using one of our secure [verification methods](https://help.agego.com/verification-methods.md), create your [AgeGO account](https://help.agego.com/my-account.md) in seconds, and enjoy faster access across supported websites on future visits.

* Fast and secure age verification.
* Simple and user-friendly process.
* One-time verification for future access.
* Privacy-focused and GDPR-compliant.
* [ISO& ACCS certification ](https://www.agego.com/blog/building-trust-in-age-verification-age-go-achieves-independent-iso-and-accs-certification)


---

# 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://help.agego.com/agego-age-verification-solution.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.
