AgeVerif

AgeVerif is a service that allows adult websites to comply with regulators by providing a fast and convenient mechanism to verify their visitors age.

We are open to partner with other age verification services allowing these to easily plug our solution into theirs.

The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119.

Definitions

• Webmaster - Also referred as "You". Website owner or administrator registered on our Webmasters Platform
• Website - A webmaster's (your) website, registered on our Webmasters Platform
• Visitor - A visitor/user accessing the website

Integrations

1. Checker Script (SDK)

A tiny 4kB script pasted on your website, allowing the visitor prove they are an adult by passing through AgeVerif's verification process or by logging into an AgeVerif account with their previously saved credentials.

Open Documentation

2. OAuth2

A more complex integration, allowing webmasters to use AgeVerif's verification process through an OAuth2 flow, without client-side scripts.

Manual Implementation Required

You must implement the OAuth2 flow manually on your application, and AgeVerif will handle the verification process.

Open Documentation

FAQ - Frequently Asked Questions

Does the Checker Script prevent my website from being crawled and indexed by search engines?

No, the checker.js script is designed to be SEO-friendly and allows search engines and AI bots like Google, ChatGPT, and Facebook to crawl and index your website.

The age verification flow is not displayed to trusted bots, ensuring your content remains discoverable in search results while still enforcing age verification for regular visitors.

Can I use the same key for multiple websites?

No, if you chose the Checker Script (SDK) integration, each website must have its own 🟢 Public Live Key. However, the key works on all subdomains of the same root domain.

E.g. A key configured for example.org will work on www.example.org and another.example.org

If you have many websites, perhaps the OAuth2 integration is a better fit, allowing you to use the same client credentials with different redirect URIs for each website or handle the redirection logic on your side via the state parameter.

Do you have an example where I can see the age verification in action?

Yes, you can see the Checker in action on our demo website: https://demo.ageverif.com

 

Additional questions?

Contact us through [email protected] if you have any questions or wish to partner with us.

Other Tools

Webmaster's external API

API for Webmasters to programmatically interact with AgeVerif services like creating and updating many websites.

Open Documentation