Head to head · Identity verification · October 2026 research run
Entrust Identity Verification (formerly Onfido) vs Shufti
Entrust Identity Verification (formerly Onfido) scores 62.1 (B) on agent readiness against Shufti's 57.8 (C), and leads in 3 of 7 scored categories. Shufti leads on payments & pricing and maintenance & community. Both do identity verification.
Best identity and business verification APIs for AI agents · All 119 verification comparisons
Which one, for what
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
- Reliability, 70 against 65
- Schema & documentation, 84 against 58
- Agent ergonomics, 65 against 47
Watch for
entrust.com answered 403 to every request, so the terms, privacy notice, pricing page and security.txt weren't read
Shufti C
Best for A team that wants document, face, address, AML and KYB checks behind one endpoint, a free plan for low volume, and an MCP server that hands the person a hosted verification link.
Ahead on
- Payments & pricing, 35 against 20
- Maintenance & community, 72 against 58
Also in its favour
- A hosted endpoint, with nothing to install
- Free to start without a card
Watch for
No OpenAPI file or other machine-readable contract was found. The reference is prose tables plus Postman collections
Score by category
| Category | Weight this run | Entrust Identity Verification (formerly Onfido) | Shufti | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 70 | 65 | Entrust Identity Verification (formerly Onfido) +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 84 | 58 | Entrust Identity Verification (formerly Onfido) +26 |
| Agent ergonomics | 13%16.2 | 65 | 47 | Entrust Identity Verification (formerly Onfido) +18 |
| Security & auth | 14%17.5 | 58 | 62 | Shufti +4 |
| Payments & pricing | 10%12.5 | 20 | 35 | Shufti +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 58 | 72 | Shufti +14 |
| Transparency & trust | 7%8.8 | 70 | 71 | Shufti +1 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 62.1/100 | C 57.8/100 |
Facts side by side
| Fact | Entrust Identity Verification (formerly Onfido) | Shufti |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Onfido Ltd (Entrust) | Shufti Pro Limited |
| Hosted endpoint | no (local only) | https://api.shuftipro.com |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| 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 Shufti's Terms and Conditions. The licences of the mobile capture SDKs were not checked |
| Tools exposed | none | 25 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-08-31 | 2026-10-06 |
| Terms last updated | couldn't be read | |
| Privacy policy last updated | 2026-09-01 | |
| Customer content may train models | couldn't be read | yes, with an opt-out |
| Terms restrict automated access | couldn't be read | |
| Terms restrict benchmarking | couldn't be read | |
| Terms or service can change without notice | couldn't be read | |
| Arbitration or class-action waiver | couldn't be read | |
| Popularity | 59k npm/wk, 27k PyPI/wk | 673 npm/wk |
Verdicts
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.
Shufti
One endpoint covers document, face, address, AML and KYB checks, with a free plan of 10 verifications a month, and a hosted MCP server adds OAuth with three scopes. No OpenAPI file, server SDK or idempotency key was found, and the status page history could not be read.
Before you call either
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
Shufti
- POST every verification to
https://api.shuftipro.com/with a uniquereferenceof 6 to 250 characters and one object per service. Read results from/statuswith that reference - Register the callback domain in the back office first. An unregistered
callback_urlis rejected - Stay under 60 requests a minute per IP on a production account and 20 on a trial account
- Check the
Signatureresponse header. Accounts created after 15 March 2023 hash the Secret Key with SHA-256 before appending it to the raw response - Through MCP, identity checks return a
verification_urlfor the person to open. No tool accepts an image, so use the REST API for offsite proofs
Questions
Which is better for AI agents, Entrust Identity Verification (formerly Onfido) or Shufti?
Entrust Identity Verification (formerly Onfido) scores 62.1 (B) on agent readiness against Shufti's 57.8 (C), and leads in 3 of 7 scored categories. Shufti leads on payments & pricing and maintenance & community.
Do Entrust Identity Verification (formerly Onfido) and Shufti need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Entrust Identity Verification (formerly Onfido) and Shufti without installing anything?
No hosted endpoint is listed for Entrust Identity Verification (formerly Onfido). Shufti has a hosted endpoint at https://api.shuftipro.com.
Other comparisons with Entrust Identity Verification (formerly Onfido) or Shufti
- Alloy vs Entrust Identity Verification (formerly Onfido)
- Alloy vs Shufti
- ComplyCube vs Entrust Identity Verification (formerly Onfido)
- ComplyCube vs Shufti
- Didit vs Entrust Identity Verification (formerly Onfido)
- Didit vs Shufti
- 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 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
- Jumio vs Shufti
- Persona vs Shufti
- Plaid Identity Verification vs Shufti
- Shufti vs Socure RiskOS
- Shufti vs Stripe Identity
- Shufti vs Sumsub
- Shufti vs Trulioo
- Shufti vs Veriff
- Shufti vs Vouched
- ComplyAdvantage vs Entrust Identity Verification (formerly Onfido)
- ComplyAdvantage vs Shufti
- Middesk vs Shufti
Machine-readable
- This page as Markdown
/compare/entrust-identity-verification-vs-shufti.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/entrust-identity-verification.json·/api/v1/tools/shufti.json - From a terminal
anchor compare entrust-identity-verification shufti(the CLI) - Over MCP
compare_tools {"a": "entrust-identity-verification", "b": "shufti"}at/mcp, no key