# Glossary

This section defines the key roles and terms used throughout the AgeGO documentation.

#### <mark style="color:$info;">AgeGO Business Account</mark>

A business account created to access AgeGO services, configure Sites, and manage integrations. This account is intended for **clients** (businesses) and not for end users.

#### <mark style="color:$info;">Client</mark>

A business, publisher, platform, or service provider that integrates AgeGO as an age-verification solution on their website or application. Clients are responsible for integrating AgeGO and enforcing age restrictions according to applicable regulations.

#### <mark style="color:$info;">Cross-site Automatic Verification</mark>

A mechanism that allows a previously verified user to be recognized across multiple AgeGO-enabled Sites using a secure verification token, reducing the need for repeated age-verification prompts.

#### <mark style="color:$info;">End User</mark>

An individual who visits a website or application that uses AgeGO and is asked to verify their age in order to access age-restricted content or services.

#### <mark style="color:$info;">Returning User</mark>

An end user who has already completed age verification and can be recognized without repeating the full verification flow, depending on the integration and session context.

#### <mark style="color:$info;">Site</mark>

A website or application operated by a Client and integrated with AgeGO.

Each Site is identified by a unique ASI value and represents a single integration context.

#### <mark style="color:$info;">Underage User</mark>

An end user who does not meet the required age threshold and is therefore denied access to age-restricted content or services.

#### <mark style="color:$info;">Verification Flow</mark>

The sequence of steps an end user goes through once age verification is triggered, from the initial prompt to a successful or failed outcome.

#### <mark style="color:$info;">Verification Method</mark>

A specific mechanism used by AgeGO to assess whether an end user meets the required age threshold (for example: selfie-based estimation, credit card verification, or digital identity checks).


---

# Agent Instructions: 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:

```
GET https://docs.agego.com/general/glossary.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.