{ "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 Veriff's 61.1 (C), and leads in 4 of 7 scored categories. Veriff leads on security \u0026 auth, payments \u0026 pricing and maintenance \u0026 community.", "b": { "slug": "veriff", "name": "Veriff", "vendor": "Veriff OÜ", "vendorUrl": "https://www.veriff.com", "kind": "http-api", "category": "identity-verification", "summary": "Identity verification service from Veriff in Tallinn. It checks an identity document and a selfie, with liveness, database checks and PEP and sanctions screening. Sessions are created and read through the Public API v1, with results sent by webhook.", "url": "https://www.anchorterminal.com/tools/veriff", "markdownUrl": "https://www.anchorterminal.com/tools/veriff.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/veriff.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/veriff.json", "repo": "https://github.com/Veriff/veriff-js-sdk", "license": "Proprietary service. The npm capture SDKs are ISC (@veriff/js-sdk, @veriff/incontext-sdk) and MIT (@veriff/react-native-sdk)", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "@veriff/incontext-sdk" }, { "registry": "npm", "name": "@veriff/js-sdk" }, { "registry": "npm", "name": "@veriff/react-native-sdk" } ], "auth": "api-key", "authNotes": "Self-serve. Signing up for a Self-Serve plan creates a Customer Portal account with a test integration, and Enterprise accounts start from a sales form. Each integration has an API key, sent as `X-AUTH-CLIENT`, and up to five shared secret keys used to compute an HMAC-SHA256 `X-HMAC-SIGNATURE` (over the body on POST and PATCH, over the session ID on GET and DELETE). POST /v1/sessions needs only the API key. Secrets are shown once and can be rotated or deleted by an admin. There are no scopes. A live integration unlocks once the account holder passes Veriff's own identity verification.", "pricing": "usage", "pricingNotes": "Self-Serve is priced per verification with a monthly minimum. Essential is $0.80 ($49 a month minimum), Plus $1.39 ($99) and Premium $1.89 ($209). PEP and sanctions screening adds $0.64, ongoing monitoring $0.09 and two-year retention $0.30. A 15-day trial covers up to 50 sessions with no card, after the account holder completes identity verification. Test integrations are free and unbilled. Enterprise, suggested for 5,000 or more verifications a month, is priced by sales (https://www.veriff.com/plans/self-serve, checked 2026-10-08).", "priceSummary": "$0.80 / tx", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs index, the API guides or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 32, "npmWeekly": 109625, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://devdocs.veriff.com", "llmsTxt": "https://devdocs.veriff.com/llms.txt", "openapi": "https://devdocs.veriff.com/apidocs/v1sessions.md", "capabilities": [ "kyc.identity", "kyc.documents", "kyc.screening" ], "tags": [ "hosted", "api-key", "hmac", "webhooks", "openapi", "llms-txt", "free-trial", "sandbox", "status-page", "bug-bounty", "soc2", "iso27001" ], "lastRelease": "2026-10-02", "graded": true, "anchor": { "graded": true, "score": 61.1, "grade": "C", "agentReady": false, "rank": 512, "ranked": true, "rankOf": 1076, "categoryRank": 9, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 43, "maintenance": 74, "payments": 40, "reliability": 62, "schema": 82, "security": 63, "transparency": 67 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "Public prices of $0.80, $1.39 and $1.89 a verification, with a 15-day trial of up to 50 sessions and no card", "llms.txt index and Markdown pages, each API endpoint with an OpenAPI 3.0.0 fragment, examples and error schemas", "Up to five shared secret keys per integration, shown once, with documented rotation and deletion", "Test integrations are created at signup, aren't billed, and let the developer force a decision", "ISO/IEC 27001:2022, SOC 2 Type II, Cyber Essentials and a bug bounty on Intigriti paying 50 to 6,000 euros" ], "weaknesses": [ "No server-side SDK and no MCP server. Official packages cover only browser and mobile capture", "No idempotency key on POST /v1/sessions, and no Retry-After or backoff guidance for the documented 429", "Nine status-page incidents between 20 July and 7 October 2026, mostly delayed decisions in the US region", "No endpoint lists sessions and no pagination was found. Every read needs a stored session ID", "Session deletion by API is off by default and capped at 10 sessions in 24 hours", "No security.txt, and the sub-processor list sits on a help centre page that needs JavaScript" ], "agentNotes": [ "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", "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", "Stay under 30 session creations a minute on Self-Serve, 600 on Enterprise. A 429 carries code 1004", "Don't blindly retry POST /v1/sessions. Each call makes a new session, which is billed on a live integration", "Poll GET /v1/sessions/{id}/decision until `verification` is not null, or accept webhooks within 5 seconds and treat duplicates as normal" ], "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": 61.1 } ], "editorialScores": { "ergonomics": 43, "maintenance": 74, "payments": 40, "reliability": 62, "schema": 82, "security": 63, "transparency": 48 }, "provenanceScore": 85 }, "connect": { "http": "curl -X POST \"https://\u003cBaseURL\u003e/v1/sessions\" \\\n -H 'Content-Type: application/json' \\\n -H 'X-AUTH-CLIENT: API-KEY' \\\n -d '{\"verification\": {}}'" }, "letme": { "capability": "https://letme.dev/kyc.identity", "tool": "https://letme.dev/veriff" }, "area": "domain-data", "unitPrices": [ { "item": "Verification, Essential plan (automated decision)", "unit": "tx", "usd": 0.8, "note": "$49 a month minimum" }, { "item": "Verification, Plus plan", "unit": "tx", "usd": 1.39, "note": "$99 a month minimum" }, { "item": "Verification, Premium plan", "unit": "tx", "usd": 1.89, "note": "$209 a month minimum" }, { "item": "PEP and sanctions screening add-on, per verification", "unit": "tx", "usd": 0.64, "note": "charged on top of the monthly minimum" }, { "item": "Ongoing monitoring add-on, per verification", "unit": "tx", "usd": 0.09, "note": "charged on top of the monthly minimum" } ], "provenance": { "legalEntity": "Veriff OÜ", "domain": "veriff.com", "domainRegistered": "2006-04-12", "endpointOnVendorDomain": true, "terms": "https://www.veriff.com/terms-of-service", "privacy": "https://www.veriff.com/privacy-notice", "statusPage": "https://status.veriff.com", "changelog": "https://devdocs.veriff.com/docs/release-notes", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The privacy notice (valid from 30 July 2020, last updated 16 April 2026) names Veriff OÜ and Veriff Brazil Ltda. and gives the Estonian Data Protection Inspectorate as lead supervisory authority.", "www.veriff.com/terms-of-service answers 200 with the title Terms of Service but no terms text in the HTML we fetched, so the terms themselves weren't read.", "www.veriff.com/.well-known/security.txt and /security.txt return 404. Reports go to a bug bounty programme on Intigriti (https://www.veriff.com/bug-bounty).", "The API base URL is per integration and shown in the Customer Portal. Code samples in the docs use https://stationapi.veriff.com.", "RDAP for veriff.com gives a registration date of 2006-04-12, which predates the company.", "The sub-processor list is linked from the privacy notice to help.veriff.com, which returned only a JavaScript shell to our fetch." ], "score": 85 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/veriff.json", "live": { "slug": "veriff", "vendorStatus": { "page": "https://status.veriff.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-14T09:39:46.209719689Z" }, "versions": [ { "registry": "github", "name": "Veriff/veriff-js-sdk", "version": "v2.0.0", "released": "2025-09-09", "seenAt": "2026-10-13T23:31:40.183610703Z" }, { "registry": "npm", "name": "@veriff/incontext-sdk", "version": "2.5.0", "seenAt": "2026-10-13T23:31:35.965000783Z" }, { "registry": "npm", "name": "@veriff/js-sdk", "version": "2.0.0", "seenAt": "2026-10-13T23:31:36.444840844Z" }, { "registry": "npm", "name": "@veriff/react-native-sdk", "version": "13.2.0", "seenAt": "2026-10-13T23:31:38.170298091Z" } ], "githubStars": 32, "npmWeekly": 86872, "securityTxt": { "url": "https://veriff.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-13T15:46:02.397688666Z" }, "llmsTxt": { "url": "https://devdocs.veriff.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-13T14:12:45.152591047Z" }, "domain": { "domain": "veriff.com", "registered": "2006-04-12", "source": "https://rdap.verisign.com/com/v1/domain/veriff.com", "checkedAt": "2026-10-11T13:13:15.609653227Z" }, "pages": [ { "url": "https://devdocs.veriff.com/docs/release-notes", "kind": "changelog", "status": 304, "checkedAt": "2026-10-13T20:12:26.964558523Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "26520a9df2cc" }, { "url": "https://www.veriff.com/privacy-notice", "kind": "privacy", "status": 200, "checkedAt": "2026-10-13T20:33:20.100316058Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "024c0d3f9713" }, { "url": "https://www.veriff.com/terms-of-service", "kind": "terms", "status": 200, "checkedAt": "2026-10-13T20:33:22.197443856Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "d9e650601ce7" } ], "updatedAt": "2026-10-14T09:39:46.209719689Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Onfido Ltd (Entrust)", "b": "Veriff OÜ", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Paid", "b": "Pay per use", "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. The npm capture SDKs are ISC (@veriff/js-sdk, @veriff/incontext-sdk) and MIT (@veriff/react-native-sdk)", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-08-31", "b": "2026-10-02", "name": "Last release" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "", "b": "2026-04-16", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "yes", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "59k npm/wk, 27k PyPI/wk", "b": "32 stars, 110k npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "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 \u0026 auth, payments \u0026 pricing and maintenance \u0026 community.", "question": "Which is better for AI agents, Entrust Identity Verification (formerly Onfido) or Veriff?" }, { "answer": "Entrust Identity Verification (formerly Onfido) takes an API key or an OAuth sign-in. Veriff needs an API key.", "question": "Do Entrust Identity Verification (formerly Onfido) and Veriff need an API key?" }, { "answer": "No hosted endpoint is listed for Entrust Identity Verification (formerly Onfido). No hosted endpoint is listed for Veriff.", "question": "Can an agent call Entrust Identity Verification (formerly Onfido) and Veriff without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 70 against 62", "Agent ergonomics, 65 against 43" ], "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", "Payments \u0026 pricing, 40 against 20", "Maintenance \u0026 community, 74 against 58" ], "also": null, "goodFor": "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.", "slug": "veriff", "watchFor": "No server-side SDK and no MCP server. Official packages cover only browser and mobile capture" } ], "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-veriff.json", "title": "Alloy vs Veriff", "url": "https://www.anchorterminal.com/compare/alloy-vs-veriff" }, { "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-veriff.json", "title": "ComplyCube vs Veriff", "url": "https://www.anchorterminal.com/compare/complycube-vs-veriff" }, { "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-veriff.json", "title": "Didit vs Veriff", "url": "https://www.anchorterminal.com/compare/didit-vs-veriff" }, { "json": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-jumio.json", "title": "Entrust Identity Verification (formerly Onfido) vs Jumio", "url": "https://www.anchorterminal.com/compare/entrust-identity-verification-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-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-veriff.json", "title": "Jumio vs Veriff", "url": "https://www.anchorterminal.com/compare/jumio-vs-veriff" }, { "json": "https://www.anchorterminal.com/compare/middesk-vs-veriff.json", "title": "Middesk vs Veriff", "url": "https://www.anchorterminal.com/compare/middesk-vs-veriff" }, { "json": "https://www.anchorterminal.com/compare/persona-vs-veriff.json", "title": "Persona vs Veriff", "url": "https://www.anchorterminal.com/compare/persona-vs-veriff" }, { "json": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-veriff.json", "title": "Plaid Identity Verification vs Veriff", "url": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-veriff" }, { "json": "https://www.anchorterminal.com/compare/shufti-vs-veriff.json", "title": "Shufti vs Veriff", "url": "https://www.anchorterminal.com/compare/shufti-vs-veriff" }, { "json": "https://www.anchorterminal.com/compare/socure-riskos-vs-veriff.json", "title": "Socure RiskOS vs Veriff", "url": "https://www.anchorterminal.com/compare/socure-riskos-vs-veriff" }, { "json": "https://www.anchorterminal.com/compare/stripe-identity-vs-veriff.json", "title": "Stripe Identity vs Veriff", "url": "https://www.anchorterminal.com/compare/stripe-identity-vs-veriff" }, { "json": "https://www.anchorterminal.com/compare/sumsub-vs-veriff.json", "title": "Sumsub vs Veriff", "url": "https://www.anchorterminal.com/compare/sumsub-vs-veriff" }, { "json": "https://www.anchorterminal.com/compare/trulioo-vs-veriff.json", "title": "Trulioo vs Veriff", "url": "https://www.anchorterminal.com/compare/trulioo-vs-veriff" }, { "json": "https://www.anchorterminal.com/compare/veriff-vs-vouched.json", "title": "Veriff vs Vouched", "url": "https://www.anchorterminal.com/compare/veriff-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-veriff.json", "title": "ComplyAdvantage vs Veriff", "url": "https://www.anchorterminal.com/compare/complyadvantage-vs-veriff" } ], "scores": [ { "by": 8, "edge": "entrust-identity-verification", "entrust-identity-verification": 70, "key": "reliability", "name": "Reliability", "veriff": 62, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 2, "edge": "entrust-identity-verification", "entrust-identity-verification": 84, "key": "schema", "name": "Schema \u0026 documentation", "veriff": 82, "weight": 13 }, { "by": 22, "edge": "entrust-identity-verification", "entrust-identity-verification": 65, "key": "ergonomics", "name": "Agent ergonomics", "veriff": 43, "weight": 13 }, { "by": 5, "edge": "veriff", "entrust-identity-verification": 58, "key": "security", "name": "Security \u0026 auth", "veriff": 63, "weight": 14 }, { "by": 20, "edge": "veriff", "entrust-identity-verification": 20, "key": "payments", "name": "Payments \u0026 pricing", "veriff": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 16, "edge": "veriff", "entrust-identity-verification": 58, "key": "maintenance", "name": "Maintenance \u0026 community", "veriff": 74, "weight": 7 }, { "by": 3, "edge": "entrust-identity-verification", "entrust-identity-verification": 70, "key": "transparency", "name": "Transparency \u0026 trust", "veriff": 67, "weight": 7 } ], "summary": "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 \u0026 auth, payments \u0026 pricing 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.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-veriff", "json": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-veriff.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-veriff.md", "slim": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-veriff.min.md" }, "markdown": "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 \u0026 auth, payments \u0026 pricing 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- 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\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 62\n- Agent ergonomics, 65 against 43\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### Veriff (C)\n\nGood 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.\n\nAhead on:\n- Security \u0026 auth, 63 against 58\n- Payments \u0026 pricing, 40 against 20\n- Maintenance \u0026 community, 74 against 58\n\nWatch for: No server-side SDK and no MCP server. Official packages cover only browser and mobile capture\n\n\n## Score by category\n\n| Category | Weight | Entrust Identity Verification (formerly Onfido) | Veriff | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 70 | 62 | Entrust Identity Verification (formerly Onfido) +8 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 84 | 82 | Entrust Identity Verification (formerly Onfido) +2 |\n| Agent ergonomics | 13% (16.2 this run) | 65 | 43 | Entrust Identity Verification (formerly Onfido) +22 |\n| Security \u0026 auth | 14% (17.5 this run) | 58 | 63 | Veriff +5 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 40 | Veriff +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 58 | 74 | Veriff +16 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 70 | 67 | Entrust Identity Verification (formerly Onfido) +3 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **62.1 · B** | **61.1 · C** | |\n\n## Facts side by side\n\n| Fact | Entrust Identity Verification (formerly Onfido) | Veriff |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Onfido Ltd (Entrust) | Veriff OÜ |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Paid | Pay per use |\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. The npm capture SDKs are ISC (@veriff/js-sdk, @veriff/incontext-sdk) and MIT (@veriff/react-native-sdk) |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-08-31 | 2026-10-02 |\n| Terms last updated | couldn't be read | couldn't be read |\n| Privacy policy last updated | | 2026-04-16 |\n| Customer content may train models | couldn't be read | yes |\n| Terms restrict automated access | couldn't be read | couldn't be read |\n| Terms restrict benchmarking | couldn't be read | couldn't be read |\n| Terms or service can change without notice | couldn't be read | couldn't be read |\n| Arbitration or class-action waiver | couldn't be read | couldn't be read |\n| Popularity | 59k npm/wk, 27k PyPI/wk | 32 stars, 110k 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**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.\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### Veriff\n\n1. 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\n2. 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\n3. Stay under 30 session creations a minute on Self-Serve, 600 on Enterprise. A 429 carries code 1004\n4. Don't blindly retry POST /v1/sessions. Each call makes a new session, which is billed on a live integration\n5. Poll GET /v1/sessions/{id}/decision until `verification` is not null, or accept webhooks within 5 seconds and treat duplicates as normal\n\n## Questions\n\n### Which is better for AI agents, Entrust Identity Verification (formerly Onfido) or Veriff?\n\nEntrust 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 \u0026 auth, payments \u0026 pricing and maintenance \u0026 community.\n\n### Do Entrust Identity Verification (formerly Onfido) and Veriff need an API key?\n\nEntrust Identity Verification (formerly Onfido) takes an API key or an OAuth sign-in. Veriff needs an API key.\n\n### Can an agent call Entrust Identity Verification (formerly Onfido) and Veriff without installing anything?\n\nNo hosted endpoint is listed for Entrust Identity Verification (formerly Onfido). No hosted endpoint is listed for Veriff.\n\n\n## For agents\n\n- 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\n- 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`\n- 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\n\n## Other comparisons with Entrust Identity Verification (formerly Onfido) or Veriff\n\n- [Alloy vs Entrust Identity Verification (formerly Onfido)](https://www.anchorterminal.com/compare/alloy-vs-entrust-identity-verification.md)\n- [Alloy vs Veriff](https://www.anchorterminal.com/compare/alloy-vs-veriff.md)\n- [ComplyCube vs Entrust Identity Verification (formerly Onfido)](https://www.anchorterminal.com/compare/complycube-vs-entrust-identity-verification.md)\n- [ComplyCube vs Veriff](https://www.anchorterminal.com/compare/complycube-vs-veriff.md)\n- [Didit vs Entrust Identity Verification (formerly Onfido)](https://www.anchorterminal.com/compare/didit-vs-entrust-identity-verification.md)\n- [Didit vs Veriff](https://www.anchorterminal.com/compare/didit-vs-veriff.md)\n- [Entrust Identity Verification (formerly Onfido) vs Jumio](https://www.anchorterminal.com/compare/entrust-identity-verification-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 Vouched](https://www.anchorterminal.com/compare/entrust-identity-verification-vs-vouched.md)\n- [Jumio vs Veriff](https://www.anchorterminal.com/compare/jumio-vs-veriff.md)\n- [Middesk vs Veriff](https://www.anchorterminal.com/compare/middesk-vs-veriff.md)\n- [Persona vs Veriff](https://www.anchorterminal.com/compare/persona-vs-veriff.md)\n- [Plaid Identity Verification vs Veriff](https://www.anchorterminal.com/compare/plaid-identity-verification-vs-veriff.md)\n- [Shufti vs Veriff](https://www.anchorterminal.com/compare/shufti-vs-veriff.md)\n- [Socure RiskOS vs Veriff](https://www.anchorterminal.com/compare/socure-riskos-vs-veriff.md)\n- [Stripe Identity vs Veriff](https://www.anchorterminal.com/compare/stripe-identity-vs-veriff.md)\n- [Sumsub vs Veriff](https://www.anchorterminal.com/compare/sumsub-vs-veriff.md)\n- [Trulioo vs Veriff](https://www.anchorterminal.com/compare/trulioo-vs-veriff.md)\n- [Veriff vs Vouched](https://www.anchorterminal.com/compare/veriff-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 Veriff](https://www.anchorterminal.com/compare/complyadvantage-vs-veriff.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 Veriff", "url": "" } ], "description": "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.", "facts": [ "Entrust Identity Verification (formerly Onfido) B 62.1", "Veriff C 61.1", "scores" ], "h1": "Entrust Identity Verification (formerly Onfido) vs Veriff", "image": "https://www.anchorterminal.com/assets/og/compare-entrust-identity-verification-vs-veriff.png", "path": "/compare/entrust-identity-verification-vs-veriff", "published": "2026-10-01", "section": "tools", "title": "Entrust Identity Verification vs Veriff for AI agents (2026)", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-veriff" }, "tokens": { "markdown": 2900, "slim": 680 }, "version": 1 }