Alloy vs Vouched

Alloy

Alloy's public docs cover journeys, evaluations, entities, documents, cases and investigations, with llms.txt, Markdown pages, OpenAPI fragments and rate-limit headers with retry-after. Access is sales-led with no public price or trial, credentials have no scopes, there is no idempotency key or server SDK, and inputs vary by each customer's workflow.

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.

Alloy

1. Get the account's base URL from the customer. Defaults are api.alloy.co and sandbox.alloy.co, and some accounts have their own hosts
2. Use unique, prefixed external IDs in sandbox. Sandbox and Production share one data store
3. Read alloy-ratelimit-remaining, and on 429 or 5xx wait for retry-after with exponential backoff and jitter
4. Expect running after about 25 seconds on journey applications and wait for the webhook instead of resubmitting
5. Send the workflow header with account-level keys, since inputs depend on the workflow configured

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