Veriff vs Vouched

Veriff

Per-verification prices are public from $0.80, with a 15-day trial of 50 sessions and no card. Each endpoint page is Markdown with an OpenAPI 3.0 fragment. There is no server SDK, MCP server or idempotency key, most calls need an HMAC signature, and the status page shows nine incidents between 20 July and 7 October 2026.

Vouched

Vouched publishes per-transaction prices from $0.75 with a $300 monthly minimum and a 14-day trial, and its docs carry llms.txt, OpenAPI fragments and filterable job search. Rate limits have no number, there is no idempotency key, server SDK or security.txt, and the API status page shows a 70-minute rise in rejections on 1 October 2026.

Veriff

1. Take the base URL from the integration's API keys page. Send X-AUTH-CLIENT on every call and store verification.id from POST /v1/sessions
2. Sign POST and PATCH bodies, and the session ID on GET and DELETE, with HMAC-SHA256 in X-HMAC-SIGNATURE. POST /v1/sessions needs no signature
3. Stay under 30 session creations a minute on Self-Serve, 600 on Enterprise. A 429 carries code 1004
4. Don't blindly retry POST /v1/sessions. Each call makes a new session, which is billed on a live integration
5. Poll GET /v1/sessions/{id}/decision until verification is not null, or accept webhooks within 5 seconds and treat duplicates as normal

Vouched

1. Use the private key in X-API-Key against verify.vouched.id or verify.eu.vouched.id, matching the account's region
2. Check Find Jobs before resubmitting. There is no idempotency key and each job is billed
3. Pass withPhotos=false and select fields on Find Jobs to keep responses small
4. In a test account, use the name test pass for a clean result and any other name for a failure
5. Back off on 429. All endpoints share one limit and no figure is published