{ "data": { "a": { "slug": "didit", "name": "Didit", "vendor": "Didit Identity Spain, S.L.", "vendorUrl": "https://didit.me", "kind": "http-api", "category": "identity-verification", "summary": "Didit is a hosted identity verification service for document, liveness, face match, sanctions screening and business registry checks. Developers reach it through a REST API with an OpenAPI spec, a hosted MCP server and client SDKs.", "url": "https://www.anchorterminal.com/tools/didit", "markdownUrl": "https://www.anchorterminal.com/tools/didit.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/didit.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/didit.json", "repo": "https://github.com/didit-protocol/mcp", "license": "Proprietary service under Didit's Business Terms and Conditions. The MCP server in didit-protocol/mcp is MIT", "transports": [ "http", "streamable-http", "stdio" ], "remoteUrl": "https://verification.didit.me", "packages": [ { "registry": "npm", "name": "@didit-protocol/mcp-server" }, { "registry": "npm", "name": "@didit-protocol/sdk-web" }, { "registry": "npm", "name": "@didit-protocol/sdk-react-native" } ], "auth": "mixed", "authNotes": "Self-serve. The REST API takes an application API key in the `x-api-key` header. A key comes from the Business Console or from the registration API on `apx.didit.me`, which emails a 6-character code and returns the key with no browser step. Each application has a primary key with full access and any number of named keys with read or write access per resource, workflow and status limits, an IP allowlist and an expiry date. Named keys are created, rotated and revoked only in the console. The hosted MCP server uses OAuth 2.1 with PKCE and dynamic client registration, with the scopes `didit:management` and `didit:verification`, and accepts no API key.", "pricing": "usage", "pricingNotes": "Pay per completed check from prepaid USD credits, with no contract or minimum and no card needed to sign up. In a workflow, ID verification is $0.15, passive liveness $0.10, face match $0.05, device and IP analysis $0.03 and AML screening $0.20. Until 1 November 2026 each organisation gets 500 free checks a month for each of the first four. From 1 November that becomes $10 of credit a month, with optional Growth ($99 a month) and Scale ($299 a month) plans. Sandbox applications are not billed (https://docs.didit.me/getting-started/pricing, checked 2026-10-08).", "priceSummary": "$0.15 / tx", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the OpenAPI spec, the docs index or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": 156, "popularity": { "githubStars": 0, "npmWeekly": 27338, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://docs.didit.me", "llmsTxt": "https://docs.didit.me/llms.txt", "openapi": "https://docs.didit.me/openapi-25.json", "registryName": "me.didit/mcp", "capabilities": [ "kyc.identity", "kyc.documents", "kyc.screening", "kyc.business", "kyc.cases" ], "tags": [ "hosted", "api-key", "oauth", "mcp", "webhooks", "openapi", "llms-txt", "free-tier", "no-card", "sandbox", "status-page", "sla", "soc2", "iso27001" ], "lastRelease": "2026-10-08", "graded": true, "anchor": { "graded": true, "score": 75, "grade": "BB", "agentReady": true, "rank": 63, "ranked": true, "rankOf": 1076, "categoryRank": 2, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 69, "maintenance": 82, "payments": 60, "reliability": 80, "schema": 88, "security": 76, "transparency": 63 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "A self-serve verification API with public per-check prices, key registration by API, scoped keys and a 365-day audit log. The status page shows three incidents marked major between 22 July and 4 September 2026, each a partial outage of the core APIs, and the sub-processor list isn't public.", "bestFor": "A team that wants document, liveness, screening and business registry checks from one API with public prices and no sales step, and an agent that has to set itself up.", "strengths": [ "An account and API key can be created by API at `apx.didit.me/auth/v2/programmatic/register/`, with an emailed code and no browser step", "Public OpenAPI 3.0.0 spec with 256 operations, plus llms.txt and a Markdown copy of every docs page", "Named API keys take read or write access per resource, workflow limits, an IP allowlist and an expiry date, and rotation keeps the old secret for 24 hours", "429 responses carry `Retry-After`, limits are published per scope, and 31 operations document an `Idempotency-Key` header or a reuse rule", "Per-check prices are public, charged only when a check finishes, with 500 free checks a month per core feature until 1 November 2026" ], "weaknesses": [ "Three incidents marked major on status.didit.me from 22 July to 4 September 2026, each a partial outage of the core APIs traced to the primary database", "No server-side SDK in any language. The published SDKs are capture clients for web, iOS, Android, React Native and Flutter", "The data processing addendum says the sub-processor list is published at `/terms/sub-processors`, but that address shows the legal index, which says the list is sent after a signed NDA", "Verification data is used for model training by default until an organisation owner turns it off in the console", "The hosted MCP server lists 156 tools to a signed-in user, 23 of them destructive, and role checks run in a mode that logs without hiding tools by default" ], "agentNotes": [ "Register with `POST https://apx.didit.me/auth/v2/programmatic/register/`, then `verify-email` with the emailed 6-character code. Use a real inbox, because reserved test domains return 500.", "Send the key as `x-api-key` to `https://verification.didit.me/v3/`. The JWT from registration works only on `apx.didit.me`.", "Create a workflow before `POST /v3/session/`. `workflow_id` is the only required field, and an unfinished session with the same `vendor_data` is returned again.", "Read results from webhooks and use `GET /v3/session/{sessionId}/decision/` for back-fill. Every per-feature result is a plural array.", "The MCP server at `https://mcp.didit.me/mcp` takes OAuth sign-in only, never an API key. Approve `didit:verification` alone when the task doesn't change workflows or keys." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 75 } ], "editorialScores": { "ergonomics": 69, "maintenance": 82, "payments": 60, "reliability": 80, "schema": 88, "security": 76, "transparency": 53 }, "provenanceScore": 73 }, "connect": { "http": "curl -X POST https://verification.didit.me/v3/session/ \\\n -H \"x-api-key: $DIDIT_API_KEY\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"workflow_id\":\"\u003cWORKFLOW_ID\u003e\",\"vendor_data\":\"user-42\",\"callback\":\"https://myapp.com/return\"}'", "claudeCode": "claude mcp add --transport http didit https://mcp.didit.me/mcp", "config": { "mcpServers": { "didit": { "url": "https://mcp.didit.me/mcp" } } } }, "letme": { "capability": "https://letme.dev/kyc.identity", "tool": "https://letme.dev/didit" }, "area": "domain-data", "unitPrices": [ { "item": "ID verification in a workflow (document capture)", "unit": "tx", "usd": 0.15, "note": "500 free a month until 1 November 2026" }, { "item": "Passive liveness in a workflow", "unit": "tx", "usd": 0.1, "note": "500 free a month until 1 November 2026" }, { "item": "Face match 1:1 in a workflow", "unit": "tx", "usd": 0.05, "note": "500 free a month until 1 November 2026" }, { "item": "Device and IP analysis in a workflow", "unit": "tx", "usd": 0.03, "note": "500 free a month until 1 November 2026" }, { "item": "AML screening", "unit": "tx", "usd": 0.2, "note": "no free allowance" }, { "item": "Proof of address", "unit": "tx", "usd": 0.2, "note": "no free allowance" }, { "item": "KYB registry, per selected company (Lite profile)", "unit": "tx", "usd": 2, "note": "search is charged separately at up to $0.50" } ], "provenance": { "legalEntity": "Didit Identity Spain, S.L.", "domain": "didit.me", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://didit.me/terms/business/", "privacy": "https://didit.me/terms/privacy-policy/", "statusPage": "https://status.didit.me", "changelog": "https://docs.didit.me/changelog/september-2026", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The Business Terms and Conditions (updated 23 September 2026) name two contracting entities. Didit Identity Spain, S.L., CIF B22929327, Barcelona, contracts with clients in the EU, EEA, UK and Switzerland, and Didit Identity, Inc., Dover, Delaware, with clients elsewhere.", "The Business Terms are the self-serve contract and include the SLA as Annex 1 and the Data Processing Addendum as Annex 2. A separate Master Services Agreement covers enterprise order forms.", "The Privacy Policy was updated on 7 October 2026 and names the Spanish Data Protection Agency as lead supervisory authority. A Verification Privacy Notice supplements it for end users.", "didit.me/.well-known/security.txt and docs.didit.me/.well-known/security.txt return 404. The Information Security Policy sends reports to security@didit.me.", "The API answers at verification.didit.me, account routes at apx.didit.me and the MCP server at mcp.didit.me, all on the vendor's domain.", "The registration date of didit.me wasn't established. whois returned nothing and rdap.org has no RDAP service for .me." ], "score": 73 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/didit.json", "live": { "slug": "didit", "probe": { "target": "https://verification.didit.me", "method": "get", "lastAt": "2026-10-14T09:41:48.745025832Z", "lastOk": true, "lastStatus": 404, "lastMs": 325, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 61, "p95ms24h": 149, "samples24h": 248, "samples30d": 1389, "days": [ { "date": "2026-10-08", "probes": 50, "ok": 50 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 100, "ok": 100 } ] }, "vendorStatus": { "page": "https://status.didit.me", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-14T09:39:05.82665204Z" }, "versions": [ { "registry": "mcp-registry", "name": "me.didit/mcp", "version": "5.0.1", "seenAt": "2026-10-14T04:18:30.41681267Z" }, { "registry": "npm", "name": "@didit-protocol/mcp-server", "version": "5.1.36", "seenAt": "2026-10-13T22:53:08.55424519Z" }, { "registry": "npm", "name": "@didit-protocol/sdk-react-native", "version": "4.9.1", "seenAt": "2026-10-13T22:53:10.755479798Z" }, { "registry": "npm", "name": "@didit-protocol/sdk-web", "version": "0.4.0", "seenAt": "2026-10-13T22:53:09.3554505Z" } ], "githubStars": 0, "npmWeekly": 1132, "securityTxt": { "url": "https://didit.me/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-13T15:45:51.737049528Z" }, "llmsTxt": { "url": "https://docs.didit.me/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-13T14:11:23.094991426Z" }, "domain": { "domain": "didit.me", "checkedAt": "2026-10-11T13:12:22.673163614Z" }, "pages": [ { "url": "https://docs.didit.me/changelog/september-2026", "kind": "changelog", "status": 200, "checkedAt": "2026-10-13T20:14:42.617522581Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "27cc95453999" }, { "url": "https://docs.didit.me/getting-started/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-13T20:14:44.918284015Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "9bca969c5102" }, { "url": "https://didit.me/terms/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-13T20:13:53.175706613Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "b971fafcf494" }, { "url": "https://didit.me/terms/business/", "kind": "terms", "status": 200, "checkedAt": "2026-10-13T20:13:50.607671313Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "293d1878de09" } ], "updatedAt": "2026-10-14T09:41:48.745025832Z" } }, "answer": "Didit scores 75 (BB) on agent readiness against Entrust Identity Verification (formerly Onfido)'s 62.1 (B), and leads in 6 of 7 scored categories. Entrust Identity Verification (formerly Onfido) leads on transparency \u0026 trust.", "b": { "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" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Didit Identity Spain, S.L.", "b": "Onfido Ltd (Entrust)", "name": "Vendor" }, { "a": "https://verification.didit.me", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP, stdio", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Didit's Business Terms and Conditions. The MCP server in didit-protocol/mcp is MIT", "b": "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", "name": "Licence" }, { "a": "156", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "me.didit/mcp", "b": "not listed", "name": "MCP registry" }, { "a": "2026-10-08", "b": "2026-08-31", "name": "Last release" }, { "a": "2026-09-23", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2026-10-07", "b": "", "name": "Privacy policy last updated" }, { "a": "yes, with an opt-out", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "yes", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "0 stars, 27k npm/wk", "b": "59k npm/wk, 27k PyPI/wk", "name": "Popularity" } ], "faq": [ { "answer": "Didit scores 75 (BB) on agent readiness against Entrust Identity Verification (formerly Onfido)'s 62.1 (B), and leads in 6 of 7 scored categories. Entrust Identity Verification (formerly Onfido) leads on transparency \u0026 trust.", "question": "Which is better for AI agents, Didit or Entrust Identity Verification (formerly Onfido)?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Didit and Entrust Identity Verification (formerly Onfido) need an API key?" }, { "answer": "Didit has a hosted endpoint at https://verification.didit.me. No hosted endpoint is listed for Entrust Identity Verification (formerly Onfido).", "question": "Can an agent call Didit and Entrust Identity Verification (formerly Onfido) without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 80 against 70", "Security \u0026 auth, 76 against 58", "Payments \u0026 pricing, 60 against 20", "Maintenance \u0026 community, 82 against 58" ], "also": [ "Agent-ready, a grade of BB or better", "A hosted endpoint, with nothing to install", "Runs on your own machine", "Free to start without a card" ], "goodFor": "A team that wants document, liveness, screening and business registry checks from one API with public prices and no sales step, and an agent that has to set itself up.", "slug": "didit", "watchFor": "Three incidents marked major on status.didit.me from 22 July to 4 September 2026, each a partial outage of the core APIs traced to the primary database" }, { "aheadOn": [ "Transparency \u0026 trust, 70 against 63" ], "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" } ], "job": { "capability": "kyc.identity", "name": "Identity verification" }, "others": [ { "json": "https://www.anchorterminal.com/compare/alloy-vs-didit.json", "title": "Alloy vs Didit", "url": "https://www.anchorterminal.com/compare/alloy-vs-didit" }, { "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/complycube-vs-didit.json", "title": "ComplyCube vs Didit", "url": "https://www.anchorterminal.com/compare/complycube-vs-didit" }, { "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/didit-vs-jumio.json", "title": "Didit vs Jumio", "url": "https://www.anchorterminal.com/compare/didit-vs-jumio" }, { "json": "https://www.anchorterminal.com/compare/didit-vs-middesk.json", "title": "Didit vs Middesk", "url": "https://www.anchorterminal.com/compare/didit-vs-middesk" }, { "json": "https://www.anchorterminal.com/compare/didit-vs-persona.json", "title": "Didit vs Persona", "url": "https://www.anchorterminal.com/compare/didit-vs-persona" }, { "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/didit-vs-shufti.json", "title": "Didit vs Shufti", "url": "https://www.anchorterminal.com/compare/didit-vs-shufti" }, { "json": "https://www.anchorterminal.com/compare/didit-vs-socure-riskos.json", "title": "Didit vs Socure RiskOS", "url": "https://www.anchorterminal.com/compare/didit-vs-socure-riskos" }, { "json": "https://www.anchorterminal.com/compare/didit-vs-stripe-identity.json", "title": "Didit vs Stripe Identity", "url": "https://www.anchorterminal.com/compare/didit-vs-stripe-identity" }, { "json": "https://www.anchorterminal.com/compare/didit-vs-sumsub.json", "title": "Didit vs Sumsub", "url": "https://www.anchorterminal.com/compare/didit-vs-sumsub" }, { "json": "https://www.anchorterminal.com/compare/didit-vs-trulioo.json", "title": "Didit vs Trulioo", "url": "https://www.anchorterminal.com/compare/didit-vs-trulioo" }, { "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/didit-vs-vouched.json", "title": "Didit vs Vouched", "url": "https://www.anchorterminal.com/compare/didit-vs-vouched" }, { "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-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/complyadvantage-vs-didit.json", "title": "ComplyAdvantage vs Didit", "url": "https://www.anchorterminal.com/compare/complyadvantage-vs-didit" }, { "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" } ], "scores": [ { "by": 10, "didit": 80, "edge": "didit", "entrust-identity-verification": 70, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 4, "didit": 88, "edge": "didit", "entrust-identity-verification": 84, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 4, "didit": 69, "edge": "didit", "entrust-identity-verification": 65, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 18, "didit": 76, "edge": "didit", "entrust-identity-verification": 58, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 40, "didit": 60, "edge": "didit", "entrust-identity-verification": 20, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 24, "didit": 82, "edge": "didit", "entrust-identity-verification": 58, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 7, "didit": 63, "edge": "entrust-identity-verification", "entrust-identity-verification": 70, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Didit scores 75 (BB) on agent readiness against Entrust Identity Verification (formerly Onfido)'s 62.1 (B), and leads in 6 of 7 scored categories. Entrust Identity Verification (formerly Onfido) leads on transparency \u0026 trust. Both do identity verification.", "verdicts": { "didit": "A self-serve verification API with public per-check prices, key registration by API, scoped keys and a 365-day audit log. The status page shows three incidents marked major between 22 July and 4 September 2026, each a partial outage of the core APIs, and the sub-processor list isn't public.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/didit-vs-entrust-identity-verification", "json": "https://www.anchorterminal.com/compare/didit-vs-entrust-identity-verification.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/didit-vs-entrust-identity-verification.md", "slim": "https://www.anchorterminal.com/compare/didit-vs-entrust-identity-verification.min.md" }, "markdown": "Didit scores 75 (BB) on agent readiness against Entrust Identity Verification (formerly Onfido)'s 62.1 (B), and leads in 6 of 7 scored categories. Entrust Identity Verification (formerly Onfido) leads on transparency \u0026 trust. Both do identity verification.\n\n- Didit: grade BB, 75/100, rank #63 of 1076. Markdown https://www.anchorterminal.com/tools/didit.md · JSON https://www.anchorterminal.com/api/v1/tools/didit.json\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- 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### Didit (BB)\n\nGood for: A team that wants document, liveness, screening and business registry checks from one API with public prices and no sales step, and an agent that has to set itself up.\n\nAhead on:\n- Reliability, 80 against 70\n- Security \u0026 auth, 76 against 58\n- Payments \u0026 pricing, 60 against 20\n- Maintenance \u0026 community, 82 against 58\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- A hosted endpoint, with nothing to install\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: Three incidents marked major on status.didit.me from 22 July to 4 September 2026, each a partial outage of the core APIs traced to the primary database\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- Transparency \u0026 trust, 70 against 63\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\n## Score by category\n\n| Category | Weight | Didit | Entrust Identity Verification (formerly Onfido) | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 80 | 70 | Didit +10 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 88 | 84 | Didit +4 |\n| Agent ergonomics | 13% (16.2 this run) | 69 | 65 | Didit +4 |\n| Security \u0026 auth | 14% (17.5 this run) | 76 | 58 | Didit +18 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 60 | 20 | Didit +40 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 82 | 58 | Didit +24 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 63 | 70 | Entrust Identity Verification (formerly Onfido) +7 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **75 · BB** | **62.1 · B** | |\n\n## Facts side by side\n\n| Fact | Didit | Entrust Identity Verification (formerly Onfido) |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Didit Identity Spain, S.L. | Onfido Ltd (Entrust) |\n| Hosted endpoint | `https://verification.didit.me` | no (local only) |\n| Transports | HTTP, Streamable HTTP, stdio | HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Pay per use | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under Didit's Business Terms and Conditions. The MCP server in didit-protocol/mcp is MIT | 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 |\n| Tools exposed | 156 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `me.didit/mcp` | not listed |\n| Last release | 2026-10-08 | 2026-08-31 |\n| Terms last updated | 2026-09-23 | couldn't be read |\n| Privacy policy last updated | 2026-10-07 | |\n| Customer content may train models | yes, with an opt-out | couldn't be read |\n| Terms restrict automated access | not found in the text | couldn't be read |\n| Terms restrict benchmarking | yes | couldn't be read |\n| Terms or service can change without notice | not found in the text | couldn't be read |\n| Arbitration or class-action waiver | not found in the text | couldn't be read |\n| Popularity | 0 stars, 27k npm/wk | 59k npm/wk, 27k PyPI/wk |\n\n## Verdicts\n\n**Didit.** A self-serve verification API with public per-check prices, key registration by API, scoped keys and a 365-day audit log. The status page shows three incidents marked major between 22 July and 4 September 2026, each a partial outage of the core APIs, and the sub-processor list isn't public.\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## Before you call either\n\n### Didit\n\n1. Register with `POST https://apx.didit.me/auth/v2/programmatic/register/`, then `verify-email` with the emailed 6-character code. Use a real inbox, because reserved test domains return 500.\n2. Send the key as `x-api-key` to `https://verification.didit.me/v3/`. The JWT from registration works only on `apx.didit.me`.\n3. Create a workflow before `POST /v3/session/`. `workflow_id` is the only required field, and an unfinished session with the same `vendor_data` is returned again.\n4. Read results from webhooks and use `GET /v3/session/{sessionId}/decision/` for back-fill. Every per-feature result is a plural array.\n5. The MCP server at `https://mcp.didit.me/mcp` takes OAuth sign-in only, never an API key. Approve `didit:verification` alone when the task doesn't change workflows or keys.\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## Questions\n\n### Which is better for AI agents, Didit or Entrust Identity Verification (formerly Onfido)?\n\nDidit scores 75 (BB) on agent readiness against Entrust Identity Verification (formerly Onfido)'s 62.1 (B), and leads in 6 of 7 scored categories. Entrust Identity Verification (formerly Onfido) leads on transparency \u0026 trust.\n\n### Do Didit and Entrust Identity Verification (formerly Onfido) need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Didit and Entrust Identity Verification (formerly Onfido) without installing anything?\n\nDidit has a hosted endpoint at https://verification.didit.me. No hosted endpoint is listed for Entrust Identity Verification (formerly Onfido).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/didit-vs-entrust-identity-verification.json, and with the fewest tokens: https://www.anchorterminal.com/compare/didit-vs-entrust-identity-verification.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"didit\", \"b\": \"entrust-identity-verification\"}`. From a terminal: `anchor compare didit entrust-identity-verification`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/didit.json and https://www.anchorterminal.com/api/v1/tools/entrust-identity-verification.json\n\n## Other comparisons with Didit or Entrust Identity Verification (formerly Onfido)\n\n- [Alloy vs Didit](https://www.anchorterminal.com/compare/alloy-vs-didit.md)\n- [Alloy vs Entrust Identity Verification (formerly Onfido)](https://www.anchorterminal.com/compare/alloy-vs-entrust-identity-verification.md)\n- [ComplyCube vs Didit](https://www.anchorterminal.com/compare/complycube-vs-didit.md)\n- [ComplyCube vs Entrust Identity Verification (formerly Onfido)](https://www.anchorterminal.com/compare/complycube-vs-entrust-identity-verification.md)\n- [Didit vs Jumio](https://www.anchorterminal.com/compare/didit-vs-jumio.md)\n- [Didit vs Middesk](https://www.anchorterminal.com/compare/didit-vs-middesk.md)\n- [Didit vs Persona](https://www.anchorterminal.com/compare/didit-vs-persona.md)\n- [Didit vs Plaid Identity Verification](https://www.anchorterminal.com/compare/didit-vs-plaid-identity-verification.md)\n- [Didit vs Shufti](https://www.anchorterminal.com/compare/didit-vs-shufti.md)\n- [Didit vs Socure RiskOS](https://www.anchorterminal.com/compare/didit-vs-socure-riskos.md)\n- [Didit vs Stripe Identity](https://www.anchorterminal.com/compare/didit-vs-stripe-identity.md)\n- [Didit vs Sumsub](https://www.anchorterminal.com/compare/didit-vs-sumsub.md)\n- [Didit vs Trulioo](https://www.anchorterminal.com/compare/didit-vs-trulioo.md)\n- [Didit vs Veriff](https://www.anchorterminal.com/compare/didit-vs-veriff.md)\n- [Didit vs Vouched](https://www.anchorterminal.com/compare/didit-vs-vouched.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 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- [ComplyAdvantage vs Didit](https://www.anchorterminal.com/compare/complyadvantage-vs-didit.md)\n- [ComplyAdvantage vs Entrust Identity Verification (formerly Onfido)](https://www.anchorterminal.com/compare/complyadvantage-vs-entrust-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": "Didit vs Entrust Identity Verification (formerly Onfido)", "url": "" } ], "description": "Didit scores 75 (BB) to Entrust Identity Verification's 62.1 (B) for identity verification. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Didit BB 75", "Entrust Identity Verification (formerly Onfido) B 62.1", "scores" ], "h1": "Didit vs Entrust Identity Verification (formerly Onfido)", "image": "https://www.anchorterminal.com/assets/og/compare-didit-vs-entrust-identity-verification.png", "path": "/compare/didit-vs-entrust-identity-verification", "published": "2026-10-01", "section": "tools", "title": "Didit vs Entrust Identity Verification for AI agents (2026)", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/didit-vs-entrust-identity-verification" }, "tokens": { "markdown": 3000, "slim": 830 }, "version": 1 }