# Alloy vs Veriff

> Veriff scores 61.1 (C) to Alloy's 52.4 (D) for identity verification. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/alloy-vs-veriff
- Markdown: https://www.anchorterminal.com/compare/alloy-vs-veriff.md (~2,450 tokens)
- Slim: https://www.anchorterminal.com/compare/alloy-vs-veriff.min.md (~680 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/alloy-vs-veriff.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-14

Veriff scores 61.1 (C) on agent readiness against Alloy's 52.4 (D), and leads in 6 of 7 scored categories. Alloy leads on agent ergonomics. Both do identity verification.

- Alloy: grade D, 52.4/100, rank #782 of 1076. Markdown https://www.anchorterminal.com/tools/alloy.md · JSON https://www.anchorterminal.com/api/v1/tools/alloy.json
- Veriff: grade C, 61.1/100, rank #512 of 1076. Markdown https://www.anchorterminal.com/tools/veriff.md · JSON https://www.anchorterminal.com/api/v1/tools/veriff.json
- Best identity and business verification APIs for AI agents: https://www.anchorterminal.com/best/identity-verification/index.md
- All 119 verification comparisons: https://www.anchorterminal.com/compare/identity-verification/index.md

## Which one, for what

### Alloy (D)

Good for: Banks and fintechs that already run onboarding through Alloy and want an agent to submit journey applications, read decisions and work investigations.

Ahead on:
- Agent ergonomics, 52 against 43

Watch for: No public prices, trial or self-serve sign-up. Access starts with a demo request

### Veriff (C)

Good for: A team that needs document and selfie verification with public per-verification prices and a trial, and that can run a webhook receiver and HMAC signing.

Ahead on:
- Schema & documentation, 82 against 73
- Security & auth, 63 against 49
- Payments & pricing, 40 against 0
- Transparency & trust, 67 against 62

Watch for: No server-side SDK and no MCP server. Official packages cover only browser and mobile capture


## Score by category

| Category | Weight | Alloy | Veriff | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 59 | 62 | Veriff +3 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 73 | 82 | Veriff +9 |
| Agent ergonomics | 13% (16.2 this run) | 52 | 43 | Alloy +9 |
| Security & auth | 14% (17.5 this run) | 49 | 63 | Veriff +14 |
| Payments & pricing | 10% (12.5 this run) | 0 | 40 | Veriff +40 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 72 | 74 | Veriff +2 |
| Transparency & trust | 7% (8.8 this run) | 62 | 67 | Veriff +5 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **52.4 · D** | **61.1 · C** | |

## Facts side by side

| Fact | Alloy | Veriff |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | First Mile Group, Inc. (Alloy) | Veriff OÜ |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Paid | Pay per use |
| x402 | no | no |
| Licence | Proprietary service under Alloy's terms of service. The @alloyidentity/web-sdk capture package is MIT | Proprietary service. The npm capture SDKs are ISC (@veriff/js-sdk, @veriff/incontext-sdk) and MIT (@veriff/react-native-sdk) |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-05 | 2026-10-02 |
| Terms last updated | 2026-03-12 | couldn't be read |
| Privacy policy last updated | no date given | 2026-04-16 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | yes | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | yes | couldn't be read |
| Popularity | 21k npm/wk | 32 stars, 110k npm/wk |

## Verdicts

**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.

**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.

## Before you call either

### 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

### 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

## Questions

### Which is better for AI agents, Alloy or Veriff?

Veriff scores 61.1 (C) on agent readiness against Alloy's 52.4 (D), and leads in 6 of 7 scored categories. Alloy leads on agent ergonomics.

### Do Alloy and Veriff need an API key?

Alloy takes an API key or an OAuth sign-in. Veriff needs an API key.

### Can an agent call Alloy and Veriff without installing anything?

No hosted endpoint is listed for Alloy. No hosted endpoint is listed for Veriff.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/alloy-vs-veriff.json, and with the fewest tokens: https://www.anchorterminal.com/compare/alloy-vs-veriff.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "alloy", "b": "veriff"}`. From a terminal: `anchor compare alloy veriff`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/alloy.json and https://www.anchorterminal.com/api/v1/tools/veriff.json

## Other comparisons with Alloy or Veriff

- [Alloy vs ComplyCube](https://www.anchorterminal.com/compare/alloy-vs-complycube.md)
- [Alloy vs Didit](https://www.anchorterminal.com/compare/alloy-vs-didit.md)
- [Alloy vs Entrust Identity Verification (formerly Onfido)](https://www.anchorterminal.com/compare/alloy-vs-entrust-identity-verification.md)
- [Alloy vs Jumio](https://www.anchorterminal.com/compare/alloy-vs-jumio.md)
- [Alloy vs Middesk](https://www.anchorterminal.com/compare/alloy-vs-middesk.md)
- [Alloy vs Persona](https://www.anchorterminal.com/compare/alloy-vs-persona.md)
- [Alloy vs Plaid Identity Verification](https://www.anchorterminal.com/compare/alloy-vs-plaid-identity-verification.md)
- [Alloy vs Shufti](https://www.anchorterminal.com/compare/alloy-vs-shufti.md)
- [Alloy vs Socure RiskOS](https://www.anchorterminal.com/compare/alloy-vs-socure-riskos.md)
- [Alloy vs Stripe Identity](https://www.anchorterminal.com/compare/alloy-vs-stripe-identity.md)
- [Alloy vs Sumsub](https://www.anchorterminal.com/compare/alloy-vs-sumsub.md)
- [Alloy vs Trulioo](https://www.anchorterminal.com/compare/alloy-vs-trulioo.md)
- [Alloy vs Vouched](https://www.anchorterminal.com/compare/alloy-vs-vouched.md)
- [ComplyCube vs Veriff](https://www.anchorterminal.com/compare/complycube-vs-veriff.md)
- [Didit vs Veriff](https://www.anchorterminal.com/compare/didit-vs-veriff.md)
- [Entrust Identity Verification (formerly Onfido) vs Veriff](https://www.anchorterminal.com/compare/entrust-identity-verification-vs-veriff.md)
- [Jumio vs Veriff](https://www.anchorterminal.com/compare/jumio-vs-veriff.md)
- [Middesk vs Veriff](https://www.anchorterminal.com/compare/middesk-vs-veriff.md)
- [Persona vs Veriff](https://www.anchorterminal.com/compare/persona-vs-veriff.md)
- [Plaid Identity Verification vs Veriff](https://www.anchorterminal.com/compare/plaid-identity-verification-vs-veriff.md)
- [Shufti vs Veriff](https://www.anchorterminal.com/compare/shufti-vs-veriff.md)
- [Socure RiskOS vs Veriff](https://www.anchorterminal.com/compare/socure-riskos-vs-veriff.md)
- [Stripe Identity vs Veriff](https://www.anchorterminal.com/compare/stripe-identity-vs-veriff.md)
- [Sumsub vs Veriff](https://www.anchorterminal.com/compare/sumsub-vs-veriff.md)
- [Trulioo vs Veriff](https://www.anchorterminal.com/compare/trulioo-vs-veriff.md)
- [Veriff vs Vouched](https://www.anchorterminal.com/compare/veriff-vs-vouched.md)
- [Alloy vs ComplyAdvantage](https://www.anchorterminal.com/compare/alloy-vs-complyadvantage.md)
- [ComplyAdvantage vs Veriff](https://www.anchorterminal.com/compare/complyadvantage-vs-veriff.md)