Head to head · Identity verification · October 2026 research run
Entrust Identity Verification (formerly Onfido) vs Middesk
Entrust Identity Verification (formerly Onfido) scores 62.1 (B) on agent readiness against Middesk's 59 (C), and leads in 5 of 7 scored categories. Middesk leads on 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
- Agent ergonomics, 65 against 56
- Payments & pricing, 20 against 10
- Transparency & trust, 70 against 61
Watch for
entrust.com answered 403 to every request, so the terms, privacy notice, pricing page and security.txt weren't read
Middesk C
Best for An agent onboarding or re-checking US businesses for a bank, lender or marketplace that already holds a Middesk contract, with registry, TIN, sanctions and lien data in one object.
Ahead on
- Maintenance & community, 64 against 58
Also in its favour
- A hosted endpoint, with nothing to install
Watch for
No public price. Fees are set in an order form, and every docs page ends with a prompt to contact sales
Score by category
| Category | Weight this run | Entrust Identity Verification (formerly Onfido) | Middesk | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 70 | 73 | Middesk +3 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 84 | 82 | Entrust Identity Verification (formerly Onfido) +2 |
| Agent ergonomics | 13%16.2 | 65 | 56 | Entrust Identity Verification (formerly Onfido) +9 |
| Security & auth | 14%17.5 | 58 | 56 | Entrust Identity Verification (formerly Onfido) +2 |
| Payments & pricing | 10%12.5 | 20 | 10 | Entrust Identity Verification (formerly Onfido) +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 58 | 64 | Middesk +6 |
| Transparency & trust | 7%8.8 | 70 | 61 | Entrust Identity Verification (formerly Onfido) +9 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 62.1/100 | C 59/100 |
Facts side by side
| Fact | Entrust Identity Verification (formerly Onfido) | Middesk |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Onfido Ltd (Entrust) | Middesk, Inc. |
| Hosted endpoint | no (local only) | https://api.middesk.com/v1 |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Paid |
| 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 Middesk's Business Verification Terms and Conditions. The Claude Code and Codex plugins on GitHub are MIT |
| Tools exposed | none | 11 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-08-31 | 2026-10-05 |
| Terms last updated | couldn't be read | no date given |
| 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 | not found in the text |
| Terms restrict benchmarking | couldn't be read | yes |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | yes |
| Popularity | 59k npm/wk, 27k PyPI/wk | 2 stars |
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.
Middesk
A public OpenAPI 3.1 contract for 87 operations, llms.txt, Markdown docs and a dated weekly changelog make the REST API readable to an agent, and OAuth has a read-only scope. Access is sales-led. No price, self-serve signup or official SDK was found, and the hosted MCP server rejects sandbox keys.
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
Middesk
- Match the key to the host.
mk_testkeys work only at https://api-sandbox.middesk.com/v1 andmk_livekeys only at https://api.middesk.com/v1 - Name the
ordersonPOST /v1/businesses. Omitting them places a verification order plus every package the account runs automatically, all billed - Send
address_line1andaddress_line2. The API ignoresaddress_line_1without an error - A 201 means the business was created, not verified. Wait for the
business.updatedwebhook or poll untilstatusleavespending - Stay under 20 requests a second per account, and in sandbox wait the seconds in
Retry-Afterafter a 429 on business creation
Questions
Which is better for AI agents, Entrust Identity Verification (formerly Onfido) or Middesk?
Entrust Identity Verification (formerly Onfido) scores 62.1 (B) on agent readiness against Middesk's 59 (C), and leads in 5 of 7 scored categories. Middesk leads on maintenance & community.
Do Entrust Identity Verification (formerly Onfido) and Middesk need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Entrust Identity Verification (formerly Onfido) and Middesk without installing anything?
No hosted endpoint is listed for Entrust Identity Verification (formerly Onfido). Middesk has a hosted endpoint at https://api.middesk.com/v1.
Other comparisons with Entrust Identity Verification (formerly Onfido) or Middesk
- Alloy vs Entrust Identity Verification (formerly Onfido)
- Alloy vs Middesk
- ComplyCube vs Entrust Identity Verification (formerly Onfido)
- ComplyCube vs Middesk
- Didit vs Entrust Identity Verification (formerly Onfido)
- Didit vs Middesk
- Entrust Identity Verification (formerly Onfido) vs Jumio
- 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
- Jumio vs Middesk
- Middesk vs Plaid Identity Verification
- Middesk vs Stripe Identity
- Middesk vs Veriff
- Middesk vs Vouched
- ComplyAdvantage vs Entrust Identity Verification (formerly Onfido)
- ComplyAdvantage vs Middesk
- Middesk vs Persona
- Middesk vs Shufti
- Middesk vs Socure RiskOS
- Middesk vs Sumsub
- Middesk vs Trulioo
Machine-readable
- This page as Markdown
/compare/entrust-identity-verification-vs-middesk.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/entrust-identity-verification.json·/api/v1/tools/middesk.json - From a terminal
anchor compare entrust-identity-verification middesk(the CLI) - Over MCP
compare_tools {"a": "entrust-identity-verification", "b": "middesk"}at/mcp, no key