Proof of human
Prove there is a real person behind the account.
AI made fake users indistinguishable from real ones on paper. Amani proves a unique, living human is behind an account - passive liveness confirms presence, and 1:N search confirms they are not already registered ten times over.
The challenge
Bot farms and AI-generated identities inflate user numbers, poison communities, drain incentives and distort every metric you rely on.
With Amani
- Live human presence proven at sign-up
- One-human-one-account enforced biometrically
- AI-generated faces and deepfakes rejected
- Bot and automation frameworks detected pre-capture
- Genuine users complete in seconds
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: Liveness, Face Match 1:N, Device & IP Analysis.with Amani Skills
# Install Amani Skills once
npx -y github:AMANI-AI-ORG/skills --global
# Then ask your coding agent:
You › In the forgot-password flow, verify identity with the Amani KYC Core SDK (selfie liveness) on iOS before allowing a reset.
# 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();
});Proof of human - common questions
Does this require identity documents?
Not necessarily - liveness and uniqueness can prove humanness anonymously, with documents added only if you need legal identity.
How do you catch AI-generated faces?
Liveness models are retrained continuously on new generative tools and detect synthesis artefacts plus injection attacks at the capture layer.
Can it stay anonymous?
Yes - proof-of-human deployments can run without storing identity data, keeping only what you need.
Related use cases
Build this flow with Amani
Compose it in Studio without code, or integrate the API in an afternoon.