# Entrust Identity Verification (formerly Onfido) vs Veriff

> Entrust Identity Verification scores 62.1 (B) to Veriff's 61.1 (C) for identity verification. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/entrust-identity-verification-vs-veriff
- Markdown: https://www.anchorterminal.com/compare/entrust-identity-verification-vs-veriff.md (~2,900 tokens)
- Slim: https://www.anchorterminal.com/compare/entrust-identity-verification-vs-veriff.min.md (~680 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/entrust-identity-verification-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

Entrust Identity Verification (formerly Onfido) scores 62.1 (B) on agent readiness against Veriff's 61.1 (C), and leads in 4 of 7 scored categories. Veriff leads on security & auth, payments & pricing and maintenance & community. Both do identity verification.

- Entrust Identity Verification (formerly Onfido): grade B, 62.1/100, rank #472 of 1076. Markdown https://www.anchorterminal.com/tools/entrust-identity-verification.md · JSON https://www.anchorterminal.com/api/v1/tools/entrust-identity-verification.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

### Entrust Identity Verification (formerly Onfido) (B)

Good for: A company already contracted with Entrust that wants an agent to create applicants, start workflow runs and read reports through typed libraries and a public spec.

Ahead on:
- Reliability, 70 against 62
- Agent ergonomics, 65 against 43

Watch for: entrust.com answered 403 to every request, so the terms, privacy notice, pricing page and security.txt weren't read

### 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:
- Security & auth, 63 against 58
- Payments & pricing, 40 against 20
- Maintenance & community, 74 against 58

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


## Score by category

| Category | Weight | Entrust Identity Verification (formerly Onfido) | Veriff | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 70 | 62 | Entrust Identity Verification (formerly Onfido) +8 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 84 | 82 | Entrust Identity Verification (formerly Onfido) +2 |
| Agent ergonomics | 13% (16.2 this run) | 65 | 43 | Entrust Identity Verification (formerly Onfido) +22 |
| Security & auth | 14% (17.5 this run) | 58 | 63 | Veriff +5 |
| Payments & pricing | 10% (12.5 this run) | 20 | 40 | Veriff +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 58 | 74 | Veriff +16 |
| Transparency & trust | 7% (8.8 this run) | 70 | 67 | Entrust Identity Verification (formerly Onfido) +3 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **62.1 · B** | **61.1 · C** | |

## Facts side by side

| Fact | Entrust Identity Verification (formerly Onfido) | Veriff |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Onfido Ltd (Entrust) | 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 Entrust's terms. The OpenAPI spec and the server libraries (onfido-java, onfido-node, onfido-php, onfido-python, onfido-ruby) are 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-08-31 | 2026-10-02 |
| Terms last updated | couldn't be read | couldn't be read |
| Privacy policy last updated |  | 2026-04-16 |
| Customer content may train models | couldn't be read | yes |
| Terms restrict automated access | couldn't be read | couldn't be read |
| Terms restrict benchmarking | couldn't be read | couldn't be read |
| Terms or service can change without notice | couldn't be read | couldn't be read |
| Arbitration or class-action waiver | couldn't be read | couldn't be read |
| Popularity | 59k npm/wk, 27k PyPI/wk | 32 stars, 110k npm/wk |

## Verdicts

**Entrust Identity Verification (formerly Onfido).** The v3.6 API has a public MIT OpenAPI file, server libraries in five languages, OAuth client credentials with scopes and an 18-month deprecation notice. Entrust's own site answered 403, so terms, privacy notice, pricing and security.txt weren't read. There is no idempotency key, and live tokens need a Dashboard account with billing details.

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

### Entrust Identity Verification (formerly Onfido)

1. Use the regional host for the account (api.eu, api.us or api.ca.onfido.com/v3.6). v3.6 has no default region
2. Prefer an OAuth client with only the scopes the task needs over a live API token, and refresh the 60-minute access token
3. Stay under 400 requests a minute live and 120 in sandbox, and back off on a 429 `rate_limit` error
4. Check before retrying a POST. There is no idempotency key, so a retry can create a second applicant or check
5. Treat webhook events as duplicates or out of order, and verify `X-SHA2-Signature` over the raw body

### 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, Entrust Identity Verification (formerly Onfido) or Veriff?

Entrust Identity Verification (formerly Onfido) scores 62.1 (B) on agent readiness against Veriff's 61.1 (C), and leads in 4 of 7 scored categories. Veriff leads on security & auth, payments & pricing and maintenance & community.

### Do Entrust Identity Verification (formerly Onfido) and Veriff need an API key?

Entrust Identity Verification (formerly Onfido) takes an API key or an OAuth sign-in. Veriff needs an API key.

### Can an agent call Entrust Identity Verification (formerly Onfido) and Veriff without installing anything?

No hosted endpoint is listed for Entrust Identity Verification (formerly Onfido). No hosted endpoint is listed for Veriff.


## For agents

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

## Other comparisons with Entrust Identity Verification (formerly Onfido) or Veriff

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