Integrate AU10TIX for document authentication and selfie liveness verification
domain: identity-general · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain AU10TIX API credentials and the base URL for your assigned environment from the AU10TIX onboarding team
Create a transaction by POSTing to the transaction creation endpoint with customer reference data and the desired verification mode
Submit the document front image, optionally the document back image, and the selfie image to the respective image submission endpoints using the transaction ID
Trigger processing by calling the analyze or process endpoint for the transaction
Poll the transaction status endpoint or receive the result via the configured webhook when processing is complete
Parse the result object for the document authenticity score, the face match score, and any alert codes indicating document anomalies
Known gotchas
AU10TIX image quality requirements are strict; images below a minimum resolution or with excessive blur will return a quality rejection rather than a processing result
Alert codes are proprietary and version-specific; maintain a mapping table from your contract documentation and update it when AU10TIX releases new code sets
Sandbox and production environments use different base URLs and credentials; confirm the correct endpoint is configured in each deployment environment
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?