Age verification
Keep minors out without carding everyone.
Most of your users are obviously old enough. Amani estimates age from a liveness-checked selfie in under a second, lets clearly-eligible users straight through, and asks only near-threshold faces for a document.
The challenge
Requiring ID from every user destroys conversion and creates a honeypot of personal data - yet age-assurance regulation is tightening across gambling, adult content and social media.
With Amani
- Instant age checks without documents for most users
- Buffer thresholds ensure minors never slip through
- Anonymous operation possible for content gates
- Liveness prevents minors using an adult’s photo
- Document step-up only where genuinely needed
The stack
Modules powering this flow.
Switch these on in Amani Studio - or call them directly from one API.
For developers
Build this flow.
Three API calls start the session; the modules above run inside it. Compose the journey in Amani Studio without code, or let your AI coding agent wire up the SDK from a single prompt.
- JWT auth with refresh tokens
- Regional base URLs (EU · TR · UAE)
- HMAC-signed webhooks with retries
- 27 languages in the SDKs
verify.sh
# 1 · Authenticate (server-side only)
curl -X POST 'https://ae.amani.ai/api/v2/user/login/' \
--form 'username="you@company.com"' \
--form 'password="••••••••"'
# 2 · Create the customer profile
curl -X POST 'https://ae.amani.ai/api/v2/profile' \
-H 'Authorization: Bearer $ACCESS_TOKEN' \
--form 'id_card_number="784199012345678"' \
--form 'name="Layla Haddad"'
# 3 · Generate the verification URL
curl -X POST 'https://ae.amani.ai/api/v2/profile/url' \
-H 'Authorization: Bearer $ACCESS_TOKEN' \
-H 'Content-Type: application/json' \
--data '{
"profile": PROFILE_ID,
"web_sdk_url": "https://verify.amani.ai",
"language": "en",
"return_url": "https://yourapp.com/verified"
}'
# This session runs: Age Estimation, Liveness, ID Verification, KYC.with Amani Skills
# Install Amani Skills once
npx -y github:AMANI-AI-ORG/skills --global
# Then ask your coding agent:
You › Add an Amani age check to our web signup that only asks for ID when the estimate is near our threshold.
# The matching skill fetches the live docs, pins the
# current SDK version and wires up the integration -
# secrets left as placeholders. Claude Code, Cursor and
# any Agent-Skills-compatible tool.webhooks.ts
// Amani signs every webhook with an HMAC signature using
// your secret. Always verify it before processing.
import crypto from 'node:crypto';
app.post('/webhooks/amani', (req, res) => {
// Confirm the exact header name in the Webhooks API reference.
const signature = req.get('X-Amani-Signature') ?? '';
const expected = crypto
.createHmac('sha256', process.env.AMANI_WEBHOOK_SECRET)
.update(req.rawBody)
.digest('hex');
const valid =
signature.length === expected.length &&
crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected));
if (!valid) return res.status(401).end();
const { profile, status } = req.body;
if (status === 'approved') activateAccount(profile);
res.status(200).end();
});Age verification - common questions
How accurate is age estimation?
Estimation returns an age range, and you set a buffer band so anyone close to your threshold is routed to a document check. The buffer is what keeps minors out, not the estimate on its own.
Do you store the user’s face?
Only if you configure it. Pure age-gate deployments run statelessly - estimate, decide, discard.
Does this satisfy regulators?
Buffer-based estimation with document step-up is the pattern accepted by major age-assurance regimes; we help map it to your specific obligation.
Related use cases
Build this flow with Amani
Compose it in Studio without code, or integrate the API in an afternoon.