Head to head · Identity verification · October 2026 research run
Entrust Identity Verification (formerly Onfido) vs Socure RiskOS
Socure RiskOS scores 63.5 (B) on agent readiness against Entrust Identity Verification (formerly Onfido)'s 62.1 (B), and leads in 4 of 7 scored categories. Entrust Identity Verification (formerly Onfido) leads on agent ergonomics. 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
- Agent ergonomics, 65 against 46
Watch for
entrust.com answered 403 to every request, so the terms, privacy notice, pricing page and security.txt weren't read
Best for A company in the United States that wants one decision from combined KYC, document, fraud and watchlist checks through a single evaluation call.
Ahead on
- Reliability, 75 against 70
- Payments & pricing, 35 against 20
- Maintenance & community, 75 against 58
Also in its favour
- A hosted endpoint, with nothing to install
Watch for
No service agreement or API terms are published. The only terms pages are website terms of use and end-user terms for document capture
Score by category
| Category | Weight this run | Entrust Identity Verification (formerly Onfido) | Socure RiskOS | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 70 | 75 | Socure RiskOS +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 84 | 84 | even |
| Agent ergonomics | 13%16.2 | 65 | 46 | Entrust Identity Verification (formerly Onfido) +19 |
| Security & auth | 14%17.5 | 58 | 60 | Socure RiskOS +2 |
| Payments & pricing | 10%12.5 | 20 | 35 | Socure RiskOS +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 58 | 75 | Socure RiskOS +17 |
| Transparency & trust | 7%8.8 | 70 | 68 | Entrust Identity Verification (formerly Onfido) +2 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 62.1/100 | B 63.5/100 |
Facts side by side
| Fact | Entrust Identity Verification (formerly Onfido) | Socure RiskOS |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Onfido Ltd (Entrust) | Socure Inc. |
| Hosted endpoint | no (local only) | https://mcp.riskos.socure.com/sandbox |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Paid | Pay per use |
| 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. No service agreement is published, and the OpenAPI file states its licence as Proprietary |
| Tools exposed | none | 9 |
| 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 | no document linked |
| Privacy policy last updated | no date given | |
| Customer content may train models | couldn't be read | yes |
| 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 | 35k 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.
Socure RiskOS
A public OpenAPI file, llms.txt, 15 documented error codes and dated release notes cover a ten-operation REST API, and Socure Launch publishes prices from $0.80 an evaluation with a free sandbox. API keys carry no scopes, no idempotency header is defined, no service terms are published, and production stays at zero requests until Socure activates it.
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
Socure RiskOS
- Send
Authorization: Bearer <key>tohttps://riskos.sandbox.socure.com/api/evaluationfor tests andhttps://riskos.socure.com/api/evaluationfor live checks. The two environments use separate keys. - Use dummy data only in the sandbox. It returns predefined results, connects to no live data source and expects the documented test values.
- Store the
eval_idfrom everyPOST /api/evaluationresponse. No list or search endpoint exists to find it later. - On 429 wait the seconds given in
X-Retry-After. Do not blindly resend a failedPOST /api/evaluation, because no idempotency header is documented and Launch bills each initiated evaluation. - The MCP server at
https://mcp.riskos.socure.com/sandboxreads docs, workflows and webhooks with its own MCP Server Key. It cannot run evaluations or read results.
Questions
Which is better for AI agents, Entrust Identity Verification (formerly Onfido) or Socure RiskOS?
Socure RiskOS scores 63.5 (B) on agent readiness against Entrust Identity Verification (formerly Onfido)'s 62.1 (B), and leads in 4 of 7 scored categories. Entrust Identity Verification (formerly Onfido) leads on agent ergonomics.
Do Entrust Identity Verification (formerly Onfido) and Socure RiskOS need an API key?
Entrust Identity Verification (formerly Onfido) takes an API key or an OAuth sign-in. Socure RiskOS needs an API key.
Can an agent call Entrust Identity Verification (formerly Onfido) and Socure RiskOS without installing anything?
No hosted endpoint is listed for Entrust Identity Verification (formerly Onfido). Socure RiskOS has a hosted endpoint at https://mcp.riskos.socure.com/sandbox.
Other comparisons with Entrust Identity Verification (formerly Onfido) or Socure RiskOS
- Alloy vs Entrust Identity Verification (formerly Onfido)
- Alloy vs Socure RiskOS
- ComplyCube vs Entrust Identity Verification (formerly Onfido)
- ComplyCube vs Socure RiskOS
- Didit vs Entrust Identity Verification (formerly Onfido)
- Didit vs Socure RiskOS
- 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 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 Socure RiskOS
- Persona vs Socure RiskOS
- Plaid Identity Verification vs Socure RiskOS
- Shufti vs Socure RiskOS
- Socure RiskOS vs Stripe Identity
- Socure RiskOS vs Sumsub
- Socure RiskOS vs Trulioo
- Socure RiskOS vs Veriff
- Socure RiskOS vs Vouched
- ComplyAdvantage vs Entrust Identity Verification (formerly Onfido)
- ComplyAdvantage vs Socure RiskOS
- Middesk vs Socure RiskOS
Machine-readable
- This page as Markdown
/compare/entrust-identity-verification-vs-socure-riskos.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/entrust-identity-verification.json·/api/v1/tools/socure-riskos.json - From a terminal
anchor compare entrust-identity-verification socure-riskos(the CLI) - Over MCP
compare_tools {"a": "entrust-identity-verification", "b": "socure-riskos"}at/mcp, no key