Gig worker verification
Verify every worker before the first shift.
Your platform is only as trusted as the person who turns up. Amani verifies worker identity and right to work in minutes, then uses biometric re-authentication to confirm the same verified person is the one accepting jobs.
The challenge
Gig platforms onboard at volume and lose workers to slow checks - while account sharing and rented profiles put customers and licences at risk.
With Amani
- Worker identity verified in minutes, at scale
- Right-to-work documents captured and validated
- Account sharing stopped by periodic face checks
- Duplicate and banned worker re-registration blocked
- Audit evidence for platform-liability requirements
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: KYC, Biometric Re-authentication, Face Match 1:N, Address Verification.with Amani Skills
# Install Amani Skills once
npx -y github:AMANI-AI-ORG/skills --global
# Then ask your coding agent:
You › Add Amani KYC to our React signup page using the Web SDK - ID capture plus selfie liveness, then handle the approved webhook in our Node backend.
# 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();
});Gig worker verification - common questions
How do you stop workers sharing accounts?
Periodic or shift-start selfie checks confirm the verified worker is the person actually working, with liveness blocking photo attacks.
Can we verify right to work?
Yes - document capture and validation support right-to-work and equivalent regimes; see our Employee onboarding use case.
How fast is onboarding at volume?
Automated decisions return in seconds, and journeys scale from hundreds to millions of workers without re-integration.
Related use cases
Build this flow with Amani
Compose it in Studio without code, or integrate the API in an afternoon.