Head to head · Sanctions screening · October 2026 research run
ComplyAdvantage vs Entrust Identity Verification (formerly Onfido)
Entrust Identity Verification (formerly Onfido) scores 62.1 (B) on agent readiness against ComplyAdvantage's 52.6 (D), and leads in 5 of 7 scored categories. ComplyAdvantage leads on security & auth. Both do sanctions screening.
Best identity and business verification APIs for AI agents · All 119 verification comparisons
Which one, for what
Best for An agent that screens customers and companies against sanctions, politically exposed person and adverse media data, keeps them under monitoring and works the resulting alerts and cases.
Ahead on
- Security & auth, 68 against 58
Also in its favour
- A hosted endpoint, with nothing to install
Watch for
No public status page or incident history was found. status.complyadvantage.com does not resolve
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 42
- Payments & pricing, 20 against 10
- Maintenance & community, 58 against 28
- Transparency & trust, 70 against 50
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 | ComplyAdvantage | Entrust Identity Verification (formerly Onfido) | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 42 | 70 | Entrust Identity Verification (formerly Onfido) +28 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 82 | 84 | Entrust Identity Verification (formerly Onfido) +2 |
| Agent ergonomics | 13%16.2 | 67 | 65 | ComplyAdvantage +2 |
| Security & auth | 14%17.5 | 68 | 58 | ComplyAdvantage +10 |
| Payments & pricing | 10%12.5 | 10 | 20 | Entrust Identity Verification (formerly Onfido) +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 28 | 58 | Entrust Identity Verification (formerly Onfido) +30 |
| Transparency & trust | 7%8.8 | 50 | 70 | Entrust Identity Verification (formerly Onfido) +20 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 52.6/100 | B 62.1/100 |
Facts side by side
| Fact | ComplyAdvantage | Entrust Identity Verification (formerly Onfido) |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | IVXS UK Limited (trading as ComplyAdvantage) | Onfido Ltd (Entrust) |
| Hosted endpoint | https://api.mesh.complyadvantage.com | no (local only) |
| Transports | HTTP | HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | Proprietary service. No service agreement is published, and the terms page on complyadvantage.com covers the website only | 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 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-16 | 2026-08-31 |
| Terms last updated | no document linked | couldn't be read |
| Privacy policy last updated | 2026-06-12 | |
| Customer content may train models | couldn't be read | |
| 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 | none | 59k npm/wk, 27k PyPI/wk |
Verdicts
ComplyAdvantage
The Mesh API has a public OpenAPI 3.0.3 spec with 165 described operations, per-credential permissions and audit log endpoints, which suits an agent screening customers and working alerts. No status page, changelog, SDK, service agreement or subprocessor list was found in public, and access starts with a paid plan bought by a person.
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
ComplyAdvantage
- Exchange the access key and secret at
POST /v3/tokenfor a bearer token. It lasts 24 hours and can't be refreshed, so request a new one before expiry - Ask for a credential with only the permissions the task needs. Permissions can't be edited later, and each reference page names the ones a call requires
- Create a screening configuration first and keep its
configuration_identifier. Creating and screening a customer needs it - Give each customer a unique external identifier. A concurrent request for the same identifier returns 409 with a pointer to the first workflow
- Read
Ratelimit-RemainingandRatelimit-Reseton every response. A 429 body is onlyAPI rate limit exceeded
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, ComplyAdvantage or Entrust Identity Verification (formerly Onfido)?
Entrust Identity Verification (formerly Onfido) scores 62.1 (B) on agent readiness against ComplyAdvantage's 52.6 (D), and leads in 5 of 7 scored categories. ComplyAdvantage leads on security & auth.
Do ComplyAdvantage and Entrust Identity Verification (formerly Onfido) need an API key?
ComplyAdvantage uses an OAuth sign-in. Entrust Identity Verification (formerly Onfido) takes an API key or an OAuth sign-in.
Can an agent call ComplyAdvantage and Entrust Identity Verification (formerly Onfido) without installing anything?
ComplyAdvantage has a hosted endpoint at https://api.mesh.complyadvantage.com. No hosted endpoint is listed for Entrust Identity Verification (formerly Onfido).
Other comparisons with ComplyAdvantage or Entrust Identity Verification (formerly Onfido)
- Alloy vs Entrust Identity Verification (formerly Onfido)
- ComplyCube vs Entrust Identity Verification (formerly Onfido)
- Didit vs Entrust Identity Verification (formerly Onfido)
- 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
- Alloy vs ComplyAdvantage
- ComplyAdvantage vs ComplyCube
- ComplyAdvantage vs Didit
- ComplyAdvantage vs Jumio
- ComplyAdvantage vs Middesk
- ComplyAdvantage vs Persona
- ComplyAdvantage vs Plaid Identity Verification
- ComplyAdvantage vs Shufti
- ComplyAdvantage vs Socure RiskOS
- ComplyAdvantage vs Sumsub
- ComplyAdvantage vs Trulioo
- ComplyAdvantage vs Veriff
- ComplyAdvantage vs Vouched
Machine-readable
- This page as Markdown
/compare/complyadvantage-vs-entrust-identity-verification.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/complyadvantage.json·/api/v1/tools/entrust-identity-verification.json - From a terminal
anchor compare complyadvantage entrust-identity-verification(the CLI) - Over MCP
compare_tools {"a": "complyadvantage", "b": "entrust-identity-verification"}at/mcp, no key