{ "data": { "a": { "slug": "entrust-identity-verification", "name": "Entrust Identity Verification (formerly Onfido)", "vendor": "Onfido Ltd (Entrust)", "vendorUrl": "https://www.entrust.com/products/identity-verification", "kind": "http-api", "category": "identity-verification", "summary": "Entrust Identity Verification, formerly Onfido, checks identity documents, selfies and liveness, runs watchlist and database checks and orchestrates them in Workflow Studio. Agents use the Onfido Public API v3.6 in EU, US and CA regions.", "url": "https://www.anchorterminal.com/tools/entrust-identity-verification", "markdownUrl": "https://www.anchorterminal.com/tools/entrust-identity-verification.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/entrust-identity-verification.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/entrust-identity-verification.json", "repo": "https://github.com/onfido/onfido-openapi-spec", "license": "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", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "@onfido/api" }, { "registry": "pypi", "name": "onfido-python" } ], "auth": "mixed", "authNotes": "API tokens per region and environment (`api_live.`, `api_sandbox.`, with `_us` and `_ca` variants) sent as `Authorization: Token token=\u003ctoken\u003e`, generated in the Dashboard under Developers, API authentication. From v3.6, OAuth client credentials issue 60-minute access tokens, with scopes and a per-application IP allowlist set in the Dashboard. Tokens remain valid until revoked. SDK tokens are separate and scoped to one workflow run. Live checks need billing details on the account (checked 2026-10-14).", "pricing": "paid", "pricingNotes": "No price list was readable. Entrust's pricing page answered 403. The UK G-Cloud 14 listing by Onfido Ltd gives £0.43 to £2.12 a transaction and says a free trial with sandbox access is available. Sandbox requests aren't charged (checked 2026-10-14).", "priceSummary": "Paid", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the API v3.6 reference or the OpenAPI spec (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 59334, "pypiWeekly": 26714, "asOf": "2026-10-14" }, "docsUrl": "https://documentation.identity.entrust.com/", "llmsTxt": "https://documentation.identity.entrust.com/llms.txt", "openapi": "https://github.com/onfido/onfido-openapi-spec/blob/master/openapi.yaml", "capabilities": [ "kyc.identity", "kyc.documents", "kyc.screening" ], "tags": [ "hosted", "api-key", "oauth", "openapi", "llms-txt", "webhooks", "sandbox", "status-page", "python", "typescript", "java", "ruby", "php", "soc2", "iso27001" ], "lastRelease": "2026-08-31", "graded": true, "anchor": { "graded": true, "score": 62.1, "grade": "B", "agentReady": false, "rank": 472, "ranked": true, "rankOf": 1076, "categoryRank": 8, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 65, "maintenance": 58, "payments": 20, "reliability": 70, "schema": 84, "security": 58, "transparency": 70 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "Public OpenAPI 3.0 file for v3.6 (85 operations, MIT) with official libraries in Java, Node.js, PHP, Python and Ruby", "OAuth client credentials with scopes and a per-application IP allowlist, alongside region-specific API tokens", "Rate limits stated, 400 requests a minute live and 120 in sandbox, with a free sandbox that returns predetermined results", "Written versioning policy with at least 18 months' notice before a version is deprecated", "Webhooks signed with HMAC-SHA256, retried five times over 10 hours and resendable for 30 days" ], "weaknesses": [ "entrust.com answered 403 to every request, so the terms, privacy notice, pricing page and security.txt weren't read", "No idempotency key on POST and no Retry-After header on 429", "The API release notes page has no entry after 27 February 2023", "A faulty deployment rejected valid tokens on the CA Public API for an hour on 7 September 2026", "Pricing is known only as a range of £0.43 to £2.12 a transaction from a 2024 UK G-Cloud listing" ], "agentNotes": [ "Use the regional host for the account (api.eu, api.us or api.ca.onfido.com/v3.6). v3.6 has no default region", "Prefer an OAuth client with only the scopes the task needs over a live API token, and refresh the 60-minute access token", "Stay under 400 requests a minute live and 120 in sandbox, and back off on a 429 `rate_limit` error", "Check before retrying a POST. There is no idempotency key, so a retry can create a second applicant or check", "Treat webhook events as duplicates or out of order, and verify `X-SHA2-Signature` over the raw body" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 62.1 } ], "editorialScores": { "ergonomics": 65, "maintenance": 58, "payments": 20, "reliability": 70, "schema": 84, "security": 58, "transparency": 52 }, "provenanceScore": 87 }, "connect": { "install": "pip install onfido-python" }, "letme": { "capability": "https://letme.dev/kyc.identity", "tool": "https://letme.dev/entrust-identity-verification" }, "area": "domain-data", "provenance": { "legalEntity": "Onfido Ltd", "domain": "onfido.com", "domainRegistered": "2013-02-22", "endpointOnVendorDomain": true, "terms": "https://www.entrust.com/terms-and-conditions", "privacy": "https://www.entrust.com/sites/default/files/documentation/licensingandagreements/product-privacy-notice-identity-verification-services.pdf", "statusPage": "https://status.onfido.com", "changelog": "https://documentation.identity.entrust.com/api/release-notes", "securityTxt": "unknown", "checked": "2026-10-14", "notes": [ "The UK G-Cloud 14 listing names ONFIDO LTD as supplier. The docs say Onfido is now part of Entrust.", "onfido.com/terms-and-conditions and onfido.com/privacy redirect to the entrust.com URLs above, which answered 403, so neither was read.", "onfido.com/.well-known/security.txt redirects to entrust.com, which answered 403.", "The API answers on api.{eu,us,ca}.onfido.com, an onfido.com subdomain. The docs moved to documentation.identity.entrust.com.", "RDAP for onfido.com gives a registration date of 2013-02-22." ], "score": 87 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/entrust-identity-verification.json", "live": { "slug": "entrust-identity-verification", "vendorStatus": { "page": "https://status.onfido.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-14T09:39:10.845654397Z" }, "updatedAt": "2026-10-14T09:39:10.845654397Z" } }, "answer": "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 \u0026 auth and maintenance \u0026 community.", "b": { "slug": "jumio", "name": "Jumio", "vendor": "Jumio Corporation", "vendorUrl": "https://www.jumio.com", "kind": "http-api", "category": "identity-verification", "summary": "Identity verification service from Jumio Corporation in Sunnyvale. It checks identity documents and selfies with liveness, screens against sanctions and PEP lists, and runs government database checks. Transactions are started and read through regional REST APIs with OAuth2.", "url": "https://www.anchorterminal.com/tools/jumio", "markdownUrl": "https://www.anchorterminal.com/tools/jumio.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/jumio.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/jumio.json", "repo": "https://github.com/Jumio/mobile-sdk-android", "license": "Proprietary service. No public service agreement was found. The @jumio/websdk npm package is marked UNLICENSED", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "@jumio/websdk" }, { "registry": "npm", "name": "react-native-jumio-mobilesdk" } ], "auth": "oauth", "authNotes": "Sales approval. A Jumio account manager activates OAuth2 for the tenant and supplies the workflow keys. An admin then generates client ID and secret pairs in the Jumio Portal, each limited to initiating transactions, to retrieving and deleting them, or both, and each can be deactivated. The pair is sent as Basic credentials to the regional token URL with `grant_type=client_credentials`, and the bearer token lasts 60 minutes. Basic authentication on the REST APIs themselves is marked deprecated. Account creation also returns per-transaction tokens for uploads and the capture SDKs.", "pricing": "paid", "pricingNotes": "No public prices. www.jumio.com/pricing/ returns 404 and the site's Get Started button opens a sales enquiry form. No free tier, trial or self-serve signup was found. The mock service for synthetic test transactions needs a dedicated tenant that Jumio Support or the account manager sets up (checked 2026-10-08).", "priceSummary": "Paid", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in llms-full.txt, the five OpenAPI files or the Jumio website (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 72, "npmWeekly": 2122, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://documentation.jumio.ai", "llmsTxt": "https://documentation.jumio.ai/llms.txt", "openapi": "https://documentation.jumio.ai/redocusaurus/account.yaml", "capabilities": [ "kyc.identity", "kyc.documents", "kyc.screening" ], "tags": [ "hosted", "enterprise", "oauth", "openapi", "llms-txt", "callbacks", "sales-led", "status-page", "soc2", "iso27001", "java", "dotnet" ], "lastRelease": "2026-09-28", "graded": true, "anchor": { "graded": true, "score": 55, "grade": "C", "agentReady": false, "rank": 713, "ranked": true, "rankOf": 1076, "categoryRank": 14, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 45, "maintenance": 75, "payments": 0, "reliability": 65, "schema": 73, "security": 63, "transparency": 60 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "Five downloadable OpenAPI 3.0 files covering 25 operations, plus llms.txt and a 2.2 MB llms-full.txt of the docs in Markdown", "OAuth2 client credentials with 60-minute bearer tokens. Each client is limited to initiate, to retrieve and delete, or both, and can be deactivated", "Rate limits are published per tenant. Token requests 10 a second, new transactions 1 a second, retrievals 15 a second", "Statuspage at monitor.jumio.com by data centre, and an unauthenticated health endpoint per region that answers UP, DEGRADED or DOWN", "SOC 2, ISO 27001 and PCI DSS 4.0.1 listed on the Trust Centre, and a vulnerability disclosure programme at vdp.jumio.com" ], "weaknesses": [ "No public price, free tier or trial. OAuth2 and workflow keys are activated by a Jumio account manager", "No service agreement or DPA is published. The public terms of use cover end users in the United States", "Four processing degradations and a 35-minute Singapore outage on the status page between 14 August and 2 October 2026", "No idempotency key. A repeated POST or PUT on accounts starts another transaction", "GET /api/v1/workflow-executions takes no paging or filter parameters, and the specs document only 401, 403 and 404 errors", "Retention periods and the sub-processor list are available on request only, and security.txt returns 404" ], "agentNotes": [ "Use the host for the tenant's region (amer-1, emea-1 or apac-1). Tokens come from auth.\u003cregion\u003e.jumio.ai/oauth2/token with the client ID and secret as Basic credentials", "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", "Send a User-Agent header on every call. The Account API marks it required", "Don't blindly retry POST /api/v1/accounts. Each call creates an account and a transaction, and no idempotency key exists", "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" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 55 } ], "editorialScores": { "ergonomics": 45, "maintenance": 75, "payments": 0, "reliability": 65, "schema": 73, "security": 63, "transparency": 41 }, "provenanceScore": 78 }, "connect": { "http": "curl --location 'https://auth.amer-1.jumio.ai/oauth2/token' \\\n -u CLIENT_ID:CLIENT_SECRET \\\n --header 'Accept: application/json' \\\n --data-urlencode 'grant_type=client_credentials'" }, "letme": { "capability": "https://letme.dev/kyc.identity", "tool": "https://letme.dev/jumio" }, "area": "domain-data", "provenance": { "legalEntity": "Jumio Corporation", "domain": "jumio.com", "domainRegistered": "2004-03-30", "endpointOnVendorDomain": true, "terms": "", "privacy": "https://www.jumio.com/privacy-center/privacy-notices/online-services-notice/", "statusPage": "https://monitor.jumio.com", "changelog": "https://documentation.jumio.ai/docs/developer-resources/SDKs/mobile-sdk/mobile-sdk-android-master/docs/changelog", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The Online Services Privacy Notice (last updated 4 August 2026) names Jumio Corporation, 100 Mathilda Place, Suite 100, Sunnyvale, CA 94086, with Jumio Software Development GmbH in Linz as EU representative.", "No terms field. Jumio publishes no service agreement or API terms for customers. www.jumio.com/terms-of-use/ (last updated 18 June 2026) is addressed to end users in the United States, so it isn't recorded as the governing document.", "The APIs answer on jumio.ai hosts (auth, account, api, retrieval, kyx and status under amer-1, emea-1 and apac-1), a second domain used throughout Jumio's own documentation at documentation.jumio.ai.", "www.jumio.com/.well-known/security.txt and /security.txt return 404. Reports go to the vulnerability disclosure programme at https://vdp.jumio.com, which pays nothing.", "The changelog linked is the Android SDK's. No changelog for the REST APIs was found.", "RDAP for jumio.com gives a registration date of 2004-03-30." ], "score": 78 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/jumio.json", "live": { "slug": "jumio", "vendorStatus": { "page": "https://monitor.jumio.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-14T09:39:17.680456737Z" }, "versions": [ { "registry": "github", "name": "Jumio/mobile-sdk-android", "version": "v4.19.1", "released": "2026-09-28", "seenAt": "2026-10-13T23:03:31.8438655Z" }, { "registry": "npm", "name": "@jumio/websdk", "version": "0.6.2", "seenAt": "2026-10-13T23:03:29.658957915Z" }, { "registry": "npm", "name": "react-native-jumio-mobilesdk", "version": "4.11.0", "seenAt": "2026-10-13T23:03:30.077827417Z" } ], "githubStars": 72, "npmWeekly": 2384, "securityTxt": { "url": "https://jumio.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-13T15:45:23.408019204Z" }, "llmsTxt": { "url": "https://documentation.jumio.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-13T14:11:48.597122921Z" }, "domain": { "domain": "jumio.com", "registered": "2004-03-30", "source": "https://rdap.verisign.com/com/v1/domain/jumio.com", "checkedAt": "2026-10-11T13:20:49.723829226Z" }, "pages": [ { "url": "https://documentation.jumio.ai/docs/developer-resources/SDKs/mobile-sdk/mobile-sdk-android-master/docs/changelog", "kind": "changelog", "status": 304, "checkedAt": "2026-10-13T20:16:24.688432791Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "4e0b13492ecb" }, { "url": "https://www.jumio.com/privacy-center/privacy-notices/online-services-notice/", "kind": "privacy", "status": 304, "checkedAt": "2026-10-13T20:29:11.663584583Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "47ddc34e8761" } ], "updatedAt": "2026-10-14T09:39:17.680456737Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Onfido Ltd (Entrust)", "b": "Jumio Corporation", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth", "name": "Auth" }, { "a": "Paid", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "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", "b": "Proprietary service. No public service agreement was found. The @jumio/websdk npm package is marked UNLICENSED", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-08-31", "b": "2026-09-28", "name": "Last release" }, { "a": "couldn't be read", "b": "no document linked", "name": "Terms last updated" }, { "a": "", "b": "2026-08-04", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "yes", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "", "name": "Arbitration or class-action waiver" }, { "a": "59k npm/wk, 27k PyPI/wk", "b": "72 stars, 2.1k npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "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 \u0026 auth and maintenance \u0026 community.", "question": "Which is better for AI agents, Entrust Identity Verification (formerly Onfido) or Jumio?" }, { "answer": "Entrust Identity Verification (formerly Onfido) takes an API key or an OAuth sign-in. Jumio uses an OAuth sign-in.", "question": "Do Entrust Identity Verification (formerly Onfido) and Jumio need an API key?" }, { "answer": "No hosted endpoint is listed for Entrust Identity Verification (formerly Onfido). No hosted endpoint is listed for Jumio.", "question": "Can an agent call Entrust Identity Verification (formerly Onfido) and Jumio without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 70 against 65", "Schema \u0026 documentation, 84 against 73", "Agent ergonomics, 65 against 45", "Payments \u0026 pricing, 20 against 0", "Transparency \u0026 trust, 70 against 60" ], "also": null, "goodFor": "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.", "slug": "entrust-identity-verification", "watchFor": "entrust.com answered 403 to every request, so the terms, privacy notice, pricing page and security.txt weren't read" }, { "aheadOn": [ "Security \u0026 auth, 63 against 58", "Maintenance \u0026 community, 75 against 58" ], "also": null, "goodFor": "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.", "slug": "jumio", "watchFor": "No public price, free tier or trial. OAuth2 and workflow keys are activated by a Jumio account manager" } ], "job": { "capability": "kyc.identity", "name": "Identity verification" }, "others": [ { "json": "https://www.anchorterminal.com/compare/alloy-vs-entrust-identity-verification.json", "title": "Alloy vs Entrust Identity Verification (formerly Onfido)", "url": "https://www.anchorterminal.com/compare/alloy-vs-entrust-identity-verification" }, { "json": "https://www.anchorterminal.com/compare/alloy-vs-jumio.json", "title": "Alloy vs Jumio", "url": "https://www.anchorterminal.com/compare/alloy-vs-jumio" }, { "json": "https://www.anchorterminal.com/compare/complycube-vs-entrust-identity-verification.json", "title": "ComplyCube vs Entrust Identity Verification (formerly Onfido)", "url": "https://www.anchorterminal.com/compare/complycube-vs-entrust-identity-verification" }, { "json": "https://www.anchorterminal.com/compare/complycube-vs-jumio.json", "title": "ComplyCube vs Jumio", "url": "https://www.anchorterminal.com/compare/complycube-vs-jumio" }, { "json": "https://www.anchorterminal.com/compare/didit-vs-entrust-identity-verification.json", "title": "Didit vs Entrust Identity Verification (formerly Onfido)", "url": "https://www.anchorterminal.com/compare/didit-vs-entrust-identity-verification" }, { "json": "https://www.anchorterminal.com/compare/didit-vs-jumio.json", "title": "Didit vs Jumio", "url": "https://www.anchorterminal.com/compare/didit-vs-jumio" }, { "json": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-middesk.json", "title": "Entrust Identity Verification (formerly Onfido) vs Middesk", "url": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-middesk" }, { "json": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-persona.json", "title": "Entrust Identity Verification (formerly Onfido) vs Persona", "url": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-persona" }, { "json": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-plaid-identity-verification.json", "title": "Entrust Identity Verification (formerly Onfido) vs Plaid Identity Verification", "url": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-plaid-identity-verification" }, { "json": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-shufti.json", "title": "Entrust Identity Verification (formerly Onfido) vs Shufti", "url": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-shufti" }, { "json": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-socure-riskos.json", "title": "Entrust Identity Verification (formerly Onfido) vs Socure RiskOS", "url": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-socure-riskos" }, { "json": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-stripe-identity.json", "title": "Entrust Identity Verification (formerly Onfido) vs Stripe Identity", "url": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-stripe-identity" }, { "json": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-sumsub.json", "title": "Entrust Identity Verification (formerly Onfido) vs Sumsub", "url": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-sumsub" }, { "json": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-trulioo.json", "title": "Entrust Identity Verification (formerly Onfido) vs Trulioo", "url": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-trulioo" }, { "json": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-veriff.json", "title": "Entrust Identity Verification (formerly Onfido) vs Veriff", "url": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-veriff" }, { "json": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-vouched.json", "title": "Entrust Identity Verification (formerly Onfido) vs Vouched", "url": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-vouched" }, { "json": "https://www.anchorterminal.com/compare/jumio-vs-middesk.json", "title": "Jumio vs Middesk", "url": "https://www.anchorterminal.com/compare/jumio-vs-middesk" }, { "json": "https://www.anchorterminal.com/compare/jumio-vs-persona.json", "title": "Jumio vs Persona", "url": "https://www.anchorterminal.com/compare/jumio-vs-persona" }, { "json": "https://www.anchorterminal.com/compare/jumio-vs-plaid-identity-verification.json", "title": "Jumio vs Plaid Identity Verification", "url": "https://www.anchorterminal.com/compare/jumio-vs-plaid-identity-verification" }, { "json": "https://www.anchorterminal.com/compare/jumio-vs-shufti.json", "title": "Jumio vs Shufti", "url": "https://www.anchorterminal.com/compare/jumio-vs-shufti" }, { "json": "https://www.anchorterminal.com/compare/jumio-vs-socure-riskos.json", "title": "Jumio vs Socure RiskOS", "url": "https://www.anchorterminal.com/compare/jumio-vs-socure-riskos" }, { "json": "https://www.anchorterminal.com/compare/jumio-vs-stripe-identity.json", "title": "Jumio vs Stripe Identity", "url": "https://www.anchorterminal.com/compare/jumio-vs-stripe-identity" }, { "json": "https://www.anchorterminal.com/compare/jumio-vs-sumsub.json", "title": "Jumio vs Sumsub", "url": "https://www.anchorterminal.com/compare/jumio-vs-sumsub" }, { "json": "https://www.anchorterminal.com/compare/jumio-vs-trulioo.json", "title": "Jumio vs Trulioo", "url": "https://www.anchorterminal.com/compare/jumio-vs-trulioo" }, { "json": "https://www.anchorterminal.com/compare/jumio-vs-veriff.json", "title": "Jumio vs Veriff", "url": "https://www.anchorterminal.com/compare/jumio-vs-veriff" }, { "json": "https://www.anchorterminal.com/compare/jumio-vs-vouched.json", "title": "Jumio vs Vouched", "url": "https://www.anchorterminal.com/compare/jumio-vs-vouched" }, { "json": "https://www.anchorterminal.com/compare/complyadvantage-vs-entrust-identity-verification.json", "title": "ComplyAdvantage vs Entrust Identity Verification (formerly Onfido)", "url": "https://www.anchorterminal.com/compare/complyadvantage-vs-entrust-identity-verification" }, { "json": "https://www.anchorterminal.com/compare/complyadvantage-vs-jumio.json", "title": "ComplyAdvantage vs Jumio", "url": "https://www.anchorterminal.com/compare/complyadvantage-vs-jumio" } ], "scores": [ { "by": 5, "edge": "entrust-identity-verification", "entrust-identity-verification": 70, "jumio": 65, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 11, "edge": "entrust-identity-verification", "entrust-identity-verification": 84, "jumio": 73, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 20, "edge": "entrust-identity-verification", "entrust-identity-verification": 65, "jumio": 45, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 5, "edge": "jumio", "entrust-identity-verification": 58, "jumio": 63, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 20, "edge": "entrust-identity-verification", "entrust-identity-verification": 20, "jumio": 0, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 17, "edge": "jumio", "entrust-identity-verification": 58, "jumio": 75, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 10, "edge": "entrust-identity-verification", "entrust-identity-verification": 70, "jumio": 60, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "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 \u0026 auth and maintenance \u0026 community. Both do identity verification.", "verdicts": { "entrust-identity-verification": "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-jumio", "json": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-jumio.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-jumio.md", "slim": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-jumio.min.md" }, "markdown": "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 \u0026 auth and maintenance \u0026 community. Both do identity verification.\n\n- 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\n- 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\n- Best identity and business verification APIs for AI agents: https://www.anchorterminal.com/best/identity-verification/index.md\n- All 119 verification comparisons: https://www.anchorterminal.com/compare/identity-verification/index.md\n\n## Which one, for what\n\n### Entrust Identity Verification (formerly Onfido) (B)\n\nGood 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.\n\nAhead on:\n- Reliability, 70 against 65\n- Schema \u0026 documentation, 84 against 73\n- Agent ergonomics, 65 against 45\n- Payments \u0026 pricing, 20 against 0\n- Transparency \u0026 trust, 70 against 60\n\nWatch for: entrust.com answered 403 to every request, so the terms, privacy notice, pricing page and security.txt weren't read\n\n### Jumio (C)\n\nGood 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.\n\nAhead on:\n- Security \u0026 auth, 63 against 58\n- Maintenance \u0026 community, 75 against 58\n\nWatch for: No public price, free tier or trial. OAuth2 and workflow keys are activated by a Jumio account manager\n\n\n## Score by category\n\n| Category | Weight | Entrust Identity Verification (formerly Onfido) | Jumio | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 70 | 65 | Entrust Identity Verification (formerly Onfido) +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 84 | 73 | Entrust Identity Verification (formerly Onfido) +11 |\n| Agent ergonomics | 13% (16.2 this run) | 65 | 45 | Entrust Identity Verification (formerly Onfido) +20 |\n| Security \u0026 auth | 14% (17.5 this run) | 58 | 63 | Jumio +5 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 0 | Entrust Identity Verification (formerly Onfido) +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 58 | 75 | Jumio +17 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 70 | 60 | Entrust Identity Verification (formerly Onfido) +10 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **62.1 · B** | **55 · C** | |\n\n## Facts side by side\n\n| Fact | Entrust Identity Verification (formerly Onfido) | Jumio |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Onfido Ltd (Entrust) | Jumio Corporation |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | OAuth |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| 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 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-08-31 | 2026-09-28 |\n| Terms last updated | couldn't be read | no document linked |\n| Privacy policy last updated | | 2026-08-04 |\n| Customer content may train models | couldn't be read | yes |\n| Terms restrict automated access | couldn't be read | |\n| Terms restrict benchmarking | couldn't be read | |\n| Terms or service can change without notice | couldn't be read | |\n| Arbitration or class-action waiver | couldn't be read | |\n| Popularity | 59k npm/wk, 27k PyPI/wk | 72 stars, 2.1k npm/wk |\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### Entrust Identity Verification (formerly Onfido)\n\n1. Use the regional host for the account (api.eu, api.us or api.ca.onfido.com/v3.6). v3.6 has no default region\n2. Prefer an OAuth client with only the scopes the task needs over a live API token, and refresh the 60-minute access token\n3. Stay under 400 requests a minute live and 120 in sandbox, and back off on a 429 `rate_limit` error\n4. Check before retrying a POST. There is no idempotency key, so a retry can create a second applicant or check\n5. Treat webhook events as duplicates or out of order, and verify `X-SHA2-Signature` over the raw body\n\n### Jumio\n\n1. Use the host for the tenant's region (amer-1, emea-1 or apac-1). Tokens come from auth.\u003cregion\u003e.jumio.ai/oauth2/token with the client ID and secret as Basic credentials\n2. 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\n3. Send a User-Agent header on every call. The Account API marks it required\n4. Don't blindly retry POST /api/v1/accounts. Each call creates an account and a transaction, and no idempotency key exists\n5. 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\n\n## Questions\n\n### Which is better for AI agents, Entrust Identity Verification (formerly Onfido) or Jumio?\n\nEntrust 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 \u0026 auth and maintenance \u0026 community.\n\n### Do Entrust Identity Verification (formerly Onfido) and Jumio need an API key?\n\nEntrust Identity Verification (formerly Onfido) takes an API key or an OAuth sign-in. Jumio uses an OAuth sign-in.\n\n### Can an agent call Entrust Identity Verification (formerly Onfido) and Jumio without installing anything?\n\nNo hosted endpoint is listed for Entrust Identity Verification (formerly Onfido). No hosted endpoint is listed for Jumio.\n\n\n## For agents\n\n- 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\n- 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`\n- 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\n\n## Other comparisons with Entrust Identity Verification (formerly Onfido) or Jumio\n\n- [Alloy vs Entrust Identity Verification (formerly Onfido)](https://www.anchorterminal.com/compare/alloy-vs-entrust-identity-verification.md)\n- [Alloy vs Jumio](https://www.anchorterminal.com/compare/alloy-vs-jumio.md)\n- [ComplyCube vs Entrust Identity Verification (formerly Onfido)](https://www.anchorterminal.com/compare/complycube-vs-entrust-identity-verification.md)\n- [ComplyCube vs Jumio](https://www.anchorterminal.com/compare/complycube-vs-jumio.md)\n- [Didit vs Entrust Identity Verification (formerly Onfido)](https://www.anchorterminal.com/compare/didit-vs-entrust-identity-verification.md)\n- [Didit vs Jumio](https://www.anchorterminal.com/compare/didit-vs-jumio.md)\n- [Entrust Identity Verification (formerly Onfido) vs Middesk](https://www.anchorterminal.com/compare/entrust-identity-verification-vs-middesk.md)\n- [Entrust Identity Verification (formerly Onfido) vs Persona](https://www.anchorterminal.com/compare/entrust-identity-verification-vs-persona.md)\n- [Entrust Identity Verification (formerly Onfido) vs Plaid Identity Verification](https://www.anchorterminal.com/compare/entrust-identity-verification-vs-plaid-identity-verification.md)\n- [Entrust Identity Verification (formerly Onfido) vs Shufti](https://www.anchorterminal.com/compare/entrust-identity-verification-vs-shufti.md)\n- [Entrust Identity Verification (formerly Onfido) vs Socure RiskOS](https://www.anchorterminal.com/compare/entrust-identity-verification-vs-socure-riskos.md)\n- [Entrust Identity Verification (formerly Onfido) vs Stripe Identity](https://www.anchorterminal.com/compare/entrust-identity-verification-vs-stripe-identity.md)\n- [Entrust Identity Verification (formerly Onfido) vs Sumsub](https://www.anchorterminal.com/compare/entrust-identity-verification-vs-sumsub.md)\n- [Entrust Identity Verification (formerly Onfido) vs Trulioo](https://www.anchorterminal.com/compare/entrust-identity-verification-vs-trulioo.md)\n- [Entrust Identity Verification (formerly Onfido) vs Veriff](https://www.anchorterminal.com/compare/entrust-identity-verification-vs-veriff.md)\n- [Entrust Identity Verification (formerly Onfido) vs Vouched](https://www.anchorterminal.com/compare/entrust-identity-verification-vs-vouched.md)\n- [Jumio vs Middesk](https://www.anchorterminal.com/compare/jumio-vs-middesk.md)\n- [Jumio vs Persona](https://www.anchorterminal.com/compare/jumio-vs-persona.md)\n- [Jumio vs Plaid Identity Verification](https://www.anchorterminal.com/compare/jumio-vs-plaid-identity-verification.md)\n- [Jumio vs Shufti](https://www.anchorterminal.com/compare/jumio-vs-shufti.md)\n- [Jumio vs Socure RiskOS](https://www.anchorterminal.com/compare/jumio-vs-socure-riskos.md)\n- [Jumio vs Stripe Identity](https://www.anchorterminal.com/compare/jumio-vs-stripe-identity.md)\n- [Jumio vs Sumsub](https://www.anchorterminal.com/compare/jumio-vs-sumsub.md)\n- [Jumio vs Trulioo](https://www.anchorterminal.com/compare/jumio-vs-trulioo.md)\n- [Jumio vs Veriff](https://www.anchorterminal.com/compare/jumio-vs-veriff.md)\n- [Jumio vs Vouched](https://www.anchorterminal.com/compare/jumio-vs-vouched.md)\n- [ComplyAdvantage vs Entrust Identity Verification (formerly Onfido)](https://www.anchorterminal.com/compare/complyadvantage-vs-entrust-identity-verification.md)\n- [ComplyAdvantage vs Jumio](https://www.anchorterminal.com/compare/complyadvantage-vs-jumio.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-14", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Entrust Identity Verification (formerly Onfido) vs Jumio", "url": "" } ], "description": "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.", "facts": [ "Entrust Identity Verification (formerly Onfido) B 62.1", "Jumio C 55", "scores" ], "h1": "Entrust Identity Verification (formerly Onfido) vs Jumio", "image": "https://www.anchorterminal.com/assets/og/compare-entrust-identity-verification-vs-jumio.png", "path": "/compare/entrust-identity-verification-vs-jumio", "published": "2026-10-01", "section": "tools", "title": "Entrust Identity Verification vs Jumio for AI agents (2026)", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-jumio" }, "tokens": { "markdown": 2950, "slim": 780 }, "version": 1 }