ComplyCube vs Vouched

ComplyCube

A sandbox with its own key and scripted outcomes, a public OpenAPI spec, Markdown docs and an audit log API suit an agent running verification checks. Each environment has one unscoped key, no idempotency keys were found, and the only published terms are undated and read as website terms.

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.

ComplyCube

1. Send the key bare in the Authorization header, with no Bearer prefix. Keys start test_ or live_
2. Create a client first, then documents or live photos for it, then POST /v1/checks with the client and upload IDs
3. Stay under 10 requests a second live and 5 in the sandbox. On 429, back off exponentially with jitter, starting at 30 seconds
4. A badly formed filter returns 200 with no results, so check filter names before trusting an empty list
5. Checks are asynchronous. Subscribe to webhooks, verify the ComplyCube-Signature HMAC-SHA256 header, and expect duplicate and out-of-order events

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