Head to head · Identity verification · October 2026 research run
Didit vs Veriff
Didit scores 77.8 (BB) on agent readiness against Veriff's 64.8 (B), and leads in 6 of 7 scored categories. Veriff 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, 90 against 67
- Schema & documentation, 88 against 82
- Agent ergonomics, 69 against 43
- Security & auth, 76 against 63
- Payments & pricing, 90 against 60
- Maintenance & community, 82 against 74
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
- Rated higher by the reviewer agents, 4.0 against 3.3 out of 5
Watch for
Session deletion responses changed from 204 to 200 in August 2026 and batch deletions of over 20 sessions to 202 in October, each announced only in that month's changelog
Veriff B
Best for A team that needs document and selfie verification with public per-verification prices and a trial, and that can run a webhook receiver and HMAC signing.
Ahead on
- Transparency & trust, 69 against 64
Also in its favour
- No incidents deducted, where Didit loses 3 points for them
Watch for
No server-side SDK and no MCP server. Official packages cover only browser and mobile capture
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Payments & pricing Didit +30
Didit 90
No x402, MPP or L402 (0). Per-check prices are public without a login, re-read on 1 November, such as $0.15 for ID verification and $0.20 for AML screening (20). From 1 November 2026 the Free plan gives $10 of credit a month with no card, about 30 full ID checks, for organisations that sign up with a work email, in place of 500 free checks a month per core feature. The sandbox stays free at 500 test sessions a day per application (20). An agent can register and receive an API key through POST /auth/v2/programmatic/register/ and verify-email with no browser. It needs a real inbox for the emailed code, and we scored the line in full (20). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.
Veriff 60
No x402, MPP or L402 (0). Per-verification prices are public, at $0.80, $1.39 and $1.89 with monthly minimums of $49, $99 and $209, and add-ons priced per verification (20). A 15-day trial of up to 50 sessions with no card, plus free test integrations. The trial starts after the account holder passes identity verification (20). Signup is a browser flow and keys come from the Customer Portal (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Agent ergonomics Didit +26
Didit 69
Graded on the REST API. No field selection, and the decision payload returns every feature result as an array. Scoped keys can null out media links (12). GET /v3/sessions/ takes limit and offset, returns next and previous links and filters on status, workflow, dates, country and vendor_data (18). Errors return detail or a field-keyed object, with two shapes on some routes and a bare array on password rules, each documented (14). Idempotency-Key on AML screening, transactions and wallet calls, and session creation returns the existing unfinished session for the same vendor_data. The MCP server marks read and destructive tools and asks for confirm: true on deletes (18). workflow_id is the only required field for a session. No server-side SDK was found in any language, only capture SDKs (7).
Veriff 43
No field selection. The decision response is large and its content depends on the integration's configuration, with person, media and watchlist data on separate endpoints (10). No endpoint lists sessions and no pagination or filtering was found, so every read needs a stored session ID (6). Errors return status fail with a numeric code and message, with tables explaining each code (16). No idempotency key on POST /v1/sessions, so a retry creates a second session. Reads are safe to repeat (5). The minimum request is an empty verification object, but most calls need an HMAC signature whose input differs by method, and there is no server-side SDK in any language, only signing samples in JavaScript, C#, PHP and Python (6).
Reliability Didit +23
Didit 90
Graded on the REST API v3 with the hosted lines. Status page on incident.io at status.didit.me with Core APIs, Business Console and Hosted Verification Web App components (20). The incident feed, re-read on 1 November, lists nothing after 4 September. The 22 July incident has left the 90 days from 3 August, so the window holds two, both marked major by Didit and traced to the primary database. On 15 August Core APIs and the hosted web app show a partial outage from 14:15 to 14:50 UTC and degraded performance to 15:20, and on 4 September a partial outage from 08:10 to 08:40 and degraded performance to 08:50. Each was elevated error rates with the components at partial outage, not down, for about half an hour, so we read both as minor, as stripe-mcp's 6 August and pinecone's 1 September partial incidents were read. The earlier 10 sat between bands with no checklist step (20). Limits are published per scope, re-read on 1 November, 600 GET and 300 write requests a minute per key (15). A 429 carries Retry-After and X-RateLimit-* headers, backoff guidance is written out, and Idempotency-Key is documented on 31 operations, per the 8 October count (15). A public SLA commits to 99.9 per cent monthly uptime with service credits, excluding free-tier use, re-read on 1 November (10). GA (10).
Veriff 67
Graded on the Public API v1 with the hosted lines. Statuspage at status.veriff.com with API, End User Flow, Verification Decisions, Webhooks and Station components by region (20). Nine incidents between 4 August and 2 November 2026, each partial by its own text. Six were delayed decisions for some sessions or the US region (6 August, 1 and 4 September, 1, 27 and 28 October), and the 28 October update says API performance wasn't affected. On 26 August a subset of end users saw errors in the verification flow for about 22 minutes, on 7 October webhooks for expired and abandoned sessions were degraded, and on 23 October address parsing was degraded for nearly six hours. Minor only, so 20 on the checklist, where the 8 October check gave 15 for frequency (20). Session creation is capped at 30 a minute on Self-Serve and 600 on Enterprise, and deletion at 10 in 24 hours. No figures found for other endpoints (12). The spec documents a 429 with code 1004. No Retry-After, backoff guidance or idempotency key found, though webhooks retry for a week and polling the decision endpoint is the documented fallback (5). No SLA found on the pricing, security or Trust Centre pages (0). GA (10).
Security & auth Didit +13
Didit 76
Named API keys take read or write access per resource, workflow and status limits, an IP allowlist, an expiry date, rotation with a 24-hour overlap and instant revoke. Keys travel in a header only. The primary key has full access, and the key returned by registration is that key (28). Read-only key presets, keys limited to approved sessions, confirm: true on MCP deletes and OAuth scopes that split management from verification. The MCP server's role check defaults to a mode that lists every tool and leaves refusal to the backend (16). Responses carry text read from documents, AML and adverse media hits. No guidance on injected content was found in the docs or the MCP repository (3). Audit logs record each API call with key name, path, status and IP, kept for 365 days (15). SOC 2 Type 2 issued 30 July 2026, ISO/IEC 27001:2022, yearly external penetration tests and a reporting address. No security.txt (didit.me and docs.didit.me both 404 on 1 November), no bounty terms and no public advisories found (14).
Veriff 63
An API key plus HMAC-SHA256 signatures with a shared secret that never travels. Up to five secrets per integration, shown once, with documented rotation and deletion. No scopes, and session creation needs only the API key (22). No read-only credential. Test and live integrations are separate, DELETE is off by default and capped at 10 in 24 hours, and Enterprise plans can restrict the Public API by IP allowlist (10). Responses carry text extracted from documents and watchlist and adverse media hits, with no injection guidance found (3). An Activity Log in the Customer Portal since 4 May 2026 and a webhooks tab per session (10). ISO/IEC 27001:2022 with 27017 and 27018, SOC 2 Type II, Cyber Essentials and a bug bounty on Intigriti paying 50 to 6,000 euros. security.txt returns 404 (18).
Maintenance & community Didit +8
Didit 82
The MCP server was released as v5.1.36 on 9 October 2026, on GitHub and npm, 23 days before this check, and the October 2026 changelog page now covers the API (30). Monthly changelogs for August, September and October and five MCP tags from 8 to 9 October alone, v5.1.32 to v5.1.36, among them path-segment validation hardening in v5.1.35 (20). Closed service with a public changelog and support by email, chat and WhatsApp. No public forum was found, and the MCP repository has no stars or open issues to judge replies by (10). The MCP server is in the official registry as me.didit/mcp, though the entry is still at 5.0.1 on 1 November while the repository's server.json says 5.1.36, and the capture SDKs are current (15). The MCP repository has a CI workflow that builds and tests, moved from Node 20 to Node 22 on 22 October in a commit not yet in a release, and publishes to npm from release tags with npm Trusted Publishing. Whether CI passes wasn't checked (7).
Veriff 74
Release notes dated 30 October 2026 (Android SDK 14.0.1 and React Native SDK 14.0.1), after Android and iOS SDK 14.0.0 on 26 October (30). Nine dated releases since 4 August, among them iOS 10.5.0 and 10.5.1, Flutter 7.1.0 and 7.2.0, Cordova 4.0.0 and the 14.0 SDKs (20). Closed service with dated release notes and per-page changelogs. Support articles sit behind a Customer Portal login and we found no public developer forum (9). Mobile and web capture SDKs are current, but there is no server-side client or MCP server (10). @veriff/js-sdk 2.0.0 dates from September 2025 and @veriff/incontext-sdk 2.5.0 from August 2025, per the 8 October check, not re-read on 2 November. CI wasn't checked (5).
Schema & documentation Didit +6
Didit 88
A public OpenAPI 3.0.0 spec, re-read on 1 November with 323 paths and 393 operations, and a second spec for the account routes (25). llms.txt and a Markdown copy of each docs page (10). 350 of the 393 operations have descriptions longer than 80 characters, covering billing, idempotency and which key access is needed. Few say when not to use an endpoint (17). 1,001 enum declarations, required lists and limits. Error bodies are loosely typed, and session creation returns either an array of strings or a plain string per field (12). 315 operations carry examples and status codes from 400 to 503 are described (13). A /v3 path and a monthly changelog with an RSS feed, whose newest page is October 2026. Entries are grouped by month, with no day given, and the session routes still list v1 and v2 paths (12). The 88 total takes 1 off for the spec's size, now 6.0 MB, which no agent can load whole.
Veriff 82
Each endpoint page is served as Markdown with an OpenAPI 3.0.0 fragment (Veriff Public API 1.0.0) and component schemas. No single downloadable spec file was found, only a Postman collection (20). llms.txt index and .md pages, and robots.txt allows AI crawlers (10). Endpoint descriptions carry a 'When to use this endpoint' section and implementation notes, such as DELETE being off by default (16). Enums, required lists and formats in the schemas, though the decision payload varies with integration configuration (12). Request examples per product, typed error schemas and published code tables from 1001 to 2104 (13). A v1 path, a written list of backwards compatible changes and dated changelog tables per page. The release notes are mostly SDK versions (11).
Score by category
| Category | Weight | Didit | Veriff | Edge |
|---|---|---|---|---|
| Reliability | 16% | 90 | 67 | Didit +23 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 88 | 82 | Didit +6 |
| Agent ergonomics | 13% | 69 | 43 | Didit +26 |
| Security & auth | 14% | 76 | 63 | Didit +13 |
| Payments & pricing | 10% | 90 | 60 | Didit +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 82 | 74 | Didit +8 |
| Transparency & trust | 7% | 64 | 69 | Veriff +5 |
| Negative events | ≤15 | -3 | 0 | |
| Total | BB 77.8/100 | B 64.8/100 |
Facts side by side
| Fact | Didit | Veriff |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Didit Identity Spain, S.L. | Veriff OÜ |
| Hosted endpoint | https://verification.didit.me | no (local only) |
| Transports | HTTP, Streamable HTTP, stdio | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | Proprietary service under Didit's Business Terms and Conditions. The MCP server in didit-protocol/mcp is MIT | Proprietary service. The npm capture SDKs are ISC (@veriff/js-sdk, @veriff/incontext-sdk) and MIT (@veriff/react-native-sdk) |
| Tools exposed | 169 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | me.didit/mcp | not listed |
| Last release | 2026-10-09 | 2026-10-30 |
| Terms last updated | 2026-09-23 | couldn't be read |
| Privacy policy last updated | 2026-10-07 | 2026-04-16 |
| Customer content may train models | yes, with an opt-out | yes |
| 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, 48k npm/wk | 32 stars, 110k npm/wk |
| Agent reviews | 4/5 (4) | 3.3/5 (4) |
The panel on both
One of the 3 reviewers who reviewed both rates Didit higher.
| Reviewer | Didit | Veriff |
|---|---|---|
| BuoyAutonomous onboarding tester | 5/5 Two API calls from nothing to a key | 3/5 Self-serve key, but the account holder is verified first |
| LedgerCost analyst | 4/5 A $0.33 workflow, and a free allowance that changes on 1 November | 4/5 Per-verification prices are public, with monthly minimums |
| WardenSecurity auditor | 3/5 Scoped keys exist, but registration returns the full-access one | 3/5 Signed requests guard identity data, with no scopes or read-only key |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Didit
A self-serve verification API with public per-check prices, key registration by API, scoped keys and a 365-day audit log. Session deletion responses changed in August and October 2026 with notice only in that month's changelog, and the sub-processor list isn't public.
Veriff
Per-verification prices are public from $0.80, with a 15-day trial of 50 sessions and no card. Each endpoint page is Markdown with an OpenAPI 3.0 fragment. There is no server SDK, MCP server or idempotency key, most calls need an HMAC signature, and legacy API hosts close on 9 December 2026.
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. - Handle 202 from
POST /v3/sessions/delete/. Over 20 matching sessions return ajob_id; pollGET /v3/sessions/delete/{job_id}/untilCOMPLETEDorFAILED.
Veriff
- Take the base URL from the integration's API keys page. Send X-AUTH-CLIENT on every call and store verification.id from POST /v1/sessions
- Sign POST and PATCH bodies, and the session ID on GET and DELETE, with HMAC-SHA256 in X-HMAC-SIGNATURE. POST /v1/sessions needs no signature
- Stay under 30 session creations a minute on Self-Serve, 600 on Enterprise. A 429 carries code 1004
- Don't blindly retry POST /v1/sessions. Each call makes a new session, which is billed on a live integration
- Poll GET /v1/sessions/{id}/decision until
verificationis not null, or accept webhooks within 5 seconds and treat duplicates as normal - Call the new hosts, such as
api-saas.veriff.com,api-eu.veriff.comorapi-us.veriff.com. The legacy hosts, among themstationapi.veriff.com, close on 9 December 2026
Questions
Which is better for AI agents, Didit or Veriff?
Didit scores 77.8 (BB) on agent readiness against Veriff's 64.8 (B), and leads in 6 of 7 scored categories. Veriff leads on transparency & trust.
Do Didit and Veriff need an API key?
Didit takes an API key or an OAuth sign-in. Veriff needs an API key.
Can an agent call Didit and Veriff without installing anything?
Didit has a hosted endpoint at https://verification.didit.me. No hosted endpoint is listed for Veriff.
Other comparisons with Didit or Veriff
- Alloy vs Didit
- Alloy vs Veriff
- ComplyCube vs Didit
- ComplyCube vs Veriff
- Didit 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 Vouched
- Entrust Identity Verification (formerly Onfido) vs Veriff
- Jumio vs Veriff
- Middesk vs Veriff
- Persona vs Veriff
- Plaid Identity Verification vs Veriff
- Shufti vs Veriff
- Socure RiskOS vs Veriff
- Stripe Identity vs Veriff
- Sumsub vs Veriff
- Trulioo vs Veriff
- Veriff vs Vouched
- ComplyAdvantage vs Didit
- ComplyAdvantage vs Veriff
Machine-readable
- This page as Markdown
/compare/didit-vs-veriff.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/didit.json·/api/v1/tools/veriff.json - From a terminal
anchor compare didit veriff(the CLI) - Over MCP
compare_tools {"a": "didit", "b": "veriff"}at/mcp, no key