# Entrust Identity Verification (formerly Onfido) vs Jumio

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

- Canonical: https://www.anchorterminal.com/compare/entrust-identity-verification-vs-jumio
- Markdown: https://www.anchorterminal.com/compare/entrust-identity-verification-vs-jumio.md (~2,950 tokens)
- Slim: https://www.anchorterminal.com/compare/entrust-identity-verification-vs-jumio.min.md (~780 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/entrust-identity-verification-vs-jumio.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 Jumio's 55 (C), and leads in 5 of 7 scored categories. Jumio leads on security & auth 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
- Jumio: grade C, 55/100, rank #713 of 1076. Markdown https://www.anchorterminal.com/tools/jumio.md · JSON https://www.anchorterminal.com/api/v1/tools/jumio.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 65
- Schema & documentation, 84 against 73
- Agent ergonomics, 65 against 45
- Payments & pricing, 20 against 0
- Transparency & trust, 70 against 60

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

### Jumio (C)

Good for: An enterprise with a Jumio contract that wants document, selfie and liveness checks, watchlist screening and Latin American, Thai and Australian database checks behind OpenAPI-described endpoints.

Ahead on:
- Security & auth, 63 against 58
- Maintenance & community, 75 against 58

Watch for: No public price, free tier or trial. OAuth2 and workflow keys are activated by a Jumio account manager


## Score by category

| Category | Weight | Entrust Identity Verification (formerly Onfido) | Jumio | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 70 | 65 | Entrust Identity Verification (formerly Onfido) +5 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 84 | 73 | Entrust Identity Verification (formerly Onfido) +11 |
| Agent ergonomics | 13% (16.2 this run) | 65 | 45 | Entrust Identity Verification (formerly Onfido) +20 |
| Security & auth | 14% (17.5 this run) | 58 | 63 | Jumio +5 |
| Payments & pricing | 10% (12.5 this run) | 20 | 0 | Entrust Identity Verification (formerly Onfido) +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 58 | 75 | Jumio +17 |
| Transparency & trust | 7% (8.8 this run) | 70 | 60 | Entrust Identity Verification (formerly Onfido) +10 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **62.1 · B** | **55 · C** | |

## Facts side by side

| Fact | Entrust Identity Verification (formerly Onfido) | Jumio |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Onfido Ltd (Entrust) | Jumio Corporation |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Paid | Paid |
| 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. No public service agreement was found. The @jumio/websdk npm package is marked UNLICENSED |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-08-31 | 2026-09-28 |
| Terms last updated | couldn't be read | no document linked |
| Privacy policy last updated |  | 2026-08-04 |
| Customer content may train models | couldn't be read | yes |
| Terms restrict automated access | couldn't be read |  |
| Terms restrict benchmarking | couldn't be read |  |
| Terms or service can change without notice | couldn't be read |  |
| Arbitration or class-action waiver | couldn't be read |  |
| Popularity | 59k npm/wk, 27k PyPI/wk | 72 stars, 2.1k 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.

**Jumio.** Five OpenAPI 3.0 files, an llms.txt index and OAuth2 clients limited to initiating or to retrieving and deleting make the API readable and containable. Access starts with an account manager, with no public price, trial or service agreement, and the status page shows four processing degradations and a 35-minute Singapore outage between 14 August and 2 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

### Jumio

1. Use the host for the tenant's region (amer-1, emea-1 or apac-1). Tokens come from auth.<region>.jumio.ai/oauth2/token with the client ID and secret as Basic credentials
2. Reuse the bearer token for its 60 minutes. Token requests are limited to 10 a second and new transactions to 1 a second per tenant
3. Send a User-Agent header on every call. The Account API marks it required
4. Don't blindly retry POST /api/v1/accounts. Each call creates an account and a transaction, and no idempotency key exists
5. Wait for the callback or poll the status endpoint until PROCESSED before retrieving. Jumio's retry schedule starts at 40 seconds and stops after 940

## Questions

### Which is better for AI agents, Entrust Identity Verification (formerly Onfido) or Jumio?

Entrust Identity Verification (formerly Onfido) scores 62.1 (B) on agent readiness against Jumio's 55 (C), and leads in 5 of 7 scored categories. Jumio leads on security & auth and maintenance & community.

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

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

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

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


## For agents

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

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

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