Face Match 1:N
Find duplicates and watchlisted faces at scale.
Fraudsters don’t sign up once. Face Search 1:N compares every new face against your existing user base and watchlists - surfacing duplicate accounts, previously banned users and known bad actors before they get a second chance.
Capabilities
What Face Match 1:N gives you.
Duplicate-account detection
New sign-ups searched against every enrolled face to stop multi-accounting and bonus abuse.
Internal watchlists
Maintain banned-user galleries; a returning fraudster is flagged the moment their face reappears.
Millisecond search
Vector search across millions of enrolled faces returns candidates in real time, inline with onboarding.
Configurable galleries
Segment collections by product, region or risk tier, with retention rules per gallery.
Human-review handoff
Candidate matches presented side-by-side with scores for fast, defensible adjudication.
Privacy-first storage
Faces stored as irreversible templates, encrypted, with deletion honoured across every gallery.
From session to signed result.
Four steps - the same integration pattern as every Amani module.
Create a session
One API call (or a Studio journey) starts a verification session for this module.
User completes the flow
Your customer is guided through capture in your branded UI - web or mobile.
Checks run in real time
Face Match 1:N executes alongside any other modules in the journey.
You receive a signed result
A webhook delivers the decision, scores and evidence to your backend.
For developers
Integrate Face Match 1:N.
Authenticate, create a profile, generate a verification URL - then let Amani handle the rest. Or describe what you want to your AI coding agent and let Amani Skills wire it up from the live docs.
Available on
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"
}'
# Face Match 1:N runs inside this session - configure it in Amani Studio.with Amani Skills
# Install Amani Skills once
npx -y github:AMANI-AI-ORG/skills --global
# Then ask your coding agent:
You › On signup, run an Amani face search against our existing users to block duplicate accounts.
# 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();
});Face Match 1:N - common questions
How many faces can a gallery hold?
Galleries scale to tens of millions of templates with millisecond search - sized to your user base on Enterprise plans.
Is this compliant with privacy law?
Faces are stored as non-reversible biometric templates with consent capture, retention limits and deletion APIs to support GDPR-class obligations.
What’s the difference from 1:1?
1:1 answers “is this the same person as this reference?”; 1:N answers “have we ever seen this face before?” - deduplication and watchlisting rather than binding.
Related modules
Add Face Match 1:N to your flow
Switch it on in Amani Studio, or call it directly from the API.