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

# Integration

AgeGO offers two integration paths, depending on the level of control and flexibility you need.

* **Overlay (client-side):** A drop-in JavaScript snippet that renders an overlay on top of your pages and masks content until verification is complete. Fastest to launch, minimal or no backend work.
* **S2S (server-to-server):** A backend workflow where your server decides who and when to send to AgeGO for verification and handles callbacks. Requires development effort but offers maximum flexibility.

## <mark style="color:$primary;">How It Works</mark>

At a high level, both integration paths follow the same logical flow, with differences in how verification is triggered.

{% stepper %}
{% step %}
A visitor requests a page on your site.
{% endstep %}

{% step %}
Your site triggers AgeGO:

* **Overlay**: the JavaScript snippet displays the verification overlay directly on the page.
* **S2S**: your server redirects selected users to AgeGO for verification.
  {% endstep %}

{% step %}
AgeGO performs the configured verification checks (for example: Selfie, Credit Card, SMS).
{% endstep %}

{% step %}
Your site receives the verification result via redirect or callback and:

* grants access, or
* denies access, depending on the result.
  {% endstep %}
  {% endstepper %}

## <mark style="color:$primary;">Choose Your Integration Path</mark>

When a site is created in the AgeGO Admin Panel, site owners are presented with three integration options under **Integrate AgeGO with your website**:

![](/files/6f1aa3d1f18d14e4633e2339c90f563704a02e3d)

### <mark style="color:$info;">Modal Integration (JavaScript Snippet)</mark>

Recommended for most websites.

* Add one JavaScript snippet.
* AgeGO opens as an overlay.
* No backend setup required.
* Automatic handling of user interface and verification flow.
* Ideal for publishers, platforms, and most online services.

→ [Open Modal Integration Guide](/integration/integration/modal-integration-overlay.md)

### <mark style="color:$info;">Server-to-Server (S2S)</mark>

Recommended for platforms needing deeper control.

* Backend-driven sequence.
* You manage redirects and session validation.
* Works well for mobile apps, regulated industries, and custom flows.
* Requires handling callbacks and checking verification status.

→ [Open S2S Integration Guide](/integration/integration/s2s-integration.md)


---

# 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/integration/integration.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.