Block bots
Keep automation out of your sign-up flow.
Bots do not fill in forms, they flood them. Amani identifies emulators, headless browsers and automation frameworks before capture even begins, then proves a live human with passive liveness - no puzzles for real users to solve.
The challenge
Scripted sign-ups exhaust promotions, scrape inventory and pollute your data, while CAPTCHAs punish genuine users and are increasingly solved by machines anyway.
With Amani
- Emulators and virtual devices identified pre-capture
- Headless browsers and automation frameworks flagged
- Velocity signals expose scripted mass sign-ups
- No puzzles or friction for genuine humans
- Signals returned to your own risk engine
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: Device & IP Analysis, Liveness, Email Verification, Phone Verification.with Amani Skills
# Install Amani Skills once
npx -y github:AMANI-AI-ORG/skills --global
# Then ask your coding agent:
You › Capture Amani device and IP risk signals during our web signup and pass the score to our fraud engine.
# 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();
});Block bots - common questions
Does this replace CAPTCHA?
For most flows, yes - device intelligence and liveness identify automation without asking humans to prove anything.
Will it slow down sign-up?
No. Signals are collected passively during the flow and add no perceptible time.
Can we use the signals ourselves?
Yes - every signal and score is returned in the result and via webhook for your own models.
Related use cases
Build this flow with Amani
Compose it in Studio without code, or integrate the API in an afternoon.