POST to the applicants endpoint with first name, last name, and optionally email to create an applicant and capture the returned applicant ID
POST the document image to the documents endpoint with the applicant ID, document type enum, and side field set appropriately for single or multi-page documents
POST the selfie image to the live photos or live videos endpoint with the applicant ID
POST to the checks endpoint with the applicant ID and a reports array containing report name values for document and facial similarity
Store the returned check ID and poll or await the webhook event for check completion with a status of complete
Read the sub-result and breakdown fields on each report object to determine pass, consider, or caution outcomes
Known gotchas
Document and selfie must be uploaded before creating the check; the check creation call will fail if referenced media is missing
Facial similarity reports require a live photo or live video — a plain selfie upload to the wrong endpoint may not satisfy the liveness requirement depending on your contract tier
The check result field reflects the worst sub-result across all reports; inspect each report individually for granular pass/fail reasons
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp