# ADVANCE.AI > ADVANCE.AI is the digital identity verification, KYC/KYB, AML, compliance and risk-management > business unit of Advance Intelligence Group (Singapore, founded 2016). Its public Open API at > https://api.advance.ai provides eKYC building blocks — token authentication, Global Document > Verification with OCR and ID forgery detection, face comparison, and liveness detection with > video evidence and programmatic PII deletion. Onboarding is sales-led; there is no self-service > sign-up and no published pricing. Generated by API Evangelist on 2026-09-07 from ADVANCE.AI's public documentation. ADVANCE.AI does not publish an llms.txt of its own (/llms.txt returns 404 on advance.ai, api.advance.ai and doc.advance.ai, probed 2026-09-07). ## Read this first - Every response is HTTP 200. The outcome lives in the JSON envelope field `code`, never in the HTTP status. A client that branches on HTTP status will read every failure as a success. - Branch on `code`, never on `message`. ADVANCE.AI states message text changes without notice. - Billing is per response code. Each documented code is tagged `free` or `pay`. Four face-comparison FAILURE codes are chargeable, so blind retry of a bad image costs money each attempt. - Every returned image and video URL expires after 24 hours. - Two of the three product flows require a mobile SDK step. A document verification or liveness result cannot be produced over HTTP alone — a human must present a document or a face to a phone camera. Plan around this before designing an autonomous integration. ## Authentication POST https://api.advance.ai/openapi/auth/ticket/v1/generate-token with `accessKey`, `timestamp` (13-digit epoch ms) and `signature` = SHA256(accessKey + secretKey + timestamp). Optional `periodSecond` sets lifetime (default 3600, min 60, max 86400). Pass the returned token on every other call as the `X-ACCESS-TOKEN` header. One token works across all APIs and reissuing does not invalidate an outstanding token. Keys are read from the ADVANCE.AI Websaas platform under Account > Account Management. ## Operations - Generate access token: POST /openapi/auth/ticket/v1/generate-token - Document verification license: POST /intl/openapi/face-identity/document-verification/v1/auth-license - Document verification result: POST /intl/openapi/face-identity/document-verification/v1/query - Face comparison: POST /openapi/face-recognition/v4/check (multipart, firstImage + secondImage) - Liveness signatureId: POST /liveness/ext/v1/generate-signature-id - Liveness license: POST /openapi/liveness/v1/auth-license - Liveness result: POST /openapi/liveness/v3/detection-result - Liveness video: GET /liveness/ext/v1/get-video?livenessId=... - Delete liveness PII: GET /liveness/ext/v1/clear-data?livenessId=... (IRREVERSIBLE — no restore) ## Interpreting scores - Face comparison `similarity` 0-100: above 70 pass, 55-70 manual check, below 55 reject. - Liveness `livenessScore` 0-100: above 50 pass, below 50 manual check. When 0, `attackType` is 1 presentation attack, 2 injection attack, 3 unsure. ## Image requirements PNG/JPG/JPEG, under 2 MB, between 256x256 and 4096x4096. For OCR the document must be readable, upright or landscape (not tilted ~45 degrees), unobscured, on a clean background. ## Rate limits and quotas No numeric limit is published. Over-limit responses carry envelope code SERVICE_BUSY or RETRY_LATER plus a `Retry-After` HTTP header (documented example: 10s). ADVANCE.AI notes SERVICE_BUSY may migrate to HTTP 429 in future. OVER_QUERY_LIMIT means the free allocation is exhausted and is not retryable. INSUFFICIENT_BALANCE means the account balance is exhausted. ## Documentation - API reference — document verification: https://doc.advance.ai/global_document_verification.html - API reference — liveness detection: https://doc.advance.ai/liveness_detection.html - API reference — face comparison: https://doc.advance.ai/face_recognition.html - Android SDK guide: https://doc.advance.ai/sdk/android/global-iqc/en/standard.html - iOS SDK guide: https://doc.advance.ai/sdk/ios/global-iqc/en/standard.html - Status page: https://status.advance.ai/ - Support: https://support.advance.ai/hc/en-us - Security and compliance: https://advance.ai/security-compliance/ - Terms of service: https://advance.ai/terms-of-service/ - Privacy policy: https://advance.ai/privacy-policy/ - Request access: https://advance.ai/book-free-demo/ ## What ADVANCE.AI does not publish No OpenAPI or Swagger document. No GraphQL, gRPC or AsyncAPI surface. No webhooks or events. No MCP server. No A2A agent card. No /.well-known/ discovery document of any kind. No server-side client library on npm, PyPI, Maven Central or any other public registry — only Android and iOS capture SDKs from ADVANCE.AI's own endpoints. No published pricing, no self-service sign-up, no idempotency mechanism, no reversal operation, no sandbox environment, and no dated API changelog. ## Profile This file and the artifacts beside it are an independent third-party profile by API Evangelist. https://apis.io/apis/advanceai/