Head to head · Identity verification · October 2026 research run
Didit vs Entrust Identity Verification (formerly Onfido)
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 & trust. Both do identity verification.
Best identity and business verification APIs for AI agents · All 119 verification comparisons
Which one, for what
Didit BB
Best 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.
Ahead on
- Reliability, 80 against 70
- Security & auth, 76 against 58
- Payments & pricing, 60 against 20
- Maintenance & community, 82 against 58
Also in its favour
- 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
Watch 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
Entrust Identity Verification (formerly Onfido) B
Best for A company already contracted with Entrust that wants an agent to create applicants, start workflow runs and read reports through typed libraries and a public spec.
Ahead on
- Transparency & trust, 70 against 63
Watch for
entrust.com answered 403 to every request, so the terms, privacy notice, pricing page and security.txt weren't read
Score by category
| Category | Weight this run | Didit | Entrust Identity Verification (formerly Onfido) | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 80 | 70 | Didit +10 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 88 | 84 | Didit +4 |
| Agent ergonomics | 13%16.2 | 69 | 65 | Didit +4 |
| Security & auth | 14%17.5 | 76 | 58 | Didit +18 |
| Payments & pricing | 10%12.5 | 60 | 20 | Didit +40 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 82 | 58 | Didit +24 |
| Transparency & trust | 7%8.8 | 63 | 70 | Entrust Identity Verification (formerly Onfido) +7 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 75/100 | B 62.1/100 |
Facts side by side
| Fact | Didit | Entrust Identity Verification (formerly Onfido) |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Didit Identity Spain, S.L. | Onfido Ltd (Entrust) |
| Hosted endpoint | https://verification.didit.me | no (local only) |
| Transports | HTTP, Streamable HTTP, stdio | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Paid |
| x402 | no | no |
| 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 |
| Tools exposed | 156 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | me.didit/mcp | not listed |
| Last release | 2026-10-08 | 2026-08-31 |
| Terms last updated | 2026-09-23 | couldn't be read |
| Privacy policy last updated | 2026-10-07 | |
| Customer content may train models | yes, with an opt-out | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | 0 stars, 27k npm/wk | 59k npm/wk, 27k PyPI/wk |
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 (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.
Before you call either
Didit
- Register with
POST https://apx.didit.me/auth/v2/programmatic/register/, thenverify-emailwith the emailed 6-character code. Use a real inbox, because reserved test domains return 500. - Send the key as
x-api-keytohttps://verification.didit.me/v3/. The JWT from registration works only onapx.didit.me. - Create a workflow before
POST /v3/session/.workflow_idis the only required field, and an unfinished session with the samevendor_datais 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/mcptakes OAuth sign-in only, never an API key. Approvedidit:verificationalone when the task doesn't change workflows or keys.
Entrust Identity Verification (formerly Onfido)
- 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_limiterror - 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-Signatureover the raw body
Questions
Which is better for AI agents, Didit or Entrust Identity Verification (formerly Onfido)?
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 & trust.
Do Didit and Entrust Identity Verification (formerly Onfido) need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Didit and Entrust Identity Verification (formerly Onfido) without installing anything?
Didit has a hosted endpoint at https://verification.didit.me. No hosted endpoint is listed for Entrust Identity Verification (formerly Onfido).
Other comparisons with Didit or Entrust Identity Verification (formerly Onfido)
- Alloy vs Didit
- Alloy vs Entrust Identity Verification (formerly Onfido)
- ComplyCube vs Didit
- ComplyCube vs Entrust Identity Verification (formerly Onfido)
- Didit vs Jumio
- Didit vs Middesk
- Didit vs Persona
- Didit vs Plaid Identity Verification
- Didit vs Shufti
- Didit vs Socure RiskOS
- Didit vs Stripe Identity
- Didit vs Sumsub
- Didit vs Trulioo
- Didit vs Veriff
- Didit vs Vouched
- Entrust Identity Verification (formerly Onfido) vs Jumio
- Entrust Identity Verification (formerly Onfido) vs Middesk
- Entrust Identity Verification (formerly Onfido) vs Persona
- Entrust Identity Verification (formerly Onfido) vs Plaid Identity Verification
- Entrust Identity Verification (formerly Onfido) vs Shufti
- Entrust Identity Verification (formerly Onfido) vs Socure RiskOS
- Entrust Identity Verification (formerly Onfido) vs Stripe Identity
- Entrust Identity Verification (formerly Onfido) vs Sumsub
- Entrust Identity Verification (formerly Onfido) vs Trulioo
- Entrust Identity Verification (formerly Onfido) vs Veriff
- Entrust Identity Verification (formerly Onfido) vs Vouched
- ComplyAdvantage vs Didit
- ComplyAdvantage vs Entrust Identity Verification (formerly Onfido)
Machine-readable
- This page as Markdown
/compare/didit-vs-entrust-identity-verification.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/didit.json·/api/v1/tools/entrust-identity-verification.json - From a terminal
anchor compare didit entrust-identity-verification(the CLI) - Over MCP
compare_tools {"a": "didit", "b": "entrust-identity-verification"}at/mcp, no key