{ "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:52:25.788754617Z" }, "updatedAt": "2026-10-14T09:52:25.788754617Z" } }, "answer": "Plaid Identity Verification scores 67.1 (B) on agent readiness against Entrust Identity Verification (formerly Onfido)'s 62.1 (B), and leads in 5 of 7 scored categories. Entrust Identity Verification (formerly Onfido) leads on payments \u0026 pricing.", "b": { "slug": "plaid-identity-verification", "name": "Plaid Identity Verification", "vendor": "Plaid Inc.", "vendorUrl": "https://plaid.com/products/identity-verification/", "kind": "http-api", "category": "identity-verification", "summary": "Plaid Identity Verification checks a person against data sources, identity documents, selfies with liveness and SMS, with risk scoring and optional Monitor watchlist screening. Sessions run in Plaid Link or through a backend-only API flow.", "url": "https://www.anchorterminal.com/tools/plaid-identity-verification", "markdownUrl": "https://www.anchorterminal.com/tools/plaid-identity-verification.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/plaid-identity-verification.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/plaid-identity-verification.json", "repo": "https://github.com/plaid/plaid-openapi", "license": "Proprietary service under Plaid's developer policy and end-user terms. The OpenAPI file and client libraries are MIT", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "plaid" }, { "registry": "pypi", "name": "plaid-python" } ], "auth": "api-key", "authNotes": "`client_id` and `secret` in the JSON body of each POST to https://sandbox.plaid.com or https://production.plaid.com, with a separate secret per environment. No scopes. Sandbox for Identity Verification is enabled self-serve from the Dashboard Products page (since 12 August 2026). Production needs a product access request, and the integrating company must be based in the US, Canada or the UK (checked 2026-10-14).", "pricing": "paid", "pricingNotes": "No public prices. Each session is billed an Anti-Fraud Engine fee plus fees for data source verification (by country), document checks and selfie checks, and retries are billed as new sessions. Exact rates appear after applying for Production. Sandbox is free (https://plaid.com/docs/account/billing/, checked 2026-10-14).", "priceSummary": "Paid", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Identity Verification docs, the API reference or the pricing page (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 1238045, "pypiWeekly": 656200, "asOf": "2026-10-14" }, "docsUrl": "https://plaid.com/docs/identity-verification/", "llmsTxt": "https://plaid.com/llms.txt", "openapi": "https://raw.githubusercontent.com/plaid/plaid-openapi/master/2020-09-14.yml", "capabilities": [ "kyc.identity", "kyc.documents", "kyc.screening" ], "tags": [ "hosted", "api-key", "openapi", "llms-txt", "webhooks", "sandbox", "status-page", "python", "typescript", "go", "java", "ruby", "bug-bounty" ], "lastRelease": "2026-10-13", "graded": true, "anchor": { "graded": true, "score": 67.1, "grade": "B", "agentReady": false, "rank": 278, "ranked": true, "rankOf": 1076, "categoryRank": 5, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 75, "maintenance": 83, "payments": 15, "reliability": 68, "schema": 91, "security": 61, "transparency": 77 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "Plaid Identity Verification has four typed endpoints in Plaid's public OpenAPI file, an idempotent create, a backend-only flow for data source checks and frequent changelog entries. Prices appear only after applying for Production, the secret has no scopes, and the rate-limit and error pages are disallowed to crawlers.", "bestFor": "US, Canadian and UK companies that want KYC with data source checks, documents and selfies, especially those already on Plaid or wanting Monitor screening in the same flow.", "strengths": [ "Four typed endpoints in the public OpenAPI file, with llms.txt and Markdown docs", "Backend-only flow runs data source checks from user data with no Link session", "`is_idempotent` on create returns the existing session instead of making a second", "Six dated Identity Verification changelog entries between 9 July and 13 October 2026", "Self-serve Sandbox since 12 August 2026, with sample identities for test outcomes" ], "weaknesses": [ "No public prices. Rates appear only after a Production application", "One team secret reaches every Plaid product, with no scopes or read-only key", "Integrating companies must be based in the US, Canada or the UK", "Data stays only while the contract is active, and access to past sessions ends with it", "Rate-limit and error pages sit under a path robots.txt disallows, so we didn't read them" ], "agentNotes": [ "Pass `is_idempotent: true` to /identity_verification/create so a retry returns the existing session", "Use the backend-only flow (data source template, `gave_consent: true`) when you already hold the user's details. Documents and selfies need the person in Link", "Wait for the STATUS_UPDATED webhook or poll /identity_verification/get. Link's onSuccess doesn't mean the user passed", "Don't issue retries casually. Each retry is a new session billed again", "Enable Sandbox for Identity Verification on the Dashboard Products page before the first call" ], "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": 67.1 } ], "editorialScores": { "ergonomics": 75, "maintenance": 83, "payments": 15, "reliability": 68, "schema": 91, "security": 61, "transparency": 57 }, "provenanceScore": 97 }, "connect": { "http": "curl -X POST https://sandbox.plaid.com/identity_verification/create \\\n-H 'Content-Type: application/json' \\\n-d '{\n \"client_user_id\": \"user-sandbox-b0e2c4ee-a763-4df5-bfe9-46a46bce993d\",\n \"client_id\": \"${PLAID_CLIENT_ID}\",\n \"secret\": \"${PLAID_SECRET}\",\n \"is_shareable\": true,\n \"template_id\": \"idvtmp_52xR9LKo77r1Np\",\n \"gave_consent\": true\n}'" }, "letme": { "capability": "https://letme.dev/kyc.identity", "tool": "https://letme.dev/plaid-identity-verification" }, "sameCompany": [ "plaid" ], "area": "domain-data", "provenance": { "legalEntity": "Plaid Inc.", "domain": "plaid.com", "domainRegistered": "1995-08-16", "endpointOnVendorDomain": true, "terms": "https://plaid.com/legal/#developer-policy", "privacy": "https://plaid.com/legal/#privacy-statement", "statusPage": "https://status.plaid.com", "changelog": "https://plaid.com/docs/changelog/", "securityTxt": "valid", "checked": "2026-10-14", "notes": [ "Same entity, legal pages and status page as the plaid listing. Plaid Financial Ltd and Plaid, B.V. cover the UK and the EEA.", "plaid.com/.well-known/security.txt lists HackerOne and security@plaid.com and expires 2026-12-31.", "plaid.com was registered in 1995, before Plaid was founded." ], "score": 97 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/plaid-identity-verification.json", "live": { "slug": "plaid-identity-verification", "vendorStatus": { "page": "https://status.plaid.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-14T09:53:20.159743826Z" }, "updatedAt": "2026-10-14T09:53:20.159743826Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Onfido Ltd (Entrust)", "b": "Plaid Inc.", "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": "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 under Plaid's developer policy and end-user terms. The OpenAPI file and client libraries are MIT", "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-13", "name": "Last release" }, { "a": "couldn't be read", "b": "2025-12-01", "name": "Terms last updated" }, { "a": "", "b": "2025-12-01", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "59k npm/wk, 27k PyPI/wk", "b": "1.2M npm/wk, 656k PyPI/wk", "name": "Popularity" } ], "faq": [ { "answer": "Plaid Identity Verification scores 67.1 (B) on agent readiness against Entrust Identity Verification (formerly Onfido)'s 62.1 (B), and leads in 5 of 7 scored categories. Entrust Identity Verification (formerly Onfido) leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Entrust Identity Verification (formerly Onfido) or Plaid Identity Verification?" }, { "answer": "Entrust Identity Verification (formerly Onfido) takes an API key or an OAuth sign-in. Plaid Identity Verification needs an API key.", "question": "Do Entrust Identity Verification (formerly Onfido) and Plaid Identity Verification need an API key?" }, { "answer": "No hosted endpoint is listed for Entrust Identity Verification (formerly Onfido). No hosted endpoint is listed for Plaid Identity Verification.", "question": "Can an agent call Entrust Identity Verification (formerly Onfido) and Plaid Identity Verification without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 20 against 15" ], "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": [ "Schema \u0026 documentation, 91 against 84", "Agent ergonomics, 75 against 65", "Maintenance \u0026 community, 83 against 58", "Transparency \u0026 trust, 77 against 70" ], "also": null, "goodFor": "US, Canadian and UK companies that want KYC with data source checks, documents and selfies, especially those already on Plaid or wanting Monitor screening in the same flow.", "slug": "plaid-identity-verification", "watchFor": "No public prices. Rates appear only after a Production application" } ], "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-plaid-identity-verification.json", "title": "Alloy vs Plaid Identity Verification", "url": "https://www.anchorterminal.com/compare/alloy-vs-plaid-identity-verification" }, { "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-plaid-identity-verification.json", "title": "ComplyCube vs Plaid Identity Verification", "url": "https://www.anchorterminal.com/compare/complycube-vs-plaid-identity-verification" }, { "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-plaid-identity-verification.json", "title": "Didit vs Plaid Identity Verification", "url": "https://www.anchorterminal.com/compare/didit-vs-plaid-identity-verification" }, { "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-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-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/middesk-vs-plaid-identity-verification.json", "title": "Middesk vs Plaid Identity Verification", "url": "https://www.anchorterminal.com/compare/middesk-vs-plaid-identity-verification" }, { "json": "https://www.anchorterminal.com/compare/persona-vs-plaid-identity-verification.json", "title": "Persona vs Plaid Identity Verification", "url": "https://www.anchorterminal.com/compare/persona-vs-plaid-identity-verification" }, { "json": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-shufti.json", "title": "Plaid Identity Verification vs Shufti", "url": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-shufti" }, { "json": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-socure-riskos.json", "title": "Plaid Identity Verification vs Socure RiskOS", "url": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-socure-riskos" }, { "json": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-stripe-identity.json", "title": "Plaid Identity Verification vs Stripe Identity", "url": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-stripe-identity" }, { "json": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-sumsub.json", "title": "Plaid Identity Verification vs Sumsub", "url": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-sumsub" }, { "json": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-trulioo.json", "title": "Plaid Identity Verification vs Trulioo", "url": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-trulioo" }, { "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/plaid-identity-verification-vs-vouched.json", "title": "Plaid Identity Verification vs Vouched", "url": "https://www.anchorterminal.com/compare/plaid-identity-verification-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-plaid-identity-verification.json", "title": "ComplyAdvantage vs Plaid Identity Verification", "url": "https://www.anchorterminal.com/compare/complyadvantage-vs-plaid-identity-verification" } ], "scores": [ { "by": 2, "edge": "entrust-identity-verification", "entrust-identity-verification": 70, "key": "reliability", "name": "Reliability", "plaid-identity-verification": 68, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 7, "edge": "plaid-identity-verification", "entrust-identity-verification": 84, "key": "schema", "name": "Schema \u0026 documentation", "plaid-identity-verification": 91, "weight": 13 }, { "by": 10, "edge": "plaid-identity-verification", "entrust-identity-verification": 65, "key": "ergonomics", "name": "Agent ergonomics", "plaid-identity-verification": 75, "weight": 13 }, { "by": 3, "edge": "plaid-identity-verification", "entrust-identity-verification": 58, "key": "security", "name": "Security \u0026 auth", "plaid-identity-verification": 61, "weight": 14 }, { "by": 5, "edge": "entrust-identity-verification", "entrust-identity-verification": 20, "key": "payments", "name": "Payments \u0026 pricing", "plaid-identity-verification": 15, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 25, "edge": "plaid-identity-verification", "entrust-identity-verification": 58, "key": "maintenance", "name": "Maintenance \u0026 community", "plaid-identity-verification": 83, "weight": 7 }, { "by": 7, "edge": "plaid-identity-verification", "entrust-identity-verification": 70, "key": "transparency", "name": "Transparency \u0026 trust", "plaid-identity-verification": 77, "weight": 7 } ], "summary": "Plaid Identity Verification scores 67.1 (B) on agent readiness against Entrust Identity Verification (formerly Onfido)'s 62.1 (B), and leads in 5 of 7 scored categories. Entrust Identity Verification (formerly Onfido) leads on payments \u0026 pricing. 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.", "plaid-identity-verification": "Plaid Identity Verification has four typed endpoints in Plaid's public OpenAPI file, an idempotent create, a backend-only flow for data source checks and frequent changelog entries. Prices appear only after applying for Production, the secret has no scopes, and the rate-limit and error pages are disallowed to crawlers." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-plaid-identity-verification", "json": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-plaid-identity-verification.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-plaid-identity-verification.md", "slim": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-plaid-identity-verification.min.md" }, "markdown": "Plaid Identity Verification scores 67.1 (B) on agent readiness against Entrust Identity Verification (formerly Onfido)'s 62.1 (B), and leads in 5 of 7 scored categories. Entrust Identity Verification (formerly Onfido) leads on payments \u0026 pricing. 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- Plaid Identity Verification: grade B, 67.1/100, rank #278 of 1076. Markdown https://www.anchorterminal.com/tools/plaid-identity-verification.md · JSON https://www.anchorterminal.com/api/v1/tools/plaid-identity-verification.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- Payments \u0026 pricing, 20 against 15\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### Plaid Identity Verification (B)\n\nGood for: US, Canadian and UK companies that want KYC with data source checks, documents and selfies, especially those already on Plaid or wanting Monitor screening in the same flow.\n\nAhead on:\n- Schema \u0026 documentation, 91 against 84\n- Agent ergonomics, 75 against 65\n- Maintenance \u0026 community, 83 against 58\n- Transparency \u0026 trust, 77 against 70\n\nWatch for: No public prices. Rates appear only after a Production application\n\n\n## Score by category\n\n| Category | Weight | Entrust Identity Verification (formerly Onfido) | Plaid Identity Verification | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 70 | 68 | Entrust Identity Verification (formerly Onfido) +2 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 84 | 91 | Plaid Identity Verification +7 |\n| Agent ergonomics | 13% (16.2 this run) | 65 | 75 | Plaid Identity Verification +10 |\n| Security \u0026 auth | 14% (17.5 this run) | 58 | 61 | Plaid Identity Verification +3 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 15 | Entrust Identity Verification (formerly Onfido) +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 58 | 83 | Plaid Identity Verification +25 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 70 | 77 | Plaid Identity Verification +7 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **62.1 · B** | **67.1 · B** | |\n\n## Facts side by side\n\n| Fact | Entrust Identity Verification (formerly Onfido) | Plaid Identity Verification |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Onfido Ltd (Entrust) | Plaid Inc. |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | API key |\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 under Plaid's developer policy and end-user terms. The OpenAPI file and client libraries are MIT |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-08-31 | 2026-10-13 |\n| Terms last updated | couldn't be read | 2025-12-01 |\n| Privacy policy last updated | | 2025-12-01 |\n| Customer content may train models | couldn't be read | not found in the text |\n| Terms restrict automated access | couldn't be read | not found in the text |\n| Terms restrict benchmarking | couldn't be read | yes |\n| Terms or service can change without notice | couldn't be read | not found in the text |\n| Arbitration or class-action waiver | couldn't be read | not found in the text |\n| Popularity | 59k npm/wk, 27k PyPI/wk | 1.2M npm/wk, 656k PyPI/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**Plaid Identity Verification.** Plaid Identity Verification has four typed endpoints in Plaid's public OpenAPI file, an idempotent create, a backend-only flow for data source checks and frequent changelog entries. Prices appear only after applying for Production, the secret has no scopes, and the rate-limit and error pages are disallowed to crawlers.\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### Plaid Identity Verification\n\n1. Pass `is_idempotent: true` to /identity_verification/create so a retry returns the existing session\n2. Use the backend-only flow (data source template, `gave_consent: true`) when you already hold the user's details. Documents and selfies need the person in Link\n3. Wait for the STATUS_UPDATED webhook or poll /identity_verification/get. Link's onSuccess doesn't mean the user passed\n4. Don't issue retries casually. Each retry is a new session billed again\n5. Enable Sandbox for Identity Verification on the Dashboard Products page before the first call\n\n## Questions\n\n### Which is better for AI agents, Entrust Identity Verification (formerly Onfido) or Plaid Identity Verification?\n\nPlaid Identity Verification scores 67.1 (B) on agent readiness against Entrust Identity Verification (formerly Onfido)'s 62.1 (B), and leads in 5 of 7 scored categories. Entrust Identity Verification (formerly Onfido) leads on payments \u0026 pricing.\n\n### Do Entrust Identity Verification (formerly Onfido) and Plaid Identity Verification need an API key?\n\nEntrust Identity Verification (formerly Onfido) takes an API key or an OAuth sign-in. Plaid Identity Verification needs an API key.\n\n### Can an agent call Entrust Identity Verification (formerly Onfido) and Plaid Identity Verification without installing anything?\n\nNo hosted endpoint is listed for Entrust Identity Verification (formerly Onfido). No hosted endpoint is listed for Plaid Identity Verification.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/entrust-identity-verification-vs-plaid-identity-verification.json, and with the fewest tokens: https://www.anchorterminal.com/compare/entrust-identity-verification-vs-plaid-identity-verification.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"entrust-identity-verification\", \"b\": \"plaid-identity-verification\"}`. From a terminal: `anchor compare entrust-identity-verification plaid-identity-verification`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/entrust-identity-verification.json and https://www.anchorterminal.com/api/v1/tools/plaid-identity-verification.json\n\n## Other comparisons with Entrust Identity Verification (formerly Onfido) or Plaid Identity Verification\n\n- [Alloy vs Entrust Identity Verification (formerly Onfido)](https://www.anchorterminal.com/compare/alloy-vs-entrust-identity-verification.md)\n- [Alloy vs Plaid Identity Verification](https://www.anchorterminal.com/compare/alloy-vs-plaid-identity-verification.md)\n- [ComplyCube vs Entrust Identity Verification (formerly Onfido)](https://www.anchorterminal.com/compare/complycube-vs-entrust-identity-verification.md)\n- [ComplyCube vs Plaid Identity Verification](https://www.anchorterminal.com/compare/complycube-vs-plaid-identity-verification.md)\n- [Didit vs Entrust Identity Verification (formerly Onfido)](https://www.anchorterminal.com/compare/didit-vs-entrust-identity-verification.md)\n- [Didit vs Plaid Identity Verification](https://www.anchorterminal.com/compare/didit-vs-plaid-identity-verification.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 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 Plaid Identity Verification](https://www.anchorterminal.com/compare/jumio-vs-plaid-identity-verification.md)\n- [Middesk vs Plaid Identity Verification](https://www.anchorterminal.com/compare/middesk-vs-plaid-identity-verification.md)\n- [Persona vs Plaid Identity Verification](https://www.anchorterminal.com/compare/persona-vs-plaid-identity-verification.md)\n- [Plaid Identity Verification vs Shufti](https://www.anchorterminal.com/compare/plaid-identity-verification-vs-shufti.md)\n- [Plaid Identity Verification vs Socure RiskOS](https://www.anchorterminal.com/compare/plaid-identity-verification-vs-socure-riskos.md)\n- [Plaid Identity Verification vs Stripe Identity](https://www.anchorterminal.com/compare/plaid-identity-verification-vs-stripe-identity.md)\n- [Plaid Identity Verification vs Sumsub](https://www.anchorterminal.com/compare/plaid-identity-verification-vs-sumsub.md)\n- [Plaid Identity Verification vs Trulioo](https://www.anchorterminal.com/compare/plaid-identity-verification-vs-trulioo.md)\n- [Plaid Identity Verification vs Veriff](https://www.anchorterminal.com/compare/plaid-identity-verification-vs-veriff.md)\n- [Plaid Identity Verification vs Vouched](https://www.anchorterminal.com/compare/plaid-identity-verification-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 Plaid Identity Verification](https://www.anchorterminal.com/compare/complyadvantage-vs-plaid-identity-verification.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 Plaid Identity Verification", "url": "" } ], "description": "Plaid Identity Verification scores 67.1 (B) to Entrust Identity Verification's 62.1 (B) for identity verification. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Entrust Identity Verification (formerly Onfido) B 62.1", "Plaid Identity Verification B 67.1", "scores" ], "h1": "Entrust Identity Verification (formerly Onfido) vs Plaid Identity Verification", "image": "https://www.anchorterminal.com/assets/og/compare-entrust-identity-verification-vs-plaid-identity-verification.png", "path": "/compare/entrust-identity-verification-vs-plaid-identity-verification", "published": "2026-10-01", "section": "tools", "title": "Entrust Identity Verification vs Plaid Identity Verification (2026)", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-plaid-identity-verification" }, "tokens": { "markdown": 3150, "slim": 780 }, "version": 1 }